Resources/Integration/Make

Kast and Make: why there's no scenario to build yet

Make and Zapier expect the same thing from Kast: an API or a webhook that announces what just happened. Neither exists today, so no Make scenario can be triggered by a Kast event. Anything that leaves Kast goes out through the CSV export, or through direct sending to Instantly, Lemlist, Waalaxy and Gojiberry.

Where the integration stands

01

No Kast module

Make doesn't offer a Kast module, and Kast emits no webhook a scenario could listen to. For now, conditional routing on the score would have nothing to route.

02

A single threshold, set at 70

The leads offered for transfer are the ones whose ICP score reaches 70. It's a product constant, the same for every account, not a setting you'd find in a scenario.

03

What actually leaves Kast

CSV export, in email or LinkedIn format, and direct transfer to Instantly, Lemlist, Waalaxy or Gojiberry with your own API key.

What you can do today

1

Check whether sending leads directly is enough

If your sequence runs on Instantly, Lemlist, Waalaxy or Gojiberry, you connect it in Settings › Platforms and don't need Make.

2

Otherwise, export to CSV

The LinkedIn format includes the original comment and the source post, which direct sending doesn't pass on. Your Make scenario can read that file once you've put it where the scenario looks for it.

3

Tell us which scenario you want to build

That's what will decide what gets exposed first, once an API exists. We're not putting a date on it.

Frequently asked questions

Neither for now: both need an API or a webhook, and Kast exposes neither. The question will come up again once that changes.
No, there's no trigger to expose it in the first place. The score is a column in the CSV export, where your scenario can read it once you've retrieved the file.

Get your next post scored before you publish it.

7-day trial, card required, cancel anytime.

Start for free