Grant the calendars.write scope to your integration and complete the OAuth flow to securely access calendar data.
Act-On must authorize access to the Calendars API so it can read, write, and manage calendar data on your behalf.
Endpoints include POST /calendars/ to create calendars, PUT /calendars/:calendarId to update, DELETE /calendars/:calendarId to remove, GET /calendars/ for listing, GET /calendars/:calendarId for details, GET /calendars/:calendarId/free-slots to check availability, and additional group, resource, and slug management endpoints such as POST /calendars/groups, PUT /calendars/groups/:groupId, and GET /calendars/resources/:resourceType.
Trigger: when a new calendar is added in Act-On, create a calendar in Calendars API.
Actions: use POST /calendars/ to create calendars, GET /calendars/ to list, and PUT /calendars/:calendarId to update existing records.
POST /calendars/ — create calendar; GET /calendars/ — list calendars; PUT /calendars/:calendarId — update calendar.
Key fields: name, timezone, color, and calendarId for updates.
Trigger: changes to calendar groups in Act-On.
Actions: manage groups via POST /calendars/groups, PUT /calendars/groups/:groupId, and related endpoints.
Mapping: POST /calendars/groups to create groups; PUT /calendars/groups/:groupId to update; PUT /calendars/groups/:groupId/status to enable/disable.
Key fields: groupId, slug, name, color.
Trigger: requests for available slots or resource data.
Actions: pull calendars/resources/:resourceType.
GET /calendars/resources/:resourceType
Key fields: resourceType, calendarId, resourceId.
Automate calendar workflows without writing code.
Rapidly connect and sync data between Act-On and Calendars to streamline scheduling.
Centralize control over calendar data across apps with a no-code workflow.
Key concepts include endpoints, triggers, actions, resources, groups, and mapping steps to connect Calendars API with Act-On.
A set of rules and protocols enabling Act-On to access Calendars data programmatically.
A specific URL and HTTP method used to perform an action on a resource.
The process of granting secure access to APIs, typically via OAuth or API keys.
A callback URL that receives real-time event notifications from an API.
Create calendar events automatically when new emails arrive in Act-On, using the POST /calendars/ endpoint.
Route events to calendar groups using POST /calendars/groups and related endpoints to organize schedules.
Expose free-slots data via GET /calendars/:calendarId/free-slots to optimize meeting times.
Complete OAuth flow and grant calendars.write scope to Act-On to access calendar data.
In Zapier, select the calendars API actions and set triggers aligned with your workflow.
Run end-to-end tests, verify data integrity, and deploy your automation.
The calendars.write scope authorizes creating and updating calendars, events, and related resources. It ensures Act-On can perform necessary modifications while keeping access controlled and auditable.
Yes. calendars.readonly allows you to fetch calendar data without making changes. Use it for dashboards, reporting, or read-only integrations.
Authentication typically uses OAuth 2.0. You’ll redirect users to authorize the app, then exchange a code for tokens to include in your API requests.
Endpoints include POST, GET, PUT, and DELETE for calendars, groups, and resources. See the endpoint list above for full details.
Yes. You can create and update groups with the calendars/groups endpoints and manage their status using the status endpoint.
To retrieve free slots, call GET /calendars/:calendarId/free-slots and interpret the returned time slots for scheduling.
No-code integrations are supported via Zapier; however, some basic configuration is required to map fields and triggers.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
