0.0on G210B+events
500M+users
7+years profitable
50+enterprises
Your cluster, your topics, your format.
Point a workflow at brokers you run. Ordered routing rules decide which record goes to which topic, first match wins, and the rest fall through to a default.
- Ordered topic routing rules, first match winsSet a rule per topic; the first match sends the record, and anything left over falls to your default.
- Partition key under your controlDefaults to the record ID, but you can override it per topic when a consumer needs a different key.
- JSON or AvroPick the format your consumers already parse and paste the writer schema in. No registry to stand up.
Everything else you already send to.
Webhooks, CRM writes, Slack, email and SMS run from the same canvas. Kafka is one destination among the ones you already use, not a separate product.
- Webhooks in and outReceive an inbound webhook or fire one out, from the same canvas as every other destination.
- CRM and spreadsheet writesPush a field update or a new row without a separate sync tool watching for changes.
- Messaging and email destinationsSlack, SMS and email sit next to Kafka as ordinary destinations, not a different product to configure.
Triggered by data, not by a schedule.
A workflow fires when a record changes, when an event arrives, or on a schedule if that is what you want. The trigger is part of the workflow, not a separate cron somewhere else.
- Event, record-change and scheduled triggersFires on an incoming event, a record changing, or a schedule - whichever matches how the data actually arrives.
- Branching and waits inside one canvasSplit the path on a condition or hold for a delay, without leaving the workflow you started in.
- Runs visible per recordOpen a record and see which branch it took and why, rather than an aggregate success count.
What gets routed, and where it lands.
Four destinations that need no code between the event and the consumer.
Wired into the toolsyour team already opens.
Slack, Stripe, Twilio, SendGrid, Gmail, Google Calendar, Firebase, Apache Kafka, AWS. Blu Agent operates them for you without a browser tab.
See every integration
Teams love it
They stopped stitching tools andhired one system.
StockInvest
“Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest
FieldsUSA“We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA
Hoperfy“With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy
Frequently askedquestions.
They are the part that stops the duct tape growing. Four tools, three seams, and no single view of ad click to signup to trial to paid, so somebody hand-carries data between them every week. Point the sources here and the events land on one profile under one taxonomy, then a workflow routes them onward - Kafka, webhook, CRM write, Slack - from the same canvas, so nothing gets exported into a second tool to stay in sync. No engineer on staff for it either: triggers, branches and waits are set in the builder, and the Data Engineer agent runs the recipe.
You declare the destinations, and the Data Engineer agent stays inside that list. It publishes only to the topics and buckets you named, checks consent before a send, and fails loudly rather than creating infrastructure on your account. If a property a workflow depends on changes shape, it flags which segments break before the send goes wrong, so the handoff comes before the damage. You keep the strategy layer: which destinations exist, which consent applies, and what the schema is allowed to become.
Yes. You supply the brokers and the topics a workflow may publish to. Intempt never creates topics on your cluster, and a workflow pointed at an undeclared topic fails rather than creating one.
JSON or Avro. Avro takes an inline writer schema. The partition key is yours to set, and defaults to the record identifier if you leave it alone.
It is the one that ships today. Webhooks, CRM writes, spreadsheets, Slack, email and SMS run from the same canvas - each destination is a step in the same workflow recipe, not a separate integration to maintain.