How to connect Zapier, Lemlist, Pipedrive, or HubSpot
|The MagicPost Leads module can send your leads to an outbound or CRM tool: a webhook for Zapier, Make or n8n, Lemlist, ReachBoost, Pipedrive, or HubSpot. Leads go out automatically after each detection, and you can also send a lead or a selection by hand. Connected tools are open to every account with the Leads module, which is included in the Growth, Creator, Agency, and Team plans and in the free trial. In an organization, the member needs a seat that includes Leads. The MagicPost Leads page presents the module as a whole.
The five tools you can connect
Webhook: MagicPost posts each lead to an HTTPS URL. This is how you reach Zapier, Make, n8n or your own endpoint.
Lemlist: MagicPost adds leads to one or several Lemlist campaigns.
ReachBoost: MagicPost adds leads to ReachBoost lead lists or campaigns.
Pipedrive: MagicPost creates contacts in Pipedrive, with a note.
HubSpot: MagicPost creates contacts in HubSpot, with a note.
Every MagicPost tool connection uses an API key, a token or a webhook URL that you paste. None of them uses a "sign in with" window.
MagicPost accepts one connection per tool and per user: one webhook URL, one Lemlist account, one ReachBoost workspace, one Pipedrive account and one HubSpot account. A tool that is already connected is grayed out in the list. To reach both Zapier and Make, fan out from a single webhook.
Connect a tool
Open Leads in MagicPost and stay on the Leads tab.
Click Connect a tool in the toolbar. Once a tool is connected, the same button shows the number of connected tools. On a phone, the entry is in the three-dot menu, More actions.
Pick the tool.
Paste the credentials the form asks for, then click Test and connect. MagicPost tests the connection before saving it.
Choose where the leads go, then click Create connection, or Save for ReachBoost. A webhook has nothing to choose and skips this step.
The credentials each tool needs
Webhook: the Webhook URL. MagicPost only accepts an HTTPS URL. In Zapier, create a Zap with a Catch Hook trigger and paste its URL.
Lemlist: the Lemlist API key, found in Lemlist under Settings, Integrations, API & Webhooks.
ReachBoost: the ReachBoost API key, found in ReachBoost under Integration, API Keys, and the Workspace UUID.
Pipedrive: the Pipedrive subdomain, which is the part before .pipedrive.com, and the Personal API token, found in Pipedrive under My account, Personal preferences, API.
HubSpot: the Access Token (Private App). Create a Private App in HubSpot with the scopes contacts.write, notes.write and owners.read.
Where the leads land
Lemlist: a Campaign, the Targeted ICPs, and the Icebreaker source sent to Lemlist. You can connect several campaigns to one Lemlist account.
ReachBoost: a lead list or a campaign, the Targeted ICPs, and the Email required switch. You can add several destinations to one ReachBoost account.
Pipedrive: the Lead owner the contacts are created under.
HubSpot: the Lead owner and the Default Lead Status of the contacts.
What MagicPost sends automatically
After each detection that finds leads, MagicPost sends the new leads to every connected tool that is not paused. This happens for manual detections and for the detection agent, whether or not you receive the email notification.
A single detection in MagicPost sends a capped number of leads to each destination. On a very large post, the leads beyond the cap are not sent automatically later: send them yourself with Send to tools.
MagicPost only sends leads, which means profiles with at least a Medium fit. A profile that was set aside is never sent to a tool. MagicPost has no setting for a minimum fit level: Excellent, Good and Medium leads are all sent.
Two settings narrow the automatic sending in MagicPost. Targeted ICPs, on Lemlist and ReachBoost, limits a campaign or a destination to the ICPs you tick. For a lead scored on several ICPs, MagicPost looks at the ICP where the lead has its best fit. Email required, on ReachBoost, skips the leads that have no email address.
MagicPost does not look up email addresses for customers, so most leads have no email. Leave Email required off unless you want to skip them. MagicPost never sends the same lead twice to the same destination.
Send leads by hand
MagicPost offers two manual ways to send leads to a connected tool. Both ignore Targeted ICPs and Email required, because you chose the leads yourself. Both only offer the destinations that are not paused.
One lead: open the lead card. The Tools section lists your destinations with a Send button, or Resend after a failed delivery.
A selection: tick the leads in the table, click Send to tools in the selection bar, pick the tools and confirm. MagicPost skips the leads already delivered to a tool, so you can run the action again without creating duplicates. A very large selection has to be sent in several passes.
To find what was sent, use the Synced to filter of the MagicPost Leads tab. The logo of each tool a lead was sent to also shows on the lead card.
Pause, edit or disconnect
All these actions are in the Connected tools dialog of MagicPost. The buttons of a connection appear when you hover its card.
Test checks the connection again. The card then shows OK, Error or Not tested.
Pause stops the sending to a campaign or a destination without removing it. Resume sending turns it back on.
The pencil icon of a campaign or a destination changes the campaign, the owner, the status or the targeted ICPs.
The trash icon of a connection disconnects the account. The leads already sent stay in the tool.
MagicPost lets you edit the API key of a ReachBoost connection in place, with Edit connection, and the disconnect button of ReachBoost is in that same form. For a webhook, Lemlist, Pipedrive and HubSpot, changing the URL, the key or the token means disconnecting the tool and connecting it again.
Troubleshooting
Leads do not arrive. Open Connected tools and click Test on the connection. An Error status usually means the key or the token is no longer valid. Also check that the campaign or the destination is not Paused.
A red badge shows on a campaign or a destination. The badge names the cause: Destination not found, Destination paused or Reconnect your account. The line under the campaign or the destination says what to do. Test only checks the account, so a campaign deleted or paused in the tool does not show there.
A large post sent only part of its leads. One detection sends a capped number of leads to each destination. Select the remaining leads and click Send to tools.
Some leads are missing. Check Targeted ICPs on the campaign or the destination, and Email required on ReachBoost.
A Lemlist connection has no campaign. MagicPost sends nothing to Lemlist until you click Connect a campaign.
FAQ
Can I send a batch of leads to my tools at once?
Yes. Tick the leads in the MagicPost table view and click Send to tools in the selection bar. The action appears once at least one tool is connected. Leads already delivered to a tool are skipped.
Do I need Zapier specifically?
No. The MagicPost Webhook tool posts to any HTTPS URL: Zapier, Make, n8n or your own endpoint.
What does the webhook receive?
A JSON body per lead. It contains the lead's profile, its qualifications with the ICP and the fit level, and the post the lead was detected on. A lead sent by hand has no post information.
Can I choose to send only my Excellent leads?
Not with a MagicPost setting. Automatic sending covers Excellent, Good and Medium leads, and a paused destination receives nothing, neither automatically nor by hand. With a webhook, filter on the fit level in Zapier, Make or n8n.
Can an admin connect tools for the whole team?
No. In MagicPost, connected tools belong to each user, and the team Leads page has no Connected tools button. Each member connects tools from their own Leads tab.
Need help?
Reach out via the in-app chat, or book a 30-minute onboarding call: https://cal.com/magicpost/book-a-call