Send new Tinylawn leads into the CRM, field-service, calendar, and workflow tools your team uses.
You need organization admin access in Tinylawn, a Zapier account, and an account for the app you want to connect. Have one recent lead ready for field mapping. Destination apps and workflows with several steps may require paid plans.
Tinylawn is available as a public beta app in Zapier’s app directory. Its only trigger is New Lead: an instant notification when a lead is created. Updates to existing leads do not start another run.
Open Tinylawn Integrations settings, choose Generate key, and copy the full key. Tinylawn only shows it once.
Open Zapier Connections, add a Tinylawn connection, and paste the key into the authentication field.
A successful connection is labeled with your Tinylawn organization name and slug. This helps you choose the right account when you manage more than one connection.
Treat it like a password. Tinylawn stores only a one-way hash. If the full key is lost or exposed, regenerate it and reconnect Zapier.
Choose a published template below to start with the workflow’s steps already selected. Connect your own accounts and review the mapping before testing. You can also build a Zap from scratch.
In Tinylawn Integrations settings, choose “Create a Zap”, then choose a workflow template. Setup opens separately in Zapier. Sign in when prompted.
With Tinylawn and New Lead selected, connect your business using its API key.
Test the trigger and select a recent lead sample. Connect the destination app and map its required fields.
Test each action, review the records it creates, then publish the Zap when you are ready.
You can also choose “Build your own Zap” to start from scratch. If loading stalls, “Use simple list” shows direct template links in the same chooser. Action tests can create real records in your destination account. After publishing, confirm a new lead’s run in Zap History; old leads are samples for setup and are not backfilled. Later lead edits do not start another run or update the destination record.
These published templates open in Zapier with the workflow’s steps already selected. Connect your accounts, review the fields, and test each action before enabling. New Lead starts when a lead is created; it does not add an approval step. Requested dates and times still need your team’s confirmation.
Add filters for required values that may be missing, such as a name or email address. Use one workflow to create each destination record: two creation Zaps or a replay can make duplicates. Check Zap History and the destination before retrying a run. Separate notifications or tracking steps can use the same lead without creating another customer.
Jobber: Create a request Find or create a Jobber client, then add a request and note from a new Tinylawn lead with email.
Review the client match before enabling the Zap. Jobber’s Create Request action uses the client’s first property, so check it against the requested address in the note. If your business also uses another Jobber handoff, enable only one path for each lead to avoid duplicates. Requested times remain unconfirmed.
Use this template
LMN: Find a contact and add a note Find or create an LMN contact and add a note for each new Tinylawn request.
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.
Use this templateGive the inquiry a Pending ToDo with an internal follow-up date. Choose this instead of the note-only workflow for the same leads.
GorillaDesk: Add a lead Add a GorillaDesk lead with the contact, property, and service details captured by Tinylawn.
GorillaDesk’s Zapier integration requires its Pro plan. Add Lead requires your GorillaDesk Account ID and the customer’s first name. Each run adds a lead, so review repeat submissions before follow-up. The workflow does not confirm a service appointment.
Use this template
Housecall Pro: Create a customer Create a Housecall Pro customer from the contact details on a new Tinylawn lead.
Create Customer has no notes or service-request field. It does not carry the Tinylawn link or create a job, estimate, or API Lead. First name is required. Enable the Zapier app on an eligible Housecall Pro plan and test phone mapping. Each run creates a customer, so repeat inquiries may create duplicates.
Use this template
ServiceTitan: Create a lead form Create a ServiceTitan lead form with the contact, requested property, and intake summary from Tinylawn.
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.
Use this template
FieldPulse: Create a lead Create a FieldPulse lead with contact details, requested property, and an intake note.
First name is required. Each run creates a new lead with no matching or upsert step, so check repeat inquiries before replaying a delivery. Job Notes stays empty; requested timing goes in Notes and still needs confirmation. Check your account’s Zapier access and test the workflow before enabling it.
Use this template
LawnPro: Create a follow-up to-do Create a LawnPro follow-up to-do with the full Tinylawn inquiry for your team to review.
Choose the required Type for a single to-do and verify date parsing in your LawnPro account’s timezone. This is an internal follow-up date, not the requested service date. Customer and Property remain unset, and no customer or service visit is created. Each run adds a to-do; check the lead ID before replaying. Connect an eligible LawnPro account as its owner.
Use this template
ServiceM8: Create a client Create a ServiceM8 client with the contact details and service address from a Tinylawn inquiry.
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.
Use this templateCarry the full inquiry into a Quote-stage job card. Choose this instead of the client-only workflow for the same leads.
Service Fusion: Create a customer with private notes Create a Service Fusion customer with contact details, service address, and private intake notes.
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.
Use this template
Workiz: Create a lead Create a Workiz lead with the contact, property, and request details from Tinylawn.
First name, Workiz API access, and Leads access are required. Test the resulting schedule state and any automations before enabling: Zapier describes this action as scheduling a lead, and leaving Lead start time empty has not been verified to prevent calendar effects. Each run creates a lead without duplicate matching. Requested timing is mapped only to Description.
Use this template
JobNimbus: Create a contact Create a JobNimbus contact with the customer, service address, and Tinylawn inquiry in its description.
Display Name is required. Connect your account and review its Contact Type, Status, and Source selections during setup. Check the Mobile Phone mapping because Tinylawn does not identify phone type. State Text expects supported state codes. External Id is a reference, not a guarantee of duplicate matching; test repeat inquiries with your own contacts. Requested timing stays in Description; this workflow does not create a job or booking.
Use this templateBlank values are sent as empty fields. Service details are sent as a line-item list when the lead includes matched services.
Neither is among the verified Zapier workflows in this guide. SingleOps states that it has no native Zapier integration and provides a developer Lead Entry API. Aspire offers API access on eligible plans, but a public Aspire Zapier connector has not been verified. Either path would require account access, custom integration work, and testing. No ready-to-use Tinylawn connection for either app is provided here.
Generate or regenerate the key in Tinylawn, then reconnect the Tinylawn account in Zapier. The old connection cannot be repaired without the new full key.
Create a lead in Tinylawn, return to the Zap editor, and test the New Lead trigger again. Zapier requests up to 25 recent leads for setup.
Confirm the Zap is on and uses the expected Tinylawn connection. If the API key was regenerated or revoked, reconnect the account and turn the Zap on again so Zapier can create a new subscription.
Turn off the Zaps that use Tinylawn, then revoke the API key in Tinylawn Integrations settings. Revoking or regenerating the key removes active Tinylawn webhook subscriptions.
Still stuck? Email support@gettinylawn.com with the Tinylawn business name, Zap name, and the time of the failed run. Do not email an API key.
The integration uses production HTTPS endpoints under the following base URL:
https://app.gettinylawn.com/api/v1 /zapier/me Tests the API key and returns the connected organization.
/zapier/subscriptions Registers Zapier’s unique New Lead webhook URL.
/zapier/subscriptions/{id} Removes a webhook subscription. Repeated deletes are safe.
/zapier/leads?limit=25 Returns recent leads so the Zap editor can load real samples.
Every request includes the customer-provided key
in the x-api-key
header. Invalid and revoked keys return
401 Unauthorized.
Keys are organization-scoped. The endpoints return only that organization’s name, subscriptions, and lead records.