> For the complete documentation index, see [llms.txt](https://docs.zero.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zero.inc/settings/call-recorders/circleback.md).

# Circleback

Connecting Circleback puts your meeting notes, transcripts and action items on the calendar events they belong to — and turns the action items into Zero tasks, so nothing agreed on a call depends on someone remembering it.

## Set up the integration

{% stepper %}
{% step %}

### Open the Circleback setup in Zero

Go to **Settings → Connections → Notetakers** (the **Meeting notetakers** page). Under **Available notetakers**, click the Circleback tile.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/notetaker-picker.png" alt="Meeting notetakers picker showing eight selectable notetaker services as logo cards in a two-column grid"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Set up an automation for new meetings

The setup wizard shows your personal webhook URL. In Circleback:

1. Open [Circleback Automations](https://app.circleback.ai/automations) and click `+ New automation`.
2. In the "Trigger" section, click `Run after every meeting`.
3. In the "Choose what happens" section, select `Send webhook request`.
4. Paste the webhook URL from the Zero setup wizard into the `Endpoint` field.
5. Under the "What to include" section, check `Meeting notes`, `Action items`, and `Transcript`.
6. Save the automation.

No signing secret needed. Once the automation is live, every new meeting summary reaches Zero on its own.

<figure><img src="https://storage.googleapis.com/zero-production-api-docs/images/circleback-setup.png" alt="Circleback notetaker setup with numbered automation steps, a placeholder webhook URL, a task toggle and a connect button"><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Choose whether action items become tasks

The **Turn Circleback action items into Zero tasks** toggle is on by default. Turn it off if you only want notes and transcripts.
{% endstep %}

{% step %}

### Connect your Circleback account

Click **Connect Circleback** and authorize Zero. This step is required — it is also what back-syncs your previous transcripts. Circleback then appears under **Connected** on the Meeting notetakers page.
{% endstep %}
{% endstepper %}

## What syncs

* **Meeting notes** are attached to the matching calendar event in Zero as the event summary.
* **Transcripts** are stored on the calendar event, segmented by speaker.
* **Action items** are converted into Zero tasks when the "Turn Circleback action items into Zero tasks" toggle is on.
* **Previous meetings** are back-synced once after you complete the "Connect Circleback" authorization step.

Matching runs in three passes: calendar invite ID, then meeting link (Zoom, Google Meet or Microsoft Teams), then meeting name plus a start time within an hour. Anything that matches nothing is still stored in Zero.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zero.inc/settings/call-recorders/circleback.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
