This guide walks you through connecting Albacross to n8n so that lead events — newly identified companies and (optionally) their contacts — are sent to your n8n workflows in real time.
Before you begin, make sure you have:
An active Albacross account with the n8n integration included in your plan. If you don't see n8n under Settings → Integrations, your current plan doesn't include it — please upgrade your plan or reach out to our support team to enable it.
An n8n instance you can sign in to (n8n Cloud or self-hosted, n8n 1.0 or newer). On n8n Cloud you'll also need verified community nodes enabled; on self-hosted instances the admin must have community nodes turned on.
Step 1 — Get your Albacross API key
Sign in to Albacross.
Go to Settings → Integrations → n8n.
Click Show to reveal your API key, then Copy it to the clipboard.
💡 Tip: If you ever need to rotate the key, use Regenerate on the same page. Regenerating invalidates the old key and disconnects any n8n credentials still using it.
Step 2 — Install the Albacross community node in n8n
Sign in to your n8n instance.
Open Settings → Community Nodes.
Click Install a community node. The Install community nodes dialog opens.
In npm Package Name, enter
n8n-nodes-albacross.Tick I understand the risks of installing unverified code from a public source.
Click Install and wait for the installation to finish.
Prefer to install manually? Run npm install n8n-nodes-albacross on your n8n host and restart the service. You can find the package on npm.
Step 3 — Create the Albacross credential in n8n
In any workflow, click + to add a node and search for Albacross.
Choose the Albacross Trigger node.
Under Credential to connect with, click Create New.
Paste the API key you copied in Step 1 and click Save.
n8n will automatically validate the key against Albacross. If everything is correct, the credential is marked as connected.
Step 4 — Configure the Albacross Trigger node
With the credential connected, fill in the trigger's parameters:
Segment Name or ID — pick a specific Albacross segment, or All companies to receive every identified lead.
What Do You Want to Do?
Send New and Returning Companies fires the workflow on every qualifying event.
Send Only New Companies triggers once per company (deduplicated).
Output Contacts (optional toggle) — turn this on to also receive matching contacts alongside each company. When enabled, the following fields appear:
Type of Data — choose which contact data to include (e.g. Contacts (Email)).
Contacts per Company — maximum number of contacts to return per company.
Add Keywords By — Buyer Persona (recommended) or a custom keyword list.
Buyer Persona Name or ID — pick the persona you already maintain in Albacross.
Which Countries Do You Want Contacts From? — Automatically Based on Visiting Company or a manual country list.
Must Have Emails / Must Have Phone Numbers / Must Have Contacts — toggles to skip leads that don't meet your minimum data quality bar.
Step 5 — Activate the workflow
Add the rest of your workflow (Slack, HubSpot, an HTTP request, an AI node — whatever you need) and click Active in the top-right of the editor.
As soon as the workflow is activated, the Albacross Trigger registers itself with Albacross and a matching connector appears in your Albacross account under Connectors. From this point on, any matching lead will be delivered to your n8n workflow in real time.
Verifying the connection
To confirm everything is wired up correctly:
In Albacross, go to Connectors. You should see a new n8n connector for the segment you selected.
In n8n, open the workflow's Executions tab. Each delivered lead will appear there with the full payload.
Troubleshooting
"Authentication failed" when saving the credential — Double-check that you copied the key from Settings → Integrations → n8n in Albacross (not some other access token), with no extra spaces. If you recently regenerated the key, make sure you are using the new one.
The connector doesn't appear in Albacross — The connector is created the moment the n8n workflow is activated. Toggle the workflow off and on again, and make sure the n8n webhook URL is reachable from the public internet (relevant for self-hosted n8n behind a firewall).
The segment dropdown is empty — Your Albacross account may not have any segments yet. Create one in Albacross first, or pick All companies.
I'm not receiving any leads — Check that the segment you selected actually has matching companies. You can test against a broader segment first, then narrow it down.
I renamed my trigger node and it stopped working — Re-activating the workflow will re-register the trigger with Albacross. No action is required in Albacross itself.
For issues with the community node itself, please file an issue on the n8n-nodes-albacross GitHub repository. For account, API key or plan questions, contact our support team.
Disconnecting
To stop receiving events:
From n8n: deactivate the workflow, or delete the Albacross Trigger node. The matching connector is automatically removed in Albacross.
From Albacross: regenerate the API key in Settings → Integrations → n8n. This disconnects every n8n credential that uses it.