> For the complete documentation index, see [llms.txt](https://threadly.gitbook.io/threadly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://threadly.gitbook.io/threadly/integrations/other-integrations.md).

# Other Integrations

## Calendly

Add a Calendly booking link as a CTA button in any message. Recipients can click to see your availability and book a meeting without leaving Slack.

**Setup:** In the message composer, add a CTA button and paste your Calendly link as the URL. No special configuration needed.

## Cal.com

Same as Calendly — use a Cal.com link as a CTA button URL. Cal.com is an open-source scheduling alternative.

## SavvyCal

For group scheduling, paste a SavvyCal link as a CTA button URL.

## Attio

Attio is a CRM platform. With the Attio integration, you can create [Smart Segments](https://github.com/zevzoldan/broadcastbeam/blob/claude/improve-gitbook-docs-R7rJF/docs/channel-groups/smart-segments.md) that filter channels based on Attio record properties.

**Setup:** Go to **Settings → Integrations** and authorize the Attio connection via OAuth.

## Planhat

Planhat is a customer success platform. Connect it to build smart segments that reflect your customer health data and lifecycle stages.

**Setup:** Go to **Settings → Integrations** and enter your Planhat API credentials.

## Notion

Link directly to Notion pages from CTA buttons. No integration setup required — simply paste a Notion page URL as the button destination.

## Intercom & Zendesk

Intercom and Zendesk data can be surfaced in Threadly for segment building and workflow triggers. Contact <support@trythreadly.com> for setup assistance with these integrations.


---

# 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://threadly.gitbook.io/threadly/integrations/other-integrations.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.