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

# Integrations

Connect third-party tools to extend Mochi's capabilities.

## Calendly

When Calendly is connected, Mochi automatically moves leads to **Booked Call** when they book a call. No manual stage updates needed.

### Setup

{% stepper %}
{% step %}
Go to **Settings → Integrations**
{% endstep %}

{% step %}
Click **Connect Calendly** and authorize
{% endstep %}

{% step %}
Select which event types your setters can send (discovery calls, strategy sessions, etc.)
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Requirement: Calendly Standard plan or higher. The Free plan doesn't support API integration.
{% endhint %}

### Connection Modes

Mochi supports two Calendly connection modes:

* **Per organization** — One Calendly account for the whole team. All bookings route through a single calendar.
* **Per member** — Each team member connects their own Calendly. Setters send their assigned closer's booking link.

Switch between modes in Settings → Integrations.

### How Booking Tracking Works

**Links sent from Mochi (automatic):**\
When a setter sends a Calendly link through Mochi's interface, tracking data is embedded automatically. The booking updates the lead's stage to Booked Call.

**Links sent outside Mochi (requires setup):**\
If leads book through your bio link or other sources, Mochi can still match them — but you need to add a question in Calendly asking for their Instagram username. **Use the word "Instagram" in the question text** so Mochi can identify it.

### Troubleshooting Calendly

<details>

<summary>Was the link sent from inside Mochi? (Copied links don't track)</summary>

If the link was copied and sent outside Mochi, tracking data won't be embedded and the booking won't automatically update the lead's status.

</details>

<details>

<summary>Is Calendly still connected? Check Settings → Integrations</summary>

Ensure the Calendly connection is active in Settings → Integrations; if it's disconnected, bookings won't sync.

</details>

<details>

<summary>For external bookings: Does your Calendly form include an "Instagram" question?</summary>

External bookings require a Calendly question that includes the word "Instagram" so Mochi can match the booking to the lead.

</details>

<details>

<summary>Did the lead enter the correct Instagram handle?</summary>

If the handle entered doesn't match the lead's Instagram, Mochi cannot link the booking to the lead.

</details>


---

# 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://themochi-app.gitbook.io/mochi-docs/feature-and-settings/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.