Skip to main content
Integrations · Calendly
A Guild agent books, cancels, and tracks Calendly events on your team’s behalf. Guild stores your Calendly personal access token server-side so agent code never sees it, enforces credential policies before any request leaves the platform, and logs every action for audit.

Book a demo

See how teams govern agents that use Calendly.

Talk to sales

Get access to Guild, then connect Calendly to your first agent.

What the Calendly integration exposes

The tools cover event types, availability schedules, and scheduled events, including booking, cancellation, and invitee tracking. Additional tools reach contacts, routing forms, scheduling links, shares, webhook subscriptions, organisation membership, teams, meeting recaps, activity logs, and data compliance endpoints. Tools are named with the calendly_ prefix and imported from guildai~calendly.

How it works

1

Connect your Calendly credential

In Guild, go to Access & setup > Credentials, click Connect, select calendly, and paste your personal access token into API Key. See Credentials for workspace, member, and agent-scoped options.
2

Import and wire the tools

Import CalendlyTools from @guildai-services/guildai~calendly and spread it into your llmAgent tools object. Guild sends the token as a bearer token in the Authorization header on every outbound request.
3

Select only needed tools

Use pick() to include only the calendly_ tools your agent needs. Narrowing the tool set also makes credential policies easier to write and audit.

Why Calendly access needs governing

Calendly credentials can book and cancel events, remove invitee data, manage organisation membership, and create webhook subscriptions. Guild’s credential proxy checks credential policies before any request reaches Calendly, so you can write ALLOW and DENY rules that limit an agent to specific operations, such as read-only availability checks or booking alone, without issuing a separate token. Credentials are stored and injected server-side; agent code, prompts, and containers never see the token. You can scope a credential to one workspace, one member, or one agent using Credentials, and the activity log tool surfaces a full record of actions taken. Agents that need broader access get it explicitly; everything else is denied by default once you remove the auto-created allow-all policy.

About the Calendly integration

Agents can read and manage Calendly event types, availability schedules, and scheduled events, including booking, cancelling, and tracking invitees. They can also manage contacts, routing forms, scheduling links, and webhook subscriptions. Organisation membership, teams, meeting recaps, and activity logs are also accessible. The integration is guildai~calendly.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect Calendly

In Guild, go to Access & setup > Credentials, click Connect, select calendly, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the calendly_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~calendly:

Frequently asked questions

Not yet. The catalog entry for guildai~calendly lists no webhook events, so Guild cannot trigger an agent run when a Calendly event fires. The integration does include tools to create and manage webhook subscriptions on the Calendly side.
Write a credential policy with a DENY rule targeting calendly_scheduled_events_create_scheduled_event_cancellation and similar mutating operations. Guild’s proxy enforces the rule before the request reaches Calendly. See Credential policies for DENY and ALLOW syntax.
Yes. From the installed agent’s page, connect a dedicated credential for calendly. That token serves only that agent and never applies to other agents or workspaces. See Credentials for the dedicated credential option.
Yes. The tools calendly_data_compliance_delete_invitee_data and calendly_data_compliance_delete_scheduled_event_data submit removal requests for invitee data and scheduled event data respectively. Restrict access to these tools with a credential policy if only specific agents should use them.

Put a governed agent on Calendly this week

Book a demo

See how teams govern agents that use Calendly.

Talk to sales

Get access to Guild, then connect Calendly to your first agent.
Also runs on Guild: Coda · Confluence · Fathom · Fireflies Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 10, 2026