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

# The crm_contact block

> What Groovin knew about this person in your CRM when the event was sent.

Both events carry a `crm_contact` block, so you often do not need a second call to know who this person is in your CRM.

| `status` | Meaning |
| - | - |
| `paired` | Already linked in Groovin (checked against your CRM for Attio and HubSpot) |
| `matched` | Found in your CRM and linked by Groovin now |
| `created` | Created in your CRM by Groovin now (`crm_contact_auto_created: true`) |
| `not_found` | No CRM contact found. For a received message, Groovin only searches by LinkedIn URL, so the person can still be in your CRM without one |
| `ambiguous` | Several CRM contacts match: see `matched_crm_contact_ids` |
| `not_checked` | Unknown: automatic creation is off, the profile is blocked from creation, or the CRM (Affinity) has no link yet |
| `unavailable` | Your CRM could not be reached or checked, or Groovin's processing failed first (`crm_contact_id` is then the last known link, if any). Use [Check who is already in your CRM](https://docs.groovin.ai/reference/api/lookup-contacts.md) later |

## Fields

* `is_msg_sync_enabled`: whether Groovin logs this conversation in your CRM. `false` when there is no CRM contact, `null` when unknown.
* `auto_create_outcome`: the [`crm/contacts`](https://docs.groovin.ai/reference/api/create-contacts) outcome when Groovin tried to create the contact.
* `matched_crm_contact_ids`: only with `ambiguous`, up to 10. `null` otherwise.
* `crm_contact_id` and `crm_url`: `null` for `not_found`, `ambiguous` and `not_checked`. `crm_url` is also `null` when Groovin cannot build a link to the record.
* `already_paired_in_groovin`: `null` when it could not be read.

## Fields that can be null or empty

Besides those above: `groovin_user.email` and `name`, `linkedin_account.name`, `contact.name`, `contact.slug`, `contact.profile_url`, `contact.picture_url`, `message.subject`, `message.quoted`, and, rarely, `message.provider_id`.

`message.text` can be empty, but is never `null`. `conversation_id` and `message.id` are always text, but can be empty (`""`) in the rare case LinkedIn's data lacks them.

`contact.linkedin_profile_id`, `slug`, `profile_url` and `is_crm_contact_creation_blocked` are `null` when only a Sales Navigator profile id is known.


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