Which providers Lead Hero connects to, what each one needs from you, and how connecting works.
Who can do this: owners and managers. Everyone else sees the Integrations page in read-only form with the message "Only owners and managers can manage integration settings."
What Lead Hero connects to
Providers are grouped into two categories on the Integrations page, and each one is its own tab.
Cold Email Sequencers feed positive replies into Lead Hero as leads.
Provider | What you need | Article |
Email Bison | API key, plus your Bison host | |
Instantly.ai | API key | |
HeyReach | API key. Also the largest set of options: which webhook events to receive, how provider statuses map onto Lead Hero statuses, and whether manual status changes are preserved | |
Smartlead.ai | API key | |
PlusVibe.ai | API key and a Workspace ID | |
ColdBound | API key and a Workspace ID |
CRM and Automation connect Lead Hero to a CRM.
Provider | What you need |
LeadConnector | No API key. You connect it through OAuth, with a separate button for Go HighLevel, and the connection is tied to a Subaccount Location ID |
HubSpot | Listed but not connectable yet. Its row shows Coming soon and its controls are disabled |
If a tool is not on this list, it is not supported, whatever category it belongs to. The list on your own Integrations page is the authority.
1 the workspace selector, which only appears when your organization has workspaces beyond the default. 2 the category tabs.
How connecting works
The steps are the same for every provider that uses an API key.
Open Integrations.
Choose the workspace this connection belongs to.
Select the category tab, then select the provider's row to expand it.
Enter the API key, plus the Workspace ID or host if the provider needs one.
Select Save.
Tick Enable {provider}. This checkbox only appears once a key is stored, and ticking it is what actually registers the webhook with the provider.
Check that the row badge reads Active.
You never create a webhook in the provider's own interface. Lead Hero registers it using the key you saved.
Active means three things are true at once: a key is stored, the integration is enabled, and the webhook is registered. It does not mean an event has arrived yet. To confirm that, send a positive reply from a test campaign and watch for the lead.
Each workspace is configured separately
Integration settings belong to the workspace selected at the top of the page, and nothing is inherited in either direction. Configuring a provider at organization level does not configure it for a workspace, and a workspace with no configuration of its own comes up empty rather than falling back.
Organization (Default) in the selector means the organization itself, which is also what the default workspace uses. Named workspaces each hold their own key and their own webhook.
This is worth checking first whenever a connection you are sure you made appears to be missing.
Auto-enrich is on by default
Every API-key provider has an Auto-enrich incoming leads checkbox, and it is on by default. When it is on, leads arriving from that provider can trigger LinkedIn and phone enrichment, which consumes enrichment credits.
The checkbox is greyed out until the integration is enabled, so you can only change it once the connection works. Nothing on the Integrations page shows what enrichment costs, so check Billing before leaving it on for a high-volume campaign.
Coming soon
A provider marked Coming soon appears on the page with its fields visible but disabled. It cannot be connected yet.
HubSpot is listed so you can see it is planned, not to be configured today.
When to contact support
Get in touch if:
A provider you expect is missing from the page.
A row stays Inactive after you have saved a key and ticked enable.
A test reply from your provider does not create or update the lead.
Include the organization, the workspace, the provider, and the error message shown under the form word for word. Never include the API key or the webhook URL, both of which are credentials.
Next steps
Connect Email Bison: the full setup for one provider
Connect Instantly: the same for another
Organizations, workspaces, and members: creating the workspace first
Enrich leads with phone data: what auto-enrich runs
Use the Lead Hero API and webhooks: building your own integration instead