Skip to main content

Connect Email Bison

Configure Email Bison for the correct workspace, register its webhook, and verify an active connection before using production replies.

Ü
Written by Ümit Baltacı

Point Lead Hero at your Email Bison instance so that positive replies arrive as leads in the right workspace.

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."

Before you begin

You need three things:

  • An Email Bison API key. Create it in Email Bison, not in Lead Hero.

  • Your Bison host. If you run your own instance this is your own domain, something like mail.yourcompany.com. If you are on the shared instance it is dedi.emailbison.com, which is the default. Enter the host on its own, with no https:// and no path.

  • The workspace that should receive the leads. Each workspace holds its own Email Bison connection, its own key, and its own webhook. Nothing is shared between them.

Treat the API key the way you would treat a password. Do not paste it into chat, email, or a screenshot.

Connect the integration

  1. Open Integrations.

  2. Pick the workspace at the top of the page. Do this first. Everything below is saved against whichever workspace is selected.

Each workspace keeps its own connection. Organization (Default) is the default workspace, and choosing it configures the organization rather than a named workspace.

  1. On the Cold Email Sequencers tab, select Email Bison to expand it.

  2. Enter your host in Your Bison URL (e.g. mail.yourcompany.com), or leave the default if you are on the shared instance.

  3. Paste your key into Email Bison API Key.

  4. Select Save.

A connection that has no key yet. 1 is the Bison host, showing the shared instance as its default. 2 is the key field, which masks whatever you paste. Auto-enrich incoming leads is greyed out at this stage and unlocks later.

Saving only stores the credentials. It does not connect anything yet.

  1. Once the key is saved, an Enable Email Bison checkbox appears above the form. Tick it.

After saving, the key is replaced by API key configured and the enable checkbox appears. The checkbox does not exist until a key is stored.

Ticking the box is the step that does the work. Lead Hero calls your Bison instance, registers a webhook for the lead_interested event, and points it back at Lead Hero. You never create a webhook in Email Bison yourself.

If the key or the host is wrong, registration fails, the checkbox comes back off, and the reason appears in red underneath the form. That message is the useful diagnostic, so read it before trying again.

  1. Check that the row badge reads Active.

Active on the provider row means all three conditions hold: a key is stored, the integration is enabled, and the webhook is registered on your Bison instance.

  1. Send one positive reply from a test campaign and confirm the lead appears in the workspace you selected.

What Active does and does not prove

Active means Lead Hero successfully registered a webhook in Email Bison. It does not mean any event has arrived yet. Only step 9 tells you that.

Lead Hero re-checks a healthy webhook at most once every 15 minutes. A connection that is not Active is re-checked every time the page loads. So if you have just fixed something in Email Bison, a stale Active can lag reality by up to a quarter of an hour, while a broken one updates straight away.

Auto-enrich incoming leads

Auto-enrich incoming leads is on by default, but it stays greyed out until the integration is enabled, so you can only change it after the connection works.

When it is on, leads arriving from Email Bison can trigger LinkedIn and phone enrichment. That consumes enrichment credits. Nothing on this page shows what enrichment costs, so check Billing before you leave it on for a high-volume campaign.

Like the key, this setting belongs to the selected workspace.

Change or remove the key

Once a key is saved it is never shown again. Two buttons replace it:

Button

What happens

Change API key

Opens the field so you can paste a new key. Saving re-runs webhook registration against the new credentials.

Delete API key

Asks "Delete the API key? This will disable the integration." Confirming removes the key and switches the integration off. Leads stop arriving.

The webhook URL is a credential

The webhook Lead Hero registers carries a secret in its query string. Anyone who has that full URL can post events into your workspace. Treat it like the API key: keep it out of screenshots, tickets, and shared documents.

This is also why you should never copy a key or a webhook URL from one workspace into another. Each workspace has its own secret, and reusing one sends leads to the wrong place.

Limitations

  • Email Bison can change its own menus and event names without notice. If a step here does not match what you see, follow Email Bison's interface and tell us.

  • Only positive replies are received. Lead Hero subscribes to lead_interested and nothing else.

  • Connections are per workspace. There is no way to configure one and copy it across.

When to contact support

Get in touch if:

  • The form shows an error you cannot resolve.

  • The badge stays Inactive after you have saved a key and ticked enable.

  • A test reply never arrives, or arrives in the wrong workspace.

Include the organization, the workspace, roughly when you sent the test reply, and the error message from the form word for word. Never include the API key or the webhook URL.

Next steps

Did this answer your question?