ActionGoogle CalendarUpdated June 2026

How do I create a Google Calendar event using natural language?

Short answer: Drop the "Google CalendarQuick Add Event" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Calendar ID
calendar_id
stringRequiredUse 'primary' for the user's main calendar, or a specific calendar ID
Event Text
text
stringRequiredNatural language description of the event including date, time, and title
Send Notifications
sendUpdates
optionsOptionalWhether to send notifications about the event
Sample request
{
"calendar_id": "primary",
"text": "e.g. Lunch with Sarah tomorrow at 12:30pm at The Italian Place",
"sendUpdates": "{{trigger.sendUpdates}}"
}
Returns
{
"id": "evt789xyz",
"end": {
"dateTime": "2025-01-21T13:30:00-05:00",
"timeZone": "America/New_York"
},
"start": {
"dateTime": "2025-01-21T12:30:00-05:00",
"timeZone": "America/New_York"
},
"status": "confirmed",
"summary": "Lunch with Sarah",
"htmlLink": "https://calendar.google.com/calendar/event?eid=evt789xyz",
"location": "The Italian Place"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Quick Add Event.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Quick Add Event.

What does the Quick Add Event action do in Google Calendar?
Creates an event using natural language text (e.g., "Dinner with John tomorrow at 7pm"). Google parses the title, date, and time for you, making this great for chatbot or NLP-driven scheduling.
What inputs does Quick Add Event require?
Required: Calendar ID, Event Text. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Google Calendar returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Quick Add Event support batch operations?
Yes. Run Quick Add Event inside a Loop node to process arrays. Tiny Command handles Google Calendar's rate limits automatically so you don't have to throttle manually.
More actions

Other Google Calendar actions.

Action
Create Event
Creates a new event on a Google Calendar with summary, description, start, end, attendees, location, conference link, and reminders. Standard write for piping booked meetings or scheduled tasks into Calendar.
Action
Delete Event
Deletes an event from a Google Calendar by ID. Pass sendUpdates=all to notify attendees of the cancellation; recoverable from Calendar trash.
Action
Get Event
Retrieves a specific event from a Google Calendar by ID with summary, description, start/end, attendees, conference link, and recurrence. The standard read after a trigger fires.
Action
List Calendars
Lists all calendars available to the authenticated user (primary, secondary, subscribed) with access role. Used to populate a calendar picker.
Action
List Events
Lists upcoming events from a Google Calendar with time filters (timeMin/timeMax) and query string. Used for daily-agenda emails, prep-doc generation, or scheduling assistants.
Action
Update Event
Updates an existing event on a Google Calendar: summary, description, start/end, attendees, conference link. Only the fields you pass are changed; pass sendUpdates=all to notify attendees.

Send quick add event from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.