> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Calendly

> Review the planned Calendly connection method and the prerequisites for a future scheduling integration.

Calendly appears in the reviewed integration catalog, but its self-serve connection and tool-creation flows are disabled. The dashboard preview describes the intended provider and operations. It does not establish a usable connection.

<Note>
  Do not enter a token into an unrelated provider form to work around the disabled flow. Wait for a release that explicitly enables the Calendly connection and the intended operation contracts.
</Note>

## Prepare for the connection release

The catalog defines a Personal Access Token credential method. Use [Calendly's token documentation](https://developer.calendly.com/docs/authentication/how-to-authenticate-with-personal-access-tokens) to understand account permissions and scopes. There is no need to create or paste a credential merely to inspect the current Threetone preview.

Plan which account owns the event types, what calendar data the task needs, and which changes require confirmation. Provider account access and subscription restrictions are separate from Threetone workspace access.

## What the release must establish

| Check | Required result |
| - | - |
| Credential setup | The deployed form supports the intended token method and stores it privately. |
| Connection state | The connection can be read back, reconnected, and removed through the supported workflow. |
| Tool definitions | Released operation contracts define the actual inputs, outputs, and allowed actions. |
| Agent execution | A supported runtime can call those operations with the intended workspace and account. |
| Result verification | Controlled tests confirm provider outcomes and failure handling. |

Use [integration overview](/agents-platform/configure/integrations/overview) to choose an available connection method today. A custom integration needs its own supported credentials and execution design; it is not automatically equivalent to the planned native connector.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Why can I see Calendly but not connect it?" id="faq-calendly-preview">The catalog can display a preview definition while its connection feature remains disabled. Check the provider's current release status and enabled actions.</Accordion>
  <Accordion title="Are the listed operations ready to execute?" id="faq-calendly-operations">No executable Calendly operation manifest is established by the reviewed source. Catalog descriptions are planning information rather than proof of tool execution.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.