Start the contact record
Keep the customer and requested property together for your JobNimbus team.
Send new Tinylawn inquiries to JobNimbus
Bring contact and property details into JobNimbus, with the service request and a link back to Tinylawn in the description for your team’s follow-up.
Via Zapier
Connect your accounts, review the fields, and test before enabling. View JobNimbus 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 contact
Choose Create Contact. Map Display Name to the full customer name, then map First Name, Last Name, Email, Mobile Phone, Address Line1, City, State Text, and Zip. Map Tinylawn’s client ID to External Id as a reference. Use Description for the full intake, requested timing awaiting confirmation, source, lead ID, and Tinylawn link.
Lead context ready for the next step
- Customer full, first, and last name
- Email address and phone number
- Street, city, state, and postal code
- Service needs and requested timing in Description
- Source, 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:
Display Name is required. Connect your account and review its Contact Type, Status, and Source selections during setup. Check the Mobile Phone mapping because Tinylawn does not identify phone type. State Text expects supported state codes. External Id is a reference, not a guarantee of duplicate matching; test repeat inquiries with your own contacts. Requested timing stays in Description; this workflow does not create a job or booking.
Workflows this connection fits
Carry the inquiry forward
Preserve service needs and requested timing in Description.
Review the original intake
Use the Tinylawn link before agreeing on the next step with the customer.
Common questions about this connection
How does Tinylawn connect to JobNimbus?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to JobNimbus 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 full, first, and last name, Email address and phone number, Street, city, state, and postal code, Service needs and requested timing in Description, Source, Tinylawn lead ID, and link. Empty values remain empty, and the destination action determines which fields it accepts.
