Create the contact record
Give your team the customer and service-address details for follow-up.
Bring Tinylawn inquiries into Service Fusion
Pass new contact and service-address details into Service Fusion, with service needs, requested timing, and the Tinylawn link in Private Notes for your team to review.
Via Zapier
Connect your accounts, review the fields, and test before enabling. View Service Fusion 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 customer with private notes
Choose Create Customer. Map Customer Name, First Name, Last Name, Email, Phone, Street 1, City, State Prov, and Postal Code. Put the request, timing awaiting confirmation, source, lead ID, and Tinylawn link in Private Notes.
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 Private Notes
- 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:
Service Fusion requires its Pro plan for Zapier. Customer Name is required. Each run creates a customer without matching existing records, so review repeat inquiries before enabling or replaying. Billing, credit, tax, and account-specific settings remain untouched. Requested dates and times still need confirmation; this workflow creates no job or booking.
Workflows this connection fits
Keep intake notes private
Preserve the request in Private Notes while leaving Public Notes empty.
Review before arranging work
Use the Tinylawn link to check the full inquiry before confirming the next step.
Common questions about this connection
How does Tinylawn connect to Service Fusion?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to Service Fusion 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 Private Notes, Source, Tinylawn lead ID, and link. Empty values remain empty, and the destination action determines which fields it accepts.
