> ## Documentation Index
> Fetch the complete documentation index at: https://heybtw.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# set_crm_of_record

> Save which CRM this workspace's team uses, so no later session and no teammate is asked again.

> [!WARNING]
>
> Writes to your heyBTW workspace: it saves the name of the CRM your team uses. It is a label only. heyBTW reads no CRM through it, writes to no CRM and no figure in heyBTW changes.

heyBTW works next to whatever CRM you have connected in Claude. set\_crm\_of\_record remembers which one that is, for every member of the workspace, so the question is asked once.

Follows the [heyBTW MCP rules](https://heybtw.com/docs/mcp/rules.md).

## When to use it

Use it when `crm_context.agent_guidance` says the CRM is not recorded and the user has asked for an owner, a deal or activity. Save what you found or what the user said.

* "We use Pipedrive."
* "Who owns the accounts that came to the Austin dinner?" (and no CRM is recorded yet)

## Parameters

| Parameter | Type | Required | Notes |
| - | - | - | - |
| `name` | string | Yes | The CRM's product name as the user or the connector states it. At most 60 characters. No link, email address or key. |
| `source` | string | Yes | `detected` (the one connector in your client that searches contacts, companies or deals) or `user_stated` (the user named it). `dashboard` is refused. |
| `client_request_id` | string | Yes | A fresh hyphenated UUID for each new write. Reuse it only to retry that same write. |
| `contract_version` | string | No | Omit for v1, the only version advertised. |

## What it changes

Every CRM-dependent tool then serves `crm_context.crm_of_record` for every member of the workspace.

A call appends a new version and keeps the prior one. If the saved CRM's connector stops answering, or the user names another CRM, save the new one instead of asking again later.

A CRM connected inside heyBTW is recorded by heyBTW itself and always outranks a saved record. That is why `source: "dashboard"` is refused here.

## Rules the agent must follow

* Save a CRM only after the user asked a CRM question. Finding the CRM is separate from setting up an event.
* Save the product name only. Never save a link, an email address or a key.
* Do not write CRM facts (deal stage, owner, amount) into heyBTW. The CRM stays the source.

## Retry safely

On a transport error, retry with the same `client_request_id`. A committed write is replayed (`idempotent_replay: true`), never repeated.

## Errors and gaps

* `invalid_parameter`: `name` is empty, too long or carries a link, email address or key; `source` is not `detected` or `user_stated`; or `client_request_id` is missing or malformed.
* `insufficient_scope`: the sign-in lacks write access. Nothing is saved. Reconnect and approve write access on the consent screen.
* `rate_limit_exceeded`: wait for `Retry-After`. See [Limits and errors](https://heybtw.com/docs/mcp/limits-and-errors.md).

Writing needs no plan: every workspace can write.

## Related

* [get\_workspace\_overview](https://heybtw.com/docs/tools/get-workspace-overview.md): `crm_context` and the two routes to a CRM.
* [Works with any CRM](https://heybtw.com/docs/playbooks/works-with-any-crm.md): which numbers come from heyBTW and which from your CRM.
* [Connect your CRM and event platform](https://heybtw.com/docs/playbooks/connect-crm-and-event-platform.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.