Review requested times
Keep new requests visible on a calendar without treating them as confirmed jobs.
When Tinylawn creates a new lead, Zapier can use Google Calendar’s Create Detailed Event action to place the requested timing and useful job context on a calendar your team reviews.
Via Zapier
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.
A completed call or intake flow creates the structured New Lead record that starts the Zap.
You choose which available customer, property, request, timing, and source fields the next action receives.
Map the requested date and time, customer, property address, service needs, and Tinylawn lead link into a Google Calendar event.
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.
Keep new requests visible on a calendar without treating them as confirmed jobs.
Put the caller, address, service, and source record in one event description.
Route new lead requests to a dedicated calendar your office team monitors.
No. This connection uses the Tinylawn Zapier app and Google Calendar's supported Zapier action. It is not a native or two-way sync.
The current Tinylawn trigger is New Lead. When Tinylawn creates a lead, Zapier receives the mapped lead fields and runs the destination action you configured.
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.