Documentation version: 2026-11-16.2
Canonical: https://docs.creator.gg/tools/crm_relations_link.md

# crm_relations_link

Review an explicit custom relationship link intent after verifying both records, account, object order and user-defined association. Currently returns a native handoff without writing: the current relation response schema omits verifiable linked-record identity. Native many-to-many links are supported; read guides/data-ingestion for native UI and direct API routes. Never replaces Primary Company. Linking natively may trigger workflows. Reuse the same requestId when retrying an uncertain operation.

## Execution

Call this MCP tool at https://mcp.creator.gg/mcp. The connection selects the workspace. A tool name is not a REST route.

Effect: changes workspace data. requestId is required by the service (8–128 characters); reuse it only for the same action and arguments.
This action has destructive or external-delivery effects. Resolve the user's requested scope before execution.

## Behavior and limits

Currently no provider write is dispatched. Both references must be owned, align with the association first/second object keys and use a user-defined non-Primary Company label. The incomplete relation-response schema produces CRM_RELATION_CONTRACT_UNAVAILABLE; missing cardinality metadata is not a ban on many-to-many links. requestId retains this intent and its body-free handoff receipt, not permission to create a link. Linking in the native account can start workflows.

## Example arguments

Examples illustrate the schema. Replace placeholder IDs with workspace IDs and recalculate dates. For mutations, use a new requestId for each new action and retain it for identical retries.

```json
{
  "associationId": "association_example",
  "first": {
    "objectKey": "contact",
    "recordId": "contact_example"
  },
  "second": {
    "objectKey": "business",
    "recordId": "company_example"
  },
  "requestId": "example-crm_relations_link-001"
}
```

## Input schema

Generated from the executable tool contract. The behavior notes and related guide cover rules that JSON Schema cannot express.

```json
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "associationId": {
      "type": "string",
      "minLength": 1,
      "maxLength": 128,
      "pattern": "^[A-Za-z0-9_-]+$"
    },
    "first": {
      "type": "object",
      "properties": {
        "objectKey": {
          "type": "string",
          "maxLength": 160,
          "pattern": "^(contact|business|opportunity|custom_objects\\.[a-z][a-z0-9_]{0,99})$"
        },
        "recordId": {
          "type": "string",
          "minLength": 1,
          "maxLength": 128,
          "pattern": "^[A-Za-z0-9_-]+$"
        }
      },
      "required": [
        "objectKey",
        "recordId"
      ],
      "additionalProperties": false
    },
    "second": {
      "type": "object",
      "properties": {
        "objectKey": {
          "type": "string",
          "maxLength": 160,
          "pattern": "^(contact|business|opportunity|custom_objects\\.[a-z][a-z0-9_]{0,99})$"
        },
        "recordId": {
          "type": "string",
          "minLength": 1,
          "maxLength": 128,
          "pattern": "^[A-Za-z0-9_-]+$"
        }
      },
      "required": [
        "objectKey",
        "recordId"
      ],
      "additionalProperties": false
    },
    "requestId": {
      "description": "Required by the Creator Platform service for mutations: a stable 8–128 character identifier. Reuse on retries; change for a new action.",
      "type": "string",
      "pattern": "^[A-Za-z0-9_.:-]{8,128}$"
    }
  },
  "required": [
    "associationId",
    "first",
    "second"
  ],
  "additionalProperties": false
}
```

## Result interpretation

Inspect status, message and operation-specific data; list and record shapes vary. A completed read or accepted request does not prove delivery or publication. Reconcile unknown outcomes. HUMAN_ACTION_REQUIRED returns instructions without performing the action.

## Related guides

- [crm-relationships](https://docs.creator.gg/guides/crm-relationships.md)
- [Recovery](https://docs.creator.gg/guides/recovery.md)


## Import and sync data

For initial import/backfill or ongoing ingestion of new users/people, companies and many-to-many memberships, read [Import and sync data](https://docs.creator.gg/guides/data-ingestion.md). It distinguishes field definitions from values, stable external IDs from changed emails, native webhook/API routes from Creator MCP, and actual writes from handoffs.
- [Email subscription preferences](https://docs.creator.gg/guides/email-preferences.md)
