Native Built into Kerux: connect Chili Piper once and every campaign can use it.

Chili Piper meetings stop your LinkedIn follow-ups

When a lead books through Chili Piper, from a form or a link, Kerux hears about it, finds the lead by email and stops the LinkedIn sequence.

How it works

Daniel is in your LinkedIn campaign and visits your site after the second message.
He fills in the demo form; Chili Piper books him with a rep.
Chili Piper's webhook reaches Kerux and the lead is found by his email.
The remaining LinkedIn steps stop and the owner gets a Slack message.
A moved or cancelled meeting updates the lead too.

Moved and cancelled meetings too. Chili Piper sends no booker name; Kerux finds the lead by email.

In Kerux, click LinkedIn accounts in the menu. Under Booking tools, pick Chili Piper and click Add a booking tool, then click Manage on its row and Copy URL.
In Chili Piper, open Command Center > Integrations > Webhooks and add one Custom Webhook per event (New Meeting, Meeting Update, Canceled Meeting) with the Kerux URL, then switch each to Enabled.
Book a test meeting with the email of a lead in a campaign. The row says Receiving, and the lead's timeline shows the meeting.

Does Kerux have a native Chili Piper integration?

Yes. Chili Piper is built into Kerux: you connect it once and every campaign can use it, with no Zapier and no code in between.

Chili Piper doesn't send the booker's name. Is that a problem?

No. Kerux finds the lead by email, which Chili Piper sends. The name stays the one already on the lead.

Does it work with Chili Piper's routing?

Yes. Whoever the meeting is routed to, the webhook says a meeting was booked with that email, and that's what stops the follow-ups.

Try Kerux free for 10 days. No card needed.