Instance · CRM
Contacts Introduction
Last updated 1 November 2026
Contact records in the CRM: details, companies, custom fields, archiving and webhooks.
A contact is a person in your CRM: a customer, a lead, a supplier or anyone else you deal with. Each contact holds their name, email, phone, addresses and custom fields, and can be linked to a company. Tasks, activities and attachments on a contact keep the history of your dealings with them.
What you can do with contacts
| Job | Where |
|---|---|
| Add a contact | Adding a contact |
| Edit, archive and restore contacts | Managing contacts |
| Import or export contacts | Importing and exporting contacts |
Fields you can shape
Dropdowns such as contact type, contact category and lead source come from system fields, which you change in CRM system fields. Add your own fields as custom fields under the contacts configuration in CRM custom fields.
Archive and restore
Archiving removes a contact from the active list and keeps their history. Restoring brings them back. Through the CRM API these are POST requests to /crm/api/v2/contacts/:uuid/archive and /restore; a PATCH to those addresses is refused.
Contacts are users
Each CRM contact is stored as a user with a CRM contact profile. Fields such as first name, last name and email are on the user, and fields such as job title are on the profile. A developer reading contacts with GraphQL needs to know this; see Build an app on top of the CRM.
The CRM sends a webhook when a contact is created or updated.
Common mistakes
- Creating a second contact with the same email. Search first, and update the existing one.
- Deleting a contact to hide them. Archive them, so their history stays.
- Typing a new lead source on a contact. Lead sources are managed in system fields.