Skip to main content

Calendly

Read event types, availability and booked meetings, and share scheduling links.

Connect it with: Sign in (OAuth), API key. Calendly's own documentation: https://developer.calendly.com/docs/authentication/creating-an-oauth-app.

What agents can do​

Connect Calendly so the agents working your tasks can reach it. With it connected, they can:

  • List your event types and hand out the right scheduling link in a message or a report.
  • Read upcoming and past booked meetings, with invitee names and answers, to prepare or follow up.
  • Check free time before proposing a meeting slot.

Before you start​

  • A Calendly account. The API is open to every plan, but organization-wide reads need an owner or admin account.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Calendly​

This is the quickest way in: you sign in to Calendly and approve what Jaah asks for. You never copy a key.

  1. In Jaah, open Secrets and select New.
  2. Search for Calendly and select its card.
  3. Give the secret a name you will recognize, such as the account or workspace it reaches, and choose who can use it (see Who can use it).
  4. Select Connect Calendly. Calendly's sign-in window opens.
  5. Sign in to Calendly if asked, check the access listed, and approve it.
  6. You land back in Jaah on the new secret, which reads Connected once its test passes.

If the button reads Jaah app not configured, this Jaah has no app registered at Calendly yet. Use an API key, or your own OAuth app, until it does.

Scopes Jaah requests​

Jaah asks Calendly for these scopes, and no others. A scope marked optional is a checkbox on the Connect screen: untick it and agents simply cannot do that part.

These scopes are set on the OAuth app itself, not chosen at sign-in, so every connection gets exactly these.

ScopeWhy Jaah asks for it
users:readRead the connected user's profile, so the connection shows whose it is
event_types:readList event types, to hand out the right scheduling link
scheduled_events:readRead booked meetings and their invitees
availability:readRead free time before proposing a slot
organizations:readFind the organization's members, for owner and admin accounts

Connect with an API key​

Prefer this when you cannot sign in with Calendly — for example a service account, or a token your admin issued. On the Connect screen select Use an API key instead.

Find each value first:

  • Personal access token: Calendly > your profile menu > Developer > Personal access tokens > Generate new token: name it Jaah, tick users:read, event_types:read, scheduled_events:read, availability:read and organizations:read, then copy the token - Calendly shows it once.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Calendly card.
  2. Name the secret and choose who can use it.
  3. Select Use an API key instead.
  4. Fill in Personal access token.
  5. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Register your own OAuth app at Calendly when your company requires apps it controls, or before this Jaah has an app registered there.

  1. Create an OAuth app in Calendly's developer console, https://calendly.com/app/developer?tab=oauth_apps (Calendly's documentation).
  2. Set its redirect URI to https://app.jaah.ai/api/credentials/connect/callback (on your own Jaah, its console address followed by /api/credentials/connect/callback).
  3. Give it the scopes in Scopes Jaah requests.
  4. Copy its client ID and client secret.
  5. In Jaah, start a new Calendly secret, select Use your own OAuth app, paste both values and select Connect Calendly.

The client secret is stored with the connection, encrypted, like any other secret value.

Test the connection​

Select Test on the secret. Jaah calls Calendly's API once (GET https://api.calendly.com/users/me) with the stored values, and shows who it answered as, or which value Calendly refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A signed-in connection hands the agent a live access_token, with access_token_expires_at. Jaah refreshes it before it expires, so an agent never handles a refresh token.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Calendly secret org/calendly”.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Calendly once the test passes. Steps: Replace or delete a secret.
  • Reconnect: when Calendly ends the grant (a password change, a revoked app, an expired refresh), the secret shows Needs reconnect. Select Reconnect and sign in again; agents get the new token on their next call.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Calendly's side too, revoke Jaah in Calendly's settings, or revoke or delete the key at Calendly.

Limitations​

  • Jaah asks for read access only: agents cannot book, cancel or reschedule meetings or change event types.
  • Agents see the connected user's events; another member's events are visible only to an owner or admin account.
  • Calendly scopes are fixed on the app: with your own OAuth app, the scopes you ticked there are what agents get.
  • Agents can do only what the connected Calendly account and its granted scopes allow.

Troubleshooting​

Test says Calendly rejected the personal access token (401)

The token was revoked, expired or mistyped. Generate a new one under Developer > Personal access tokens and select Replace on the secret.

Agents get 403 Permission Denied on a read

The token or app lacks that scope. Generate a token with the scopes listed above, or add them to your own OAuth app and reconnect.

Consent fails with invalid redirect URI

Calendly allows one redirect URI per app and it must match exactly. With your own app, set it to the redirect URI shown on this page.

The secret shows Needs reconnect

The user disconnected Jaah in Calendly or the grant was revoked. Select Reconnect.

Still stuck? Select Test and read the result: it names the value Calendly refused and the status it answered.

FAQ​

Can agents book meetings for me?

No. Jaah connects with read-only scopes; agents share your scheduling link instead.

Does a token from the old Integrations page work?

Yes, but a token from Developer > Personal access tokens lets you choose its scopes, which is safer.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Calendly account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.