Pro plan. RB2B sends people to a campaign’s trigger URL, and trigger URLs are part of Pro and Agency (and the free trial). Anything you already have keeps working on every plan. See Plans and billing.
How it connects: RB2B’s webhook to n8n or Make, then Kerux’s trigger URL. RB2B’s payload below is from RB2B’s webhook guide.
Before you start
- RB2B plan: person-level data with LinkedIn profiles is on RB2B’s paid plans, and covers US visitors (RB2B’s site).
- Privacy: check that your site’s privacy policy covers visitor identification where your visitors are.
What RB2B sends
Set it up
1
Copy the Kerux trigger URL
In Kerux, open the campaign, click + Add on the Trigger half of the start box, choose Incoming webhook (API), click Add, then Copy link. Then in Integrations > Developers > Trigger URLs, turn on Check people against my ideal customer first for it.
2
Receive RB2B in n8n or Make
n8n: a Webhook node. Make: Webhooks > Custom webhook. Paste its URL in RB2B’s webhook integration and send RB2B’s test payload.
3
Rename and POST to Kerux
An HTTP Request node (n8n) or HTTP > Make a request (Make): POST to the trigger URL with JSON:
202 with enrolled, review and skipped counts and a judgments list: good fits enter, unsure ones wait for your review, misses are skipped.
Write the first message well
Use{{contact.custom.page}} to choose the campaign or the angle, not to tell people you saw them on your site.
Common errors
422 VALIDATION_FAILED
422 VALIDATION_FAILED
The visitor had no LinkedIn URL (RB2B sometimes identifies only the company). Add a filter so only payloads with
LinkedIn URL continue.Too many people enter
Too many people enter
Turn on the ideal-customer check, or filter by RB2B’s
Tags (for example only “Hot Page”) before posting to Kerux.