Via API steps and webhooks No app to install: Kerux talks to n8n's API with HTTP steps and webhooks, set up once.

n8n workflows inside your LinkedIn campaigns

Q: Is there a Kerux node for n8n?

Not yet. n8n's built-in HTTP Request and Webhook nodes do everything: send leads to a trigger URL, receive Kerux's signed events, and answer a lead's callback URL. It works the same on n8n Cloud and self-hosted.

Q: What does a lead need to enter through n8n?

A LinkedIn profile URL, in linkedin_url. Kerux matches leads by it, so the same person is never added twice.

Q: What happens if n8n is down or refuses a call?

The lead stops with n8n's own error message and shows in Need attention with a Retry button. It never shows as finished because a call failed, and nothing else goes out to that lead until you decide.

Send leads from any n8n workflow to a campaign, get every reply and accepted invitation back as an event, and let a lead wait in Kerux until your n8n workflow answers.

Start free trial Read the setup guide

How it works

Your n8n workflow runs
Any trigger: a database row, a form, a CRM change.

The lead enters the campaign

One POST with the LinkedIn URL and any fields.

Campaign
1. Invitation accepted
2. Event sent to your n8n Webhook node
3. Follow-up message
Events flow back to n8n
Accepted, replied, booked: your Webhook node gets them.

An example workflow

n8n watches your source (Postgres, Airtable, a form) and an HTTP Request node POSTs each new person to the Kerux trigger URL.
The campaign sends the LinkedIn invitation and first message.
A Call & wait step POSTs the lead to an n8n Webhook node with {{wait.callback_url}}; your workflow scores the lead and POSTs the score back to that URL.
The campaign branches on the score: high scores get a personal message, the rest a lighter sequence.
reply.positive events reach a second n8n workflow that creates the deal in your CRM.

What data flows

Kerux sends to n8n

linkedin.invitation_accepted
linkedin.message_received
reply.positive
meeting.booked

n8n sends to Kerux

linkedin_url
first_name
last_name
email
company

Set it up

In Kerux, open the campaign, click + Connect on the Automations half of the first card, choose Incoming webhook (API) and Copy link.
In Kerux, open Integrations > Connections and click Connect on Custom API (under Developers). Pick how n8n signs in, paste the key and n8n's Base URL, click Save, then Test connection.
In n8n, add an HTTP Request node: method POST, that URL, body JSON with linkedin_url (required), first_name, last_name, email, company and any extra fields under custom.
For events, add a Webhook node in n8n, copy its production URL into Kerux under Integrations > Developers > Webhooks, pick the events and click Send test event.
To answer a waiting lead, put a Call & wait step in the campaign that calls your n8n Webhook node with {{wait.callback_url}} in the body; end your workflow with an HTTP Request node that POSTs the result to that URL.
In the campaign's Builder, click Test to open Test on one lead: the lead's journey shows what Kerux sent to n8n and what came back.

Questions

Is there a Kerux node for n8n?

Not yet. n8n's built-in HTTP Request and Webhook nodes do everything: send leads to a trigger URL, receive Kerux's signed events, and answer a lead's callback URL. It works the same on n8n Cloud and self-hosted.

Can I check that an event really came from Kerux?

Yes. Kerux signs every webhook with the Standard Webhooks scheme; n8n can check the signature with a Code or Crypto node. Trigger URLs can also require a signature on what you send.

What does a lead need to enter through n8n?

A LinkedIn profile URL, in linkedin_url. Kerux matches leads by it, so the same person is never added twice.

What happens if n8n is down or refuses a call?

The lead stops with n8n's own error message and shows in Need attention with a Retry button. It never shows as finished because a call failed, and nothing else goes out to that lead until you decide.

Use it in a campaign

Try Kerux free for 10 days. No card needed.