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 start on a Kast event. Whatever leaves Kast leaves through CSV export, or through direct sending to Instantly, Lemlist, Waalaxy and Gojiberry.
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.
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.
CSV export, in email or LinkedIn format, and direct sending to Instantly, Lemlist, Waalaxy or Gojiberry with your own API key.
If your sequence runs on Instantly, Lemlist, Waalaxy or Gojiberry, you connect it in Settings › Platforms and Make becomes unnecessary.
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 reads from.
That's what will decide what gets exposed first, once an API exists. We're not putting a date on it.
Seven-day public trial, card required. Keep your tools, Kast feeds them.
Start for free