PristineSend's CRM keeps your companies, deals, notes and tasks beside the contacts you email. This page is about using it from your own code and from your own AI. In PristineSend it lives in Audience → Companies and Pipeline.
The CRM is connected to the rest of PristineSend. Segments can choose contacts by their company, deals and replies. Replies can reach the pipeline. A deal entering a stage can start an automation.
Someone in the team turns the CRM on once, in Audience → Companies, and sets up the pipeline in Pipeline. Until the CRM is on, every CRM request is refused with 403 crm_not_enabled, and so are deal and pipeline requests until the pipeline exists. The stages, the company properties and who is in the team are set in PristineSend; the API reads them.
Two scopes, given to an API key or a connected AI in Settings → Developer: Read the CRM (crm:read) to look, and Edit the CRM (crm:write) to change. Edit the CRM is never part of the default access new agents get: it can delete companies and deals, which nothing brings back, and move deals into stages, which can start automations that send email. So a person gives it, to each agent that needs it.
| Reference | What it covers |
|---|---|
| Companies | List, read, create, change and delete companies. |
| Deals and pipeline | Read the stages and the team; create, change, move and delete deals. |
| Notes and tasks | Write notes; list, create, finish and change tasks, the reply tasks included. |
| Timeline and search | Everything that happened with a record, and a search across the CRM. |
| Contacts | Every contact carries company_id, and PATCH changes it. |
Every change counts against the CRM's own limit of 120 a minute per account, beside your key's limit (Rate limits). A change to a deal or a task names the updated_at it read and lands only on that version, so two people, or a person and an AI, never overwrite each other. The SDK has every endpoint as companies, deals, pipeline, notes, tasks, timeline and crm.search.
Connect your own AI, Claude for example, as the MCP guide says, and it can work in your CRM with you through these tools. PristineSend runs no AI model for any of them. They are listed to your AI only once your account has the CRM on, and none of them deletes anything.
| Tool | Scope | What it does |
|---|---|---|
search_crm | crm:read | Find companies (by name or domain), deals (by name) and contacts (by address or name) in the account's CRM, at most 8 of each. Read one with get_crm_record. |
get_crm_record | crm:read | Read one contact, company or deal (give one id) and its timeline, newest first: emails, replies, signups, deal history, notes and tasks. With cursor, the timeline's next page only. |
get_pipeline | crm:read | Read the pipeline: its currency, its stages in order (ids for save_deal's stage_id) and the team, by the emails save_deal and save_crm_task take. |
list_crm_tasks | crm:read | List tasks, newest first. kind "reply" with status "open" lists replies waiting for an answer: who wrote, when, the subject of the email they answer, and sorting's label and line. Read the reply itself in the user's inbox, answer there (a draft unless asked to send), then finish the task with save_crm_task and log the answer with add_crm_note (kind email). |
save_company | crm:write | Create a company (a name or a domain), or change one by id: its name, domain or property values. Contacts at its domain join it while the account links by domain. |
save_deal | crm:write | Create a deal (a name, and a stage from get_pipeline, else the first open stage), or change one by id and the updated_at you read: its fields, or move it with stage_id (lost_reason for Lost), not both at once. A deal entering a stage can start an automation. |
add_crm_note | crm:write | Write a note on one contact, company or deal (give one id): a note, a call, a meeting, or an email, such as an answer to a reply you sent from the user's inbox. |
save_crm_task | crm:write | Create a task (a title; about one contact, company or deal, or none), or change one by id: done true or false, or its title, due date or assignee with the updated_at you read, not both at once. |
Things you can ask it:
When replies reach your pipeline, each real reply gives someone a task to answer it, and the reply itself is forwarded to your inbox. If your AI can also reach that inbox, through its own connection to your email such as Claude's Gmail connector, it can help you answer:
list_crm_tasks with kind reply and status open: who wrote, when, and which of your emails they answered.save_crm_task finishes the task, and add_crm_note with kind email notes the answer on their timeline.The answer goes from your own mailbox, so the conversation stays there. PristineSend never sends it, never sees it, and keeps no copy of the reply's words. Someone who asked to stop is unsubscribed only when a person presses Unsubscribe them in PristineSend.
Three events tell your system what happened, each chosen per endpoint in Settings → Webhooks: deal.created, deal.stage_changed (Won and Lost included) and email.replied (someone replied to a tracked email). A deal event carries the deal as the API reads it. See Webhooks.
The CRM has no test copy: a ps_test_ key reads and changes your real records. It cannot create a deal or move one to another stage, because that can start an automation that sends real email; those need a ps_live_ key.
A deal's history, a note's author and a task say who made each change: an API key by its name (“The API key ‘Zapier’”), and a connected AI by the person who connected it (“An AI connected by Sam”). Name your keys for what uses them.