Integrations

HubSpot

1. Open CRM integrations and choose Connect HubSpot; approve on HubSpot’s page.
2. Optionally, name a Do-not-contact property (its internal name).

• Each lead becomes a HubSpot contact at its first invitation or message, and every invitation, message and reply shows on its timeline, as it happens.
• Every night, contacts Reachpool made that have the do-not-contact property set become exclusions of the workspace, so its campaigns leave them out.

Pipedrive

Connect Pipedrive approves on Pipedrive’s page. Or connect with your own API token (Pipedrive: Personal preferences → API): your company domain, the part before .pipedrive.com, and the token, then Connect with the token. Each lead becomes a Pipedrive person at its first invitation or message, and every invitation, message and reply is a done activity on it. Nothing is read back from Pipedrive.

Either CRM

• Include the message text on the contact’s timeline: on unless you turn it off; off, the timeline only says a message was sent or received.
• Each sender can have a CRM owner, who then owns the contacts it brings.
• Connect again when the card says the connection needs it, and Disconnect to stop: what is in the CRM already stays.

Webhooks

Webhooks: an https URL, the events it takes, then Add webhook. Its signing secret is shown once. The events are: invite sent, invite accepted, message sent, message received, lead replied, lead completed its sequence, sender warning, sender restricted, conversation labeled.

A webhook’s page has Send test event, every delivery and Send again. A receiver that is down gets each event again for a day. How to check signatures, the payloads and Zapier or Make recipes are in the API docs.

API keys

In the workspace’s Settings, under API keys: a name (say, Zapier), then Make a key. Copy it then: it is not shown again. A key works in that workspace only, as the person who made it; Revoke ends it. The API docs have the rest.