3.2Advanced
0 of 5 lessons0%
Connect Kuration to Everything Else
Push scored rows into your CRM and sequencer automatically, and trigger Kuration from outside the app.
RevOps, and anyone whose finished list has to land somewhere other than a CSV.
5 lessons30 min
What this course costs
Exports and integrations do not spend research credits. Only the enrichment behind them does.
What you will be able to do
- Map fields once so every future export lands without manual work.
- Get notified when something changes, rather than checking.
- Drive Kuration from your own system, with your own AI keys where you want them.
Before you start
- Course 2.3, in particular column naming. Field mapping is trivial if the names already match and painful if they do not.
- Admin access to whatever you are connecting.
The lessons
- 1Map fields once: CRM and sequencer exports that keep working7 min readvideoscreenshotsFree.
- 2Webhooks and Slack notifications6 min readscreenshotsFree.
- 3Call any external tool with your own API key6 min readscreenshotsKuration charges for the column. The external service charges you separately on your own key.
- 4Run AI columns on your own Anthropic, OpenAI or Gemini key5 min readscreenshotsMoves the model cost onto your own provider bill.
- 5The workflow API: submit, poll, fetch6 min readThe same as running the workflow in the app. The API is a different door, not a different price.
The build that proves it
A list that arrives without anyone moving it
Connect one CRM or sequencer. Map every field once. Push a scored segment to it. Add a webhook that notifies your team when new rows clear the threshold. Then run the workflow again and confirm nothing needed touching.
- You have done it when
- The second run lands in the destination system with zero manual field mapping and a notification you did not have to check for.
- Credit budget
- No research credits. Time only.