Create an intake request
Move a captured lead into Jobber for review without retyping the basics.
For leads with an email address, Zapier can find or create a Jobber client, create a request, and add a note with the service details and Tinylawn link for your team to review.
Via Zapier
Connect your accounts, review the fields, and test before enabling. View Jobber on Zapier
Tinylawn remains the intake layer. Zapier moves selected lead data into the action you configure; your destination tool remains where the team manages the work.
When a call or intake flow creates a lead, the New Lead trigger starts your enabled Zap with the captured details. It does not wait for your team to approve the lead.
Map the fields your chosen action accepts. Add filters for missing required values and test the resulting record before turning the Zap on.
Add a Filter that requires Client Email to exist. Use Find Client with create-if-missing enabled, pass its client ID to Create Request, then use Add Note for the service needs, requested address and timing, and Tinylawn link.
Requires a Zapier account, a Tinylawn organization API key, and access to the destination account. Destination action availability can depend on that provider’s plan.
Move a captured lead into Jobber for review without retyping the basics.
Carry the service address and request details into the handoff.
Include the source lead link so staff can open the complete Tinylawn record.
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to Jobber through its supported Zapier actions. You need accounts for both apps and Zapier. This workflow sends data one way from Tinylawn.
New Lead is the only Tinylawn trigger. An enabled Zap starts automatically when a lead is created, without a Tinylawn approval step. Your team still confirms requested service and timing. Changes to an existing lead do not trigger another run.
This workflow sends data one way when a lead is created. Later edits in either app do not sync through New Lead. Before replaying a run or enabling a second Zap, check for records already created: a create action can produce duplicates. Find-or-create steps only match by the rules you configure.
Available fields include Customer name and contact details, Service needs, Property address, Requested timing, Tinylawn lead link. Empty values remain empty, and the destination action determines which fields it accepts.