Skip to main content
Plans. Kerux events are on every plan. The meeting, email and WhatsApp events only happen when you have a calendar or booking tool, an email inbox or a WhatsApp number connected, and connecting those is part of Pro and Agency. The SMS reply event is coming soon. See Plans and billing.
A Kerux event starts a campaign on its own when something happens to a contact inside Kerux. It works the same whether the change comes from a person, an import, the public API, a form, a signal or another campaign. LinkedIn only says a message was seen when the person shares read receipts (see Seen, Delivered and Not seen yet), so this trigger never fires for people who turned them off. It only starts people who are already contacts in Kerux.

Add a Kerux event

1

Open the campaign

Click Campaigns and open the campaign.
2

Click + Add on the Trigger half

On the start box of the Builder, click + Add on the Trigger half. The Add a trigger panel opens on the right. Or open the Triggers tab, click + Add and pick Kerux event.
3

Find the event and fill it in

Search for it (for example tag or task) or find it in its group, and click it. Its settings show right away: fill them in and click Add trigger. It shows on the start box and under Kerux events in the Triggers tab, with when it was last used.
Any member who can edit campaigns can add Kerux events. A campaign can have up to 10. A campaign that isn’t launched yet keeps the people under Waiting for launch until you turn it on.

Dates and birthdays

Birthday reminder (in Schedule and dates) is a Date reminder ready for birthdays: every year, on the day, at 9:00, on the custom field whose name looks like a birthday. Change any of it before you click Add trigger. Add a custom field with dates first (Contacts > Custom fields), for example Birthday, written as 1990-03-14 or, without the year, 03-14. Dates like 14/03/1990 work when they can only be read one way. Kerux checks every day at the time you chose, in the time zone you chose, also on the days the clocks change. Someone born on 29 February is reminded on 28 February in other years.

Schedules

A schedule runs at the day and time you set, in its time zone, and puts the list (or the contacts with the tag) in the campaign, up to 5,000 contacts per run. Nobody enters twice, unless you turn on Allow re-entry in the campaign’s Settings: then people who finished enter again on the next run, once the minimum gap has passed. A run missed by more than 12 hours (for example during maintenance) is skipped, never sent late. A trigger link is a tracked link that sends whoever clicks it into the campaign, then to the page you chose.
  1. Add a Trigger link clicked event with a name, for example webinar, and the page it goes to.
  2. In any message (of any campaign), write {{links.webinar}}. Each contact gets their own link.
  3. When a contact clicks it, they land on your page and enter the campaign.
The name booking is taken: {{links.booking}} is always your booking page. A trigger link named booking from before keeps working as {{links.booking_trigger}}, and the campaign’s Triggers tab says so. Link previews (LinkedIn, Slack, WhatsApp…) and other robots don’t count as clicks. The link only ever goes to the page you chose, and nobody can change it to enroll someone else. A trigger link belongs to one contact, so it has no QR code. To bring in people who scan a code at an event, print a form’s QR code instead (see QR code for a form).

Loops are stopped for you

A change made by a campaign’s own steps never sends people back into the same campaign. When campaigns pass people to each other (campaign A tags a contact, which starts B, which changes something that starts A…), Kerux stops the chain after 3 hops. The contact’s journey shows Not sent back in (loop guard) when that happens.

With the API

Everything here is also in the public API: GET / POST /v1/workflows/{id}/event-triggers (message_read takes an optional workflow_id; whatsapp_reply and sms_reply take nothing, and sms_reply answers 403 SMS_COMING_SOON while text messages are coming soon; account_attention takes an optional problems list: locked, restricted, signin, removed, down; stage_changed takes optional from_stage and to_stage stage ids, none for off the board; engagement_hot takes nothing; engagement_changed takes an optional min_score; reply_received takes optional channels (linkedin, email, sms, whatsapp); note_added takes an optional contains; task_added and task_completed take nothing; task_due takes timing (before or overdue) and hours (0 to 168, default 1); do_not_contact takes direction (added or removed) and optional channels (all, email, sms, whatsapp); segment takes a segment_id; meeting_soon takes hours, 0.25 to 72, default 24, and late_bookings, skip or send) and DELETE /v1/event-triggers/{id}. Changes made through the API (adding a contact, tags, fields, notes, tasks, the do-not-contact list) start these campaigns too.

Common problems

Check that the campaign is on, and open the contact page: the timeline says Kerux trigger for each event, and whether they entered. They don’t enter when they’re already in the campaign, or went through it before and re-entry is off (or the gap hasn’t passed).
A Kerux event works on behalf of the teammate who added it. If that person left the workspace or can now only view it, the event stops. Remove it in the Triggers tab and add it again yourself.
Date reminders read custom fields. Add one in Contacts > Custom fields and fill it in for your contacts (import, API or by hand).