Skip to content
Rainmaker
Language EN
Log inTry it free
Try it free · 7 daysPricing
Help centerUpdated · 13 min read

Integrations and CRM

Connect your CRM so the people Rainmaker talks to, and what was said, show up where your team already works. Also covers web search, notification emails and signup tracking.

Rainmaker can connect to three CRMs: HubSpot, Pipedrive and Salesforce. Once connected, the messages Rainmaker sends are logged in your CRM, and with HubSpot, leads who reply are sent over with their whole conversation and their Rainmaker status history. CRM connections live on the Integrations settings page, together with an optional web search key, your notification emails, and status rows for the services Rainmaker runs for you. Your mailbox and LinkedIn account have their own pages: see Channels: your mailbox and LinkedIn.

Where to find it and who can use it

In the sidebar, click Settings, then Integrations ("CRM connections and service status"). The page itself is titled Other integrations.

TaskOwnerAdminApproverEditorViewer
Open IntegrationsYesYesNoNoNo
Connect or disconnect a CRMYesYesNoNoNo
Turn Automatically send leads who reply to HubSpot on or offYesYesNoNoNo
Press Send to HubSpot on a leadYesYesYesYesNo
Import contacts from a CRM into a campaignYesYesYesYesNo
Add, test or remove the web search keyYesYesNoNoNo
Change Email notificationsYesYesNoNoNo
Generate a signup tracking keyYesYesNoNoNo

Approvers, editors and viewers do not see Integrations in Settings. If they open it from a link, the page shows "Your workspace role cannot perform this action. Ask an owner or admin for access." See Team and roles.

Connect a CRM

The CRM section lists your connected CRMs, or "Not connected" when there are none. Each row shows the CRM account, the CRM name and an active badge.

  1. Under CRM, click Connect HubSpot, Connect Pipedrive or Connect Salesforce.
  2. You are taken to that CRM's own sign-in and permission screen. Sign in and approve access.
  3. You come back to Integrations with "Connection authorized and ready." at the top.

A workspace has at most one connection per CRM. Connecting the same CRM again replaces the earlier connection, which is also how you reconnect.

