Integration reference
Calendly Trigger and Action reference
Start Workflows from bookings and cancellations, retrieve event details, and create single-use scheduling links.
Authentication
Connect Calendly through OAuth. Select your organization and the events to watch.
- Trigger account type:
oauth2; reconnect byoauth. - Action connection type:
oauth2; available modes: Connected Calendly account.
Create or reuse the account from a Trigger or Action dialog, or manage it under Settings → Connected accounts. See Authentication and permissions for scopes and access diagnostics, or Connected accounts for reuse, reconnect, revocation, and credential rotation.
Scopes and permissions
Base Trigger authorization requests: users:read, organizations:read, scheduled_events:read, scheduled_events:write, event_types:read, webhooks:read, webhooks:write, scheduling_links:write.
Operation-specific requirements appear in the tables below. Custom event selections can add scopes dynamically, so the current Trigger or Action dialog remains authoritative for the exact consent request.
Use Calendly as a Trigger
The current provider manifest contains 6 available Trigger definitions. Representative definitions include:
- Invitee Created
- Invitee Canceled
- Invitee No Show Created
View all 6 available Trigger definitions
| Trigger | Manifest key | Delivery | Additional scopes |
|---|---|---|---|
| Invitee Created | calendly.invitee_created.instant | instant | None declared |
| Invitee Canceled | calendly.invitee_canceled.instant | instant | None declared |
| Invitee No Show Created | calendly.invitee_no_show_created.instant | instant | None declared |
| Invitee No Show Deleted | calendly.invitee_no_show_deleted.instant | instant | None declared |
| Any Calendly Events | calendly.any_event.instant | instant | None declared |
| Custom Calendly Events | calendly.custom_webhook_events.instant | instant | None declared |
Choose the narrowest event definition that fits the Workflow. Configure provider-specific resource and event filters in the Source dialog before adding broader Workflow Filters.
Use Calendly Actions
The current Action manifest contains 5 operations. Representative Actions include:
- Get Event
- List Event Invitees
- Cancel Event
- Create Single-use Scheduling Link
View all 5 available Action definitions
| Action | Manifest key | Access and auth | Manifest rate limit |
|---|---|---|---|
| Get Event | calendly.get_event | None declared FastHook-managed account | 1/second |
| List Event Invitees | calendly.list_invitees | None declared FastHook-managed account | 1/second |
| Cancel Event | calendly.cancel_event | None declared FastHook-managed account | 1/second |
| Create Single-use Scheduling Link | calendly.create_scheduling_link | None declared FastHook-managed account | 1/second |
| Custom API Request | calendly.custom_api_request | None declared FastHook-managed account | 1/second |
The Action editor reads its required permissions, fields, remote resource pickers, output schema, and rate limit from the provider manifest. Available fields can change with the selected operation and authentication mode.
Build a Workflow
- Create a Source using a Calendly Trigger definition.
- Create a Workflow with that Source as its Trigger.
- Add the required Calendly Action and select the connected account.
- Map Trigger or earlier-Step data into the Action fields with the field picker.
- Add a Filter, Paths, Delay, or Transformation when the route needs it.
- Activate the Workflow, produce a controlled event, and verify the run in Audit and in Calendly.
Troubleshooting Calendly
- The account is missing or cannot be selected
- Confirm the active FastHook team, provider, account status, and authentication mode. A disabled or revoked account cannot execute an Action.
- A resource picker is empty
- Verify that the connected provider identity can access the resource itself. OAuth consent does not add workspace, repository, channel, drive, project, base, or record permissions.
- The editor asks for additional scopes
- Reconnect the same account from the affected Trigger or Action so FastHook can request its current manifest scopes. Then reopen the editor and select the resource again.
- An active Workflow returns 401, 403, or a permission error
- Compare the selected operation’s access requirements below with the account recorded in Audit. Check provider-side membership and object access before repeating the Action.
- The provider returns 429 or a temporary 5xx
- Inspect the Step attempt and retryability in Audit. FastHook can retry temporary failures, but provider quotas and idempotency rules still apply.
Provider-specific checks
- Webhook access depends on the connected Calendly account and plan. FastHook watches events accessible to the connected user.
- Use an event UUID for event actions and an event type URI for scheduling links.
- FastHook verifies timestamped webhook signatures and deduplicates repeat deliveries.