Authenticate API requests to Calendars API using API keys or OAuth tokens, then securely store credentials in Zapier
Zapier authenticates with Calendars API via OAuth 2.0 tokens and refresh tokens ensuring ongoing access to calendars groups and resources
POST /calendars/, PUT /calendars/:calendarId, DELETE /calendars/:calendarId, calendars.readonly, GET /calendars/, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots, calendars/groups.readonly, GET /calendars/groups, calendars/groups.write, POST /calendars/groups, POST /calendars/groups/validate-slug, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status, calendars/resources.readonly, GET /calendars/resources/:resourceType
Trigger A new calendar is created in Calendars API
Actions Create a calendar assign resources and publish available slots to Zapier
POST /calendars/
Required fields name timeZone color calendarId returned after creation
Trigger Calendar data retrieved for a user or date range
Actions List calendars retrieve free slots and filter results
GET /calendars/ or GET /calendars/:calendarId/free-slots
Key fields calendarId dateRange timeZone
Trigger Changes to calendar groups or memberships
Actions Create update delete groups and assign calendars to groups
POST /calendars/groups
Key fields groupId slug title calendars
Automate charity operations without custom development reducing deployment time
Keep volunteers staff and donors aligned with live calendar data and reminders
Centralized calendar insights across campaigns for faster decision making
This glossary defines core terms like Calendar Group Endpoint Resource and Slug plus how processes work in the integration
A time based container for events that defines availability and scheduling
A specific API URL path that performs an action on Calendars data
An item such as a room or equipment that can be allocated to a calendar
A URL friendly identifier for a calendar group used in routing and linking
Automatically assign volunteers to calendars based on availability and skills when new events are created
Send reminders to donors when events are approaching by triggering messages from Zapier to email or SMS
Consolidate calendars across campaigns into a single dashboard with filters by date and location
Export API credentials from Calendars API and configure a new Zap in Zapier to use those credentials
Set up triggers like calendar created or slot available and actions like create calendar or update a group
Test end to end flows in a staging environment, then deploy and monitor runs for stability
Calendars API supports API keys and OAuth 2.0 tokens. In Zapier you typically connect via OAuth 2.0 tokens and store credentials securely. Tokens refresh automatically to maintain access. For read only access use the calendars.readonly scope in combination with the correct credentials.
Yes you can read calendar data with appropriate scopes. Use the GET endpoints to fetch calendars and slots without write permissions. Access level depends on the permissions configured in Calendars API and the Zapier app setup which can restrict to readonly access.
You can manage slots and resources by using endpoints that create and update calendars, manage groups and assign resources. Use PUT and POST calls to modify calendars and groups, and GET calls to retrieve current availability and resources.
The Calendars API exposes endpoints for creating updating and deleting calendars, reading calendars and groups, managing groups and resources and retrieving available slots. The included endpoints cover calendars calendars groups and resources with related actions.
Synchronization can occur via webhooks or polling. Ensure credentials stay current and that your Zapier zaps map fields correctly. Webhooks can push updates while polling can fetch changes at regular intervals.
No heavy coding is required. You can use Zapier templates and built in actions to connect Calendars API. Some basic mapping and field configuration may be needed to tailor flows to charity workflows.
API rate limits and error codes are documented in the Calendars API docs. Start with the default limits and monitor usage in your Zapier connections. If you hit limits contact support for guidance on pacing and batching requests.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
