Start the follow-up
Create a lead your team can review in FieldPulse.
Keep Tinylawn inquiries ready for follow-up in FieldPulse
Send a new lead’s contact and address details to FieldPulse, with the service needs, preferred timing, and Tinylawn link together in Notes.
Via 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
Choose Create Lead. Map First Name, Last Name, Email, Phone, Address, City, State, and Zip Code. Use Notes for the full request, requested timing awaiting confirmation, and Tinylawn lead link.
Lead context ready for the next step
- Customer first and last name
- Email address and phone number
- Street, city, state, and postal code
- Service needs and requested timing in Notes
- 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 is required. Each run creates a new lead with no matching or upsert step, so check repeat inquiries before replaying a delivery. Job Notes stays empty; requested timing goes in Notes and still needs confirmation. Check your account’s Zapier access and test the workflow before enabling it.
Workflows this connection fits
Carry the intake details
Keep the requested service, property, and timing with the contact details.
Check the source
Use the Tinylawn link in Notes to return to the original inquiry.
Common questions about this connection
How does Tinylawn connect to FieldPulse?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to FieldPulse 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, Email address and phone number, Street, city, state, and postal code, Service needs and requested timing in Notes, Tinylawn lead ID and link. Empty values remain empty, and the destination action determines which fields it accepts.
