Integrations and API

How do you connect cold email to your CRM, such as HubSpot or Pipedrive?

By the anymail team ·
Short answerConnect the CRM with an API token or a sign-in, choose the list or filter that feeds a campaign, map the fields and switch on the automations you want. Contacts flow in as prospects. Only people who replied flow back out, as a contact, a note and a deal in your pipeline.

A cold email tool and a CRM answer different questions. The tool knows who you wrote to and who answered. The CRM knows what happens to a deal. Connecting them removes the copying between the two, as long as you decide which events are worth a record in the CRM.

What should flow between the two systems?

Data moves in two directions, and they deserve separate decisions.

Direction What happens Typical use
Into the campaign Contacts from a CRM list or filter arrive as prospects and are enrolled in a campaign Writing to a segment your team already maintains
Back to the CRM A reply becomes a contact, a note and a deal that is created, moved or closed Giving the salesperson the context where they already work

The inbound direction is read-only towards the CRM. anymail reads the list and changes nothing in it.

For the outbound direction, the useful rule is the one anymail applies: a person who never answered is never written to the CRM. A CRM full of cold addresses is a worse database, and your own reports begin to mean less.

Which CRMs connect natively?

The native connectors are HubSpot, Pipedrive, Salesforce, Attio, monday.com, Keap and Insightly. The catalogue on the integrations page shows the status of each connector. Only the ones marked available are described here.

The connection method differs by CRM:

  • HubSpot: a private app token that starts with pat-. The connection screen names the scopes to grant and checks them.
  • Pipedrive: a personal API token, or a sign-in through Pipedrive where your installation has it enabled.
  • Salesforce: a sign-in, with a choice between production and sandbox. You also choose whether a reply becomes a Lead or a Contact.
  • Attio and monday.com: an API token. anymail reads your own objects, boards and columns and asks which ones to use, because workspaces rename their stages.

How do you connect HubSpot or Pipedrive, step by step?

  1. Open the connection screen. In the app, go to Settings, then Integrations, and pick the CRM.
  2. Paste the token or sign in. For HubSpot, create a private app first and grant the scopes the screen lists. A key in the old eu1- format no longer works.
  3. Choose the inbound source. Pick the HubSpot list or the Pipedrive filter that should feed a campaign, and the campaign it enrols into.
  4. Map the fields. A field you do not map is skipped. It is never guessed.
  5. Switch on the automations. Every automation is off until you enable it.

After the last step, wait for the first real reply and open the sync log on the connection screen. The log shows each write, so an outage on the CRM side is visible without server access.

What do the automations do?

There are six per CRM, and each one is a single rule you can turn on or off:

  • A list or filter adds contacts to a campaign.
  • An interested reply adds a note and creates a deal, or moves the one that exists.
  • A reply read as maybe later adds a note and updates an existing deal. It never creates one.
  • A reply read as a no adds a note and closes the open deal as lost.
  • A bounce or an unsubscribe adds a note and writes a value you chose into a field you picked.
  • An open or click adds a note. It is off by default.

Be sceptical of the last one. Opens are unreliable because Apple Mail Privacy Protection loads the tracking pixel whether or not a person read the message. Clicks are a firmer signal. A note for every open fills the CRM with noise.

What are the limits?

  • Notes carry the fact, the classification, the address and the time. They never carry the message.
  • If a token expires, writes queue and drain after you reconnect. A reply is not lost silently.
  • The classification of a reply decides what happens to the deal, and a classification can be wrong. Review the deals the first week.
  • A CRM without a native connector needs the REST API, a webhook or Zapier. That works for most tools, but you build the rule yourself.

What if your CRM is not on the list?

Use the API and webhooks. The REST API adds and updates prospects from any language. A signed webhook sends an event to your URL when a message is sent, a prospect replies, someone clicks, an address bounces or someone unsubscribes. Zapier can sit between the two with no code.

How does anymail handle the CRM side?

anymail keeps the sequence, the replies and the company timeline in one place and writes only conversations to your CRM, so the deal in HubSpot or Pipedrive starts from a person who answered. The integrations page lists every connector and its status.

Frequently asked questions

Does every cold address end up in my CRM?

No. Only a prospect who replied is written to HubSpot, Pipedrive and the other native connectors. Addresses that never answered stay out, so your contact base remains a record of conversations.

Does the note in the CRM contain the reply?

No. The note records the fact of the reply, how it was classified, the address and the time. The message text stays in anymail.

Which direction does data flow?

Both. A list or filter in the CRM can feed a campaign, which is read-only towards the CRM. Replies, bounces and unsubscribes then flow back as contacts, notes, deals and a marked field.

What if my CRM has no native connector?

Use the REST API and signed webhooks, or Zapier. Anything that can send an HTTPS request can add a prospect, and anything that can receive one can be told when a prospect replies.

See which companies are warming up.

Start free trial