Bring new Tinylawn inquiries into ServiceTitan

Create a lead form with the caller’s contact details, service address, and a summary of the request. Your team reviews the inquiry in ServiceTitan and confirms the next step.

Via Zapier

One-way handoff from Tinylawn’s New Lead trigger. You choose the destination action and field mapping in 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. 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. 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. 3

    Create a lead form

    Use Create Lead Form, described in Zapier as Create Lead (NO Customer/Location). Map Name, Email, Phone Number, Street, City, State, and Zip. Preserve service needs, requested timing, the lead ID, and Tinylawn link in Summary.

Lead context ready for the next step

  • Customer name, email, and phone
  • Street, city, state, and postal code
  • Service needs and requested timing in Summary
  • 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: Name is required. ServiceTitan’s Zapier connector requires an eligible API-enabled plan and administrator setup. Each run creates a lead form; there is no duplicate matching. Requested timing stays informational in Summary, and this workflow does not create a booking or confirmed job.

Workflows this connection fits

Capture an inquiry

Add a lead form without supplying an existing ServiceTitan customer or location ID.

Preserve the request

Include the service needs and requested property and timing in the intake summary.

Review before confirming

Keep the original Tinylawn record available while your team decides the next step.

Common questions about this connection

How does Tinylawn connect to ServiceTitan?

This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to ServiceTitan 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 name, email, and phone, Street, city, state, and postal code, Service needs and requested timing in Summary, Tinylawn lead ID and link. Empty values remain empty, and the destination action determines which fields it accepts.

Generate your Tinylawn key, then build the Zap.

Follow the setup guide