Integrations
Google Calendar
Create an event, list upcoming events, or check availability.
Automation buildersAdministratorsIntermediateAvailable
What this guide covers
- A Google account through OAuth with access to the intended calendar.
- 3 supported workflow actions.
- The selected Google account must be allowed to read or write the target calendar. Calendar sharing rules still apply.
- A Calendar event does not automatically identify a Yanola contact or WhatsApp recipient.
What Google Calendar connects
A Google account through OAuth with access to the intended calendar.
Create an event, list upcoming events, or check availability.
Prerequisites and permissions
- Google account permission to the calendar
- Calendar identifier
- Explicit start/end timestamps and timezone for time-based actions
External permissions
The selected Google account must be allowed to read or write the target calendar. Calendar sharing rules still apply.
Connect and configure
- Open the intended Agent Project → Integrations.
- Find Google Calendar and select Connect.
- Complete authorization with the correct external identity.
- Confirm the returned connection status is active.
- In the workflow builder, add App Action.
- Select Google Calendar, choose one supported action, select the connection, and complete the fields Yanola displays.
- Save and test with controlled data before activation.
Supported actions
| Action ID | What it does |
|---|---|
create_event | Create a calendar event. |
list_events | List upcoming events. |
check_availability | Check if a calendar has conflicts. |
Example workflow
Check availability before creating an appointment and return the confirmed time to the customer.
text
Workflow Trigger → Validate inputs → App Action (Google Calendar) → Condition → Notify or End FlowReconnection and token expiration
- Open Integrations when a workflow reports a missing, expired, revoked, or error connection.
- Select Reconnect for Google Calendar.
- Authorize the intended identity again.
- Validate access to the exact resource used by the workflow.
- Retest every dependent App Action.
Troubleshooting
| Symptom | What to check |
|---|---|
Connection is expired, revoked, or error | Reconnect from Integrations and complete provider consent. |
Action cannot find a resource | Grant the connected identity access and use the exact provider ID. |
Action input is rejected | Match the action-specific fields and data types shown in the node. |
Test and live behavior differ | Check provider environment, current permissions, external rate limits, and live data. |
Limitations and security
A Calendar event does not automatically identify a Yanola contact or WhatsApp recipient.
Timezones must be explicit when mapping scheduled activity.
Protect the connection
Never place provider access tokens or secrets in workflow text, logs, screenshots, or AI prompts. Remove unused connections and reconnect only through Yanola.
Related documentation
Connected services overviewConnect supported external accounts and use their cataloged actions from the workflow App Action node.App ActionPerform action in a connected app. Exact configuration, outputs, execution behavior, errors, limits, and examples for the App Action workflow node.A connected account was disconnectedReconnect expired, revoked, or error connections and revalidate workflow App Action configuration.