Hand off the lead
Create the supported record your CRM or field-service workflow needs.
Tinylawn’s public beta Zapier app starts a workflow when a new lead is created. Map the customer, request, property, preferred timing, and Tinylawn link into the supported actions your team needs.
Direct Zapier connection
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.
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.
Map the fields your chosen action accepts. Add filters for missing required values and test the resulting record before turning the Zap on.
Choose a supported destination app and action in Zapier, then map the Tinylawn lead fields that action accepts.
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.
Create the supported record your CRM or field-service workflow needs.
Create a review event using the requested date, time, address, and service.
Send a channel message or add the lead to a shared tracking sheet.
Tinylawn’s public beta app connects to Zapier with an organization API key. You sign in to Zapier and connect the destination apps your workflow uses.
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.
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.
Available fields include Customer name, email, and phone, Service needs and matched services, Property address, Desired date, time, and timeframe, Lead source, status, and Tinylawn link. Empty values remain empty, and the destination action determines which fields it accepts.