Keep new Tinylawn requests with your LMN contacts

Send the caller’s details and requested property into LMN, then add a communication note with the service needs and preferred timing. A separate note step keeps repeat requests visible for existing contacts.

Via Zapier

View setup guide View LMN 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

Find a contact and add a note

Use Find Contact with create-if-missing enabled. Map the contact and jobsite fields, then pass the returned LMN Lead ID to Create ToDo/Note. Put the service needs, requested property and timing, and Tinylawn link in the note.

Lead context ready for the next step

Customer first and last name
Email address and phone number
Jobsite street, city, state, and postal code
Service needs and requested timing in the note
Tinylawn lead link and received time

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: LMN requires a Professional or Enterprise plan for Zapier. Set Lead Type to Lead and Communication Type to Note for the note workflow. First and last names are required; check contact matching with your own records. Requested dates and times still need confirmation.

Another setup option

Create a follow-up task

Use this option when your team wants a follow-up task in LMN instead of a communication note alone. Find or create the contact, then create a Pending ToDo with the full intake details.

Start with New Lead, then use Find Contact with create-if-missing enabled. Filter out missing first and last names and missing email used for matching. Set Lead Type to Lead and map the requested property only to jobsite fields.
Add Create ToDo/Note and pass the native LMN Lead ID returned by Find Contact. Set Communication Type to ToDo and Status to Pending.
Set Task Name to Review Tinylawn inquiry plus the customer’s name. Map Due Date to the lead’s received time and put the full intake, requested timing awaiting confirmation, source, lead ID, and Tinylawn link in the note.
Select the appropriate assignee in your account; choose priority only if your process needs it. Test contact matching, due-date parsing in your timezone, and the resulting Pending task before enabling.

Choose this task variant or the note-only variant for the same leads. The received-time due date is for internal follow-up, not a promised service visit. Contact notes are only set when a new contact is created; the task carries each inquiry. A repeated run can add another task, so check the lead ID before replaying. This workflow does not book or dispatch work.

Workflows this connection fits

Capture landscaping inquiries

Start a contact record with the customer and property details collected during intake.

Keep repeat requests visible

Add a new communication note even when Find Contact returns an existing contact.

Prepare the next conversation

Give your team the service needs, preferred timing, and a link to review the original request.

Common questions about this connection

How does Tinylawn connect to LMN?

This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to LMN 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, Jobsite street, city, state, and postal code, Service needs and requested timing in the note, Tinylawn lead link and received time. Empty values remain empty, and the destination action determines which fields it accepts.