Send new Tinylawn contact details to ServiceM8

Create a client record with the customer’s name, phone, email, and service address. Review the full inquiry and requested timing in Tinylawn before arranging work.

Via Zapier

Use this template View setup guide

Connect your accounts, review the fields, and test before enabling. View ServiceM8 on 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

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 client

Use Create Client. Map Name to the full customer name, Address to the formatted service address, and the First Name, Last Name, Phone Number, and E-Mail Address fields. Leave Billing Address and Mobile Number unset unless independently confirmed.

Lead context ready for the next step

Customer full, first, and last name
Phone number and email address
Formatted service address

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. Create Client has no notes field: service needs, requested timing, source, and the Tinylawn link stay in Tinylawn. This workflow creates a client for each lead with no existing-client lookup, so repeated inquiries may create duplicates. It does not create a job or booking.

Another setup option

Create a quote-stage job card

Use this option when your team needs the full inquiry inside ServiceM8. It creates a job card for quote review, with the contact details, requested property, service needs, and Tinylawn link.

Use this template

Start with Tinylawn’s New Lead trigger and choose ServiceM8’s Create Job action. Change Job Status from its Work Order default to Quote.
Map Customer Name to the full customer name and Job Address to the formatted service address. Map the job contact’s first name, last name, phone, and email.
Put the full intake, source, lead ID, and Tinylawn link in Job Description. Label requested timing as awaiting confirmation and the card as ready for quote review.
Leave Billing Address and billing contact fields, Mobile, Purchase Order, and Work Completed unset. Test the resulting status, customer matching, and billing defaults before enabling.

Choose this or the client-only workflow for the same leads. Each run creates a job card; it does not supply a price, appointment, or service visit. ServiceM8 may use the job address as a billing default even when Billing Address is unset, so check that behavior in your account. Requested timing still needs confirmation.

Workflows this connection fits

Save contact entry

Start a ServiceM8 client record with the contact details captured during intake.

Keep the service address

Carry the requested property without assuming it is the billing address.

Review the full request

Return to Tinylawn for service needs and requested timing before arranging work.

Common questions about this connection

How does Tinylawn connect to ServiceM8?

This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to ServiceM8 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, Phone number and email address, Formatted service address. Empty values remain empty, and the destination action determines which fields it accepts.