> 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/garba.md).
# Garba
Connecting Garba brings your meeting summaries, transcripts and action items into Zero. It polls hourly by default; adding the optional webhook makes summaries arrive the moment they are ready.
## Connect Garba
Go to **Settings → Connections → Notetakers** (the **Meeting notetakers** page) and click the **Garba** tile under **Available notetakers**.
{% stepper %}
{% step %}
### Copy your Garba API token
Open [Garba](https://app.garba.ai) and copy your Garba API token — the token Garba issues for its [External API](https://api.garba.ai/docs).
{% endstep %}
{% step %}
### Paste the token
Paste the token into the field in Zero.
{% endstep %}
{% step %}
### Optional: configure a webhook
Zero also polls Garba hourly. A webhook syncs summaries as soon as they are ready. Garba allows one webhook per account, so this replaces any existing Zapier or custom webhook (see the [Garba webhook docs](https://help.garba.ai/en/articles/10742496-webhook-integration)).
1. Open [Garba Settings → Integrations](https://app.garba.ai)
2. Click `+ Add Webhook` on the Webhook card
3. Paste the webhook URL shown in the Zero setup wizard and connect. Garba sends a test request immediately.
{% endstep %}
{% step %}
### Choose whether action items become tasks
The **Turn Garba action items into Zero tasks** toggle is on by default. Leave it on to have Zero create tasks from your meetings; turn it off to sync only summaries and transcripts.
{% endstep %}
{% step %}
### Connect
Click **Connect Garba**. The button is enabled once a token is pasted.
{% endstep %}
{% endstepper %}
## How syncing works
* **Hourly poll**: every hour, Zero fetches your Garba meetings created in the last 2 days.
* **Webhook (optional)**: when Garba finishes a meeting summary, it notifies Zero and that meeting syncs immediately.
* Only meetings belonging to the connected Garba user are synced.
* Each Garba meeting is matched to a calendar event by exact title and a start time within 30 minutes of the event. If several events match, the one closest in time is used. Meetings without a matching calendar event are not attached to your calendar.
When a meeting matches a calendar event, Zero:
* Adds the Garba summary to the calendar event's notes (existing notes and summaries are never overwritten)
* Imports the meeting transcript
* Creates Zero tasks from the meeting's action items — or, if the meeting has no action items, extracts tasks from the summary (only when **Turn Garba action items into Zero tasks** is enabled)
## Manage the integration
Your connected Garba integration appears at the top of the **Meeting notetakers** section, with its sync status and last sync time. From there you can:
* **Sync last 7 days** — re-fetch meetings created in the last 7 days
* **Sync previous meetings** — fetch your full Garba meeting history
* Update the API token or copy the webhook URL from the integration's settings
* Disconnect the integration — meeting transcripts and summaries will no longer be synced with Zero
Triggering a manual sync requires being the integration's owner or a workspace admin.
---
# 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/garba.md?ask=&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.
