Review requested times
Keep new requests visible on a calendar without treating them as confirmed jobs.
Put requested lead timing on Google Calendar
Use Google Calendar’s Create Detailed Event action to put an inquiry on an internal review calendar. Only continue when the requested date and time are usable; your team still confirms the service.
Via 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 detailed event
Choose an internal calendar. Filter out missing or ambiguous requested dates and times, then set Start Date & Time and an End Date & Time using a review duration your business chooses. Add contact, property, service needs, and the Tinylawn link to the description. Keep attendees empty.
Lead context ready for the next step
- Desired date and time
- Preferred timeframe
- Customer name and phone
- Property address
- Service needs and Tinylawn lead 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:
Google Calendar requires valid start and end times. Tinylawn does not supply an end time or visit duration, and free-text preferences such as “next week” are not an exact start time. Test date parsing and your calendar’s timezone; invalid dates can create an event at the time the Zap runs. Use an internal calendar, keep customer attendees empty, and review visibility, reminders, and Free/Busy settings. This event does not confirm a service visit.
Workflows this connection fits
Prepare for follow-up
Put the caller, address, service, and source record in one event description.
Separate intake calendars
Route new lead requests to a dedicated calendar your office team monitors.
Common questions about this connection
How does Tinylawn connect to Google Calendar?
This guide covers the Zapier workflow: Tinylawn’s New Lead trigger sends captured details to Google Calendar 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 Desired date and time, Preferred timeframe, Customer name and phone, Property address, Service needs and Tinylawn lead link. Empty values remain empty, and the destination action determines which fields it accepts.
