Prepare follow-up
Bring captured contact and request details into a lead your Workiz team can review.
Bring new Tinylawn inquiries into Workiz
Give your team a Workiz lead with the caller’s contact details, requested property, and service needs. Keep the original Tinylawn inquiry linked in the description for follow-up.
Via Zapier
Connect your accounts, review the fields, and test before enabling. View Workiz on Zapier
One trigger. An automatic handoff.
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.
- 1
Tinylawn creates a lead
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.
- 2
Zapier maps the fields
Map the fields your chosen action accepts. Add filters for missing required values and test the resulting record before turning the Zap on.
- 3
Create a lead
Use Create Lead. Map First Name, Last Name, Phone Number, Address, City, State, PostalCode, and Email Address. Put the full intake and requested timing in Description, and leave Lead start time empty. Choose any account-specific lead source during setup.
Lead context ready for the next step
- Customer first and last name
- Phone number and email address
- Street, city, state, and postal code
- Service needs and requested timing in Description
- Tinylawn lead ID and link
Connection details
- Method
- Via Zapier
- Trigger
- New Lead
- Direction
- One-way from Tinylawn
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.
Important:
First name, Workiz API access, and Leads access are required. Test the resulting schedule state and any automations before enabling: Zapier describes this action as scheduling a lead, and leaving Lead start time empty has not been verified to prevent calendar effects. Each run creates a lead without duplicate matching. Requested timing is mapped only to Description.
Workflows this connection fits
Keep timing in context
Preserve the customer’s preferred timing in Description, with confirmation still required.
Return to the inquiry
Keep the Tinylawn lead link with the intake details.
Common questions about this connection
How does Tinylawn connect to Workiz?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to Workiz through its supported Zapier actions. You need accounts for both apps and Zapier. This workflow sends data one way from Tinylawn.
What starts the workflow?
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.
Do later changes sync, and can I replay a 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.
What Tinylawn data can I map?
Available fields include Customer first and last name, Phone number and email address, Street, city, state, and postal code, Service needs and requested timing in Description, Tinylawn lead ID and link. Empty values remain empty, and the destination action determines which fields it accepts.
