> 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/jamie.md).

# Jamie

Connecting Jamie brings your meeting summaries, transcripts and action items into Zero, matched to the calendar events they came from.

{% hint style="info" %}
**Jamie's API and webhooks are available on Jamie's Pro, Team, and Enterprise plans.**
{% endhint %}

{% stepper %}
{% step %}

### Create a personal API key in Jamie

In Jamie, open **Settings → Developers → API Keys** and create a **Personal** key. Copy it; Jamie only shows it once.
{% endstep %}

{% step %}

### Go to Settings → Connections → Notetakers and pick Jamie

Paste the API key into the first field.
{% endstep %}

{% step %}

### Create a webhook in Jamie

Copy the Webhook URL shown in Zero, then in Jamie open **Settings → Integrations → Webhooks** and click **Create Webhook**:

* Paste the Zero URL as the endpoint
* Select the `meeting.completed` event and the **Personal** scope
* Choose **HMAC-SHA256 signature** as the authentication method

Jamie shows a signing secret once after the webhook is created.
{% endstep %}

{% step %}

### Paste the signing secret into Zero and connect

Zero verifies every delivery against this secret. Choose whether Jamie action items should become Zero tasks, then click **Connect Jamie**. Zero syncs your existing Jamie meetings right away.
{% endstep %}

{% step %}

### Test the integration

Record a meeting with Jamie. Once Jamie finishes processing it, the summary, transcript, and action items appear on the matching calendar event in Zero. You can also use **Sync previous meetings** from the integration menu at any time.
{% endstep %}
{% endstepper %}


---

# 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/jamie.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.