If the connection does not go through, you come back with a red message at the top of the page instead. Common ones: "Provider denied authorization" (you clicked cancel or deny on the CRM's screen), a message that the authorization state is invalid, expired or already used (the sign-in took longer than 10 minutes, or the page was reloaded), a message that the callback is missing its state or code (the return address was cut short), a message that the token exchange returned no access token, and "Provider did not return an account identifier." In every case, click the connect button again. If clicking a connect button opens a page of plain error text instead of the CRM's sign-in screen, go back and try again; if it repeats, contact support. See Why did my CRM connection fail?

What each CRM receives

Every time Rainmaker sends a message for you (an email or a LinkedIn message from a campaign), each connected CRM is updated. People without an email address are skipped in Pipedrive and Salesforce, and in HubSpot until they have been sent over as a whole (see below).

HubSpot

  • Every sent message: the lead becomes (or updates) a HubSpot contact, and the message is logged on their timeline with its full text, as an email or a LinkedIn communication. This happens whether or not the automatic setting below is on.
  • Leads who reply: with Automatically send leads who reply to HubSpot on, Rainmaker sends the whole lead to HubSpot as soon as they reply by email or LinkedIn. That includes:
    • the contact (name, title, email, LinkedIn profile, country, website);
    • the company, found by its website domain, with the contact linked to it;
    • the whole conversation in order: every email sent and received, every LinkedIn message, and your own answers;
    • Rainmaker's status history, one note per step, for example "Rainmaker: replied — 2026-10-06 14:32 UTC (campaign Q4 outreach)". The steps are added to a campaign, contacted, replied, meeting booked, meeting cancelled, meeting held, opted out and signed up. Earlier history is filled in on the first sync;
    • one Rainmaker lead context note with the campaign, fit score, the sources Rainmaker used and an Open this lead in Rainmaker link. It is updated in place, never duplicated.
  • Lead status: on a first real reply (not an out-of-office), HubSpot's lead status moves to In progress, but only if it was empty or New.
  • Later changes follow automatically: your answers, a meeting booked or cancelled, and, an hour after a meeting's start time, whether it counts as held.
  • Optional custom fields: if HubSpot allowed Rainmaker to create custom properties when you connected, the contact also gets Rainmaker status, Rainmaker campaign and Rainmaker fit score in a Rainmaker group. If not, this step is skipped quietly; everything else still works.

Nothing is created twice. Sending the same lead again only adds what is missing.

Pipedrive

For each sent message, Rainmaker finds or creates the person in Pipedrive by email address and adds a task activity titled "[Rainmaker]" with the email's subject line.

Salesforce

For each sent message, Rainmaker finds or creates a Salesforce Lead by email address and adds a Task with the email's subject line. Salesforce sign-ins are refreshed automatically when they expire.

Pipedrive and Salesforce do not receive the full conversation or the status history.

The HubSpot sync setting

When HubSpot is connected, the CRM section shows a checkbox: Automatically send leads who reply to HubSpot. It is on by default, including for workspaces that connected HubSpot before the setting existed. Below it: "Sends their details, company, every email and LinkedIn message, and their Rainmaker status history." followed by Last sync with a date and time, or Not synced yet.

Turning it off stops reply-triggered syncs, including ones already queued. Sent messages are still logged on the contact, and Send to HubSpot still works.

If the last sync failed, a red notice appears:

  • HubSpot needs to be reconnected, with "Reconnect HubSpot to allow conversation sync." and a Reconnect HubSpot button. Your HubSpot connection is missing a permission conversation sync needs, usually because it was connected before this feature existed. Click Reconnect HubSpot and approve again.
  • Last HubSpot sync failed, with "HubSpot sync failed:" and the reason. The next reply or a manual Send to HubSpot tries again and fills in whatever is missing. If the reason says the credential expired without a refresh token, that no active HubSpot credential exists, or "Credential has been revoked." / "Credential not found for this workspace.", reconnect HubSpot with Connect HubSpot.

If saving the checkbox fails, you see "The HubSpot setting could not be saved."

Send a lead to HubSpot by hand

When HubSpot is connected, Send to HubSpot appears in two places: the ⋯ menu at the top of a conversation in the Inbox, and as a button in the lead's detail panel. It sends the same full package as the automatic sync, for any lead, whether or not they replied and whether or not the setting is on.

  • While it works it reads "Sending to HubSpot…".
  • On success you see "Sent to HubSpot." with View in HubSpot (in the Inbox, just under the ⋯ menu), and the option becomes Send again. Pressing it again is safe: anything already in HubSpot is skipped.
  • On failure you see one of: "Reconnect HubSpot to allow conversation sync.", "Connect HubSpot in Settings → Integrations first." (HubSpot is no longer connected; it now lives under Integrations), or "This lead could not be sent to HubSpot. Try again in a moment."

Owners, admins, approvers and editors see it. Viewers do not.

Import contacts from a CRM into a campaign

You can bring existing contacts from HubSpot or Pipedrive into a campaign from that campaign's Leads page. Salesforce import is not available. Connect the CRM here first.

On the Leads page toolbar, pick HubSpot or Pipedrive, then change the country choice from Country unconfirmed to US confirmed (imported contacts are treated as US contacts), and click Import CRM. The button stays greyed out until the country is confirmed, while an import runs, or if your role cannot change campaigns. If the import fails you see "Contacts could not be imported from HubSpot. Confirm the integration is connected." (or Pipedrive). If it worked but the list could not refresh: "Contacts were imported from HubSpot, but the refreshed lead list could not be loaded. Reload the page to confirm the latest state." Imported contacts go through the same checks as any other lead. The leads table is described in Leads and companies.

Disconnect a CRM

Click the bin icon (Disconnect integration) on the CRM row. A window titled Disconnect integration? asks, for example: "Disconnect "Acme portal"? Touch logging to this CRM stops immediately. Reconnecting requires authorizing again." (A touch is one message Rainmaker sends.) Click Disconnect. You will see "Disconnected" with the account name, or "Connection could not be disconnected." if it failed.

Disconnecting stops all logging and syncing to that CRM. Records already in your CRM stay there. To connect again, use the connect button and approve access again.

Web search key

The Web search section is optional. When a key from a web search service is set, Rainmaker can use live web search to answer factual questions prospects ask in their replies. Without a key, Rainmaker uses its built-in web research instead, so nothing stops working. Every answer still has to be backed by a source.

  • The badge reads Key set or Not set.
  • To add a key, paste it in the field and click Save key ("Web search key saved."). The key must be at least 8 characters.
  • Once set, only the last four characters are shown. Click Test search to check it: "Test OK" with the number of results for a sample search, or "Test failed" with the reason. Reasons include the service rejecting the key, the account's quota or rate limit being used up, the service not responding in time, an error code from the service, an unexpected answer, a network problem, or no key being set. "Test failed — the request did not complete." means the test itself could not run; try again. When the reason can't be shown, it reads "Test failed — the search service did not accept the key or did not answer. Check the key and try again."
  • If saving says a key is required, paste one first. If it says the key changed at the same time ("Web search key changed concurrently"), someone else edited it: refresh and try again.
  • Click Remove to delete it. The confirmation asks "Remove the web search API key? Reply research falls back to Rainmaker's built-in web search." You will see "Web search key removed."

Email notifications

The Email notifications section on this page controls the emails Rainmaker sends to you (not to prospects): the Recipient address, Email me when a prospect replies or books a meeting, and Product tips and reminders (drafts waiting for review, setup steps, trial follow-ups). Click Save email preferences. You will see "Email notification preferences saved." What each email contains is explained in Your account and workspace.

Status rows for Rainmaker's services

The top of Integrations shows status rows for services Rainmaker runs for you: Contact sourcing (people discovery, email discovery, email verification), Web discovery (reading public web pages), Company intelligence and Research and writing. Each shows Ready, Setup required or Missing, and some show counts. These are managed by Rainmaker, not by you: there is nothing to enter here. If one shows Setup required and a feature you need is blocked, contact Rainmaker support. You can always import a CSV from a campaign meanwhile. Open web discovery opens the Web discovery settings page, described in Settings.

Signup tracking for signup campaigns

A campaign whose goal is Drive account signups can tell Rainmaker when someone creates an account on your product, so the signup is credited to the right campaign. Open the campaign, go to its Settings tab, choose Goal and find Signup tracking. The same panel appears as the optional Connect your signup source step when you create campaigns.

When signup tracking is missing, the campaign's overview shows Campaign goal needs setup with "Signup tracking not connected — signups can't be attributed. Connect your signup source below." (and "Signup link not configured — replies can't steer anywhere." when the signup link is empty). When a contacted lead signs up, the notification bell shows, for example, "Alex Martin created an account."

At the top, a badge shows Last signup event received: with a time, or never. "(includes test events)" reminds you that test events count. Send test event checks Rainmaker's side only: "Test event sent — proves Rainmaker's side only; a real signup on your site must trigger your server's call." If some signups arrived from people Rainmaker never contacted, you see the count as "unmatched signups (organic — never contacted, not attributed to a campaign)".

Four tabs offer four ways to connect:

  • Website snippet: a short script to paste once in your site's page header, like an analytics tag. It reports form submissions that contain an email field. Click Copy snippet. This is marketing-grade tracking. Until your workspace's key loads, the snippet shows a placeholder key.
  • Server hook: code for your own server to call the moment an account is created ("This runs on your server, not your website": it needs the new user's email and your secret key, which must never appear in a public page). Click Generate signup tracking key, copy the key ("Copy this key now — it will not be shown again"), then copy the code for Node, Python or PHP. Until you generate a key, the code shows a placeholder.
  • Auth providers: an address to paste into your sign-in provider's "on user created" setting.
  • No-code / forms: an address and a request body for form tools and automation services, plus a signup tracking key and Which field is the email?.

Generating a key needs an owner or admin. If you see "This workspace has reached its active-key limit", an existing key must be revoked first; contact support if you cannot find where. Campaign goals are described in Campaigns.

Statuses and messages

Status or messageWhereWhat it meansWhat you can do
activeCRM rowThe CRM is connected.Nothing.
"Not connected"CRM sectionNo CRM connected.Click a connect button.
"Connection authorized and ready."Top of pageA CRM connection just succeeded.Nothing.
Last sync / Not synced yetHubSpot settingWhen HubSpot last received data from Rainmaker.Nothing.
HubSpot needs to be reconnectedHubSpot settingA permission is missing.Click Reconnect HubSpot.
Last HubSpot sync failedHubSpot settingThe last sync hit an error.Read the reason; the next sync or Send to HubSpot retries.
Key set / Not setWeb searchWhether a web search key is saved.Optional.
Ready / Setup required / MissingStatus rowsWhether a Rainmaker-run service is available.Contact support if it blocks you.
Last signup event received: neverSignup trackingNo signup has reached Rainmaker yet.Finish one of the four setups, then Send test event.

Troubleshooting

Questions about integrations and crm

Still stuck?

Search the troubleshooting answers, or follow a step-by-step tutorial with screenshots.