> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/plugins/integrations/communications/calendly.md).

# Calendly

With this integration connected, you can use Filed **Chat** and **Routines** to retrieve information from Calendly and, when **Write** access is enabled, perform approved actions in Calendly. This integration to Filed is connected via our integration provider [Composio](https://composio.dev/)

## Connect Calendly

1. Name the connection for the firm or scheduling team.
2. Sign in with a user who can access the intended Calendly organization and event types.
3. Approve authorization, return to Filed, and verify the connection.
4. Keep write access off unless Filed may create or update scheduling data.

If event types are missing, verify that the connected user belongs to the intended organization.

## Verify the connection

After the connection becomes **Active**, open a known item that the authorized account should be able to access. Confirm organization membership and event-type access. For a new connection, test against a non-production or non-client-sensitive item before relying on it in a deadline-driven workflow.

## Manage permissions

Read access is always enabled. Turn off **Write** in the connection settings to prevent Filed from creating or modifying Calendly data while keeping the connection available for read-only workflows. Re-enable it only after the firm approves the change.

## Troubleshooting

**The authorization screen will not complete.** Sign out of the wrong provider account, restart the connection, and use the firm-managed account that has organization membership and event-type access.

**The connection is active but data is missing.** The provider only exposes content available to the authorized user. Review organization membership and event-type access, then reconnect if the account or environment was wrong.

**The connection is pending or failed.** Open the connection in Filed, correct the provider-side issue, and select **Reconnect**. Do not create duplicate connections to work around a permissions problem.

## Using this integration with Filed Chat and Routines

Use **Chat** for one-off questions and guided work on a client, such as finding Calendly information, summarizing it, or preparing an approved next step. Use **Routines** to automate repeatable work with Calendly data on a schedule or in response to a trigger.

Both experiences respect the connection's access: they can only use data the authorized account can reach, and they can only perform changes when **Write** is enabled. Review changes in the connected application before you finalize them.

## Example prompts

Use these as starting points and replace the bracketed details with the client, date range, folder, record, or task you need. Filed will only run write actions when this connection's **Write** access is enabled.

* “Find recent Calendly information related to \[client name] and summarize the key items.”
* “Show me anything from the last 30 days that needs a response or follow-up.”
* “With write access enabled, create the approved follow-up for \[client name] for my review.”

## Capabilities

### Review communication context

Use Filed to retrieve the emails, calendar information, or meeting context available to the connected account. This helps your team find client follow-ups, deadlines, and outstanding requests.

### Coordinate approved follow-up

When **Write** access is enabled, Filed can help create approved communications, events, or tasks supported by the provider. Use this for supervised follow-up workflows rather than unsupervised outreach.

### Keep access scoped to the right account

The connection sees only what the authorized account can access. Use a firm-managed mailbox or calendar and its sharing settings to control scope.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.filed.com/reference/plugins/integrations/communications/calendly.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.