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

Make scenarios that start and steer LinkedIn campaigns

Q: Is there a Kerux app in Make?

Not yet. Make's built-in HTTP and Webhooks modules connect to Kerux today: one sends leads to a trigger URL, the other receives Kerux's events.

Q: Can Make send leads without a LinkedIn URL?

Not to a trigger URL: Kerux needs linkedin_url to know who the person is. Find it first (for example with an enrichment module) or collect it in your form.

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

The lead stops with Make'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.

Any Make scenario can send leads into a Kerux campaign, react to what happens there, and answer a lead that's waiting for data.

Start free trial Read the setup guide

How it works

A scenario starts
A Typeform answer, a new CRM contact, a sheet row.
Daniel joins the campaign
With his answers saved as fields.
Make answers the lead's callback
```
POST {{wait.callback_url}}
{
  "score": 87,
  "segment": "agency"
}
```
Lead continues
Make answers mid-campaign
Your scenario posts a score back; the lead continues.

An example workflow

A Make scenario watches your form or CRM and sends each new person to a Kerux trigger URL with HTTP > Make a request.
The campaign sends the LinkedIn invitation.
Accepted: a Call & wait step calls a Make Custom webhook with {{wait.callback_url}}; the scenario looks the company up and posts score and segment back.
The next message uses {{steps.score.payload.segment}}, and low scores take a shorter path.
A second scenario gets meeting.booked events and creates the deal in your CRM.

What data flows

Kerux sends to Make

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

Make 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 Make signs in, paste the key and Make's Base URL, click Save, then Test connection.
In Make, add HTTP > Make a request: method POST, that URL, body type JSON, with linkedin_url (required), first_name, email, company and extra fields under custom.
For events, start a scenario with Webhooks > Custom webhook, copy its address into Kerux under Integrations > Developers > Webhooks, pick the events and click Send test event so Make learns the fields.
To answer a waiting lead, have the scenario POST its result to the callback_url Kerux sent it.
In the campaign's Builder, click Test to open Test on one lead: the lead's journey shows what Kerux sent to Make and what came back.

Questions

Is there a Kerux app in Make?

Not yet. Make's built-in HTTP and Webhooks modules connect to Kerux today: one sends leads to a trigger URL, the other receives Kerux's events.

Can Make send leads without a LinkedIn URL?

Not to a trigger URL: Kerux needs linkedin_url to know who the person is. Find it first (for example with an enrichment module) or collect it in your form.

What happens if Make is down or refuses a call?

The lead stops with Make'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.