Learn · Integrations
Every integration
What connects, which direction it runs, and what ships today.
Checked against the product on · written for people writing code
The platform reads from your systems through feeds and reaches back through connectors and webhooks. The table lists every door with its status. A door marked in build rejects a call today.
| Integration | Direction | Status | What it does |
|---|---|---|---|
| OpenTelemetry | Data in | Live in part | Take in traces from your existing collector and watch them like any event stream. |
| MCP | Both ways | Live | Speak the open tool protocol, so an agent runtime that uses it can call the platform as a tool. |
| REST | Both ways | Live | Every call the platform offers is plain HTTP with a JSON body. |
| SDKs | Both ways | Live | Python, TypeScript, Java, and C#, all pinned to one contract and tested against it. |
| Inbound webhooks | Data in | Live | Give a third-party tool a URL to post to. Each post becomes an event. |
| Outbound webhooks | Out to you | Live | Tell your systems when something happened: a call was held, a review closed, an entry was written. |
| CSV and files | Data in | Live | Read rows from a file you upload, or one the platform fetches on a schedule. |
| Plain text | Data in | Live | Send a block of text and have it read as one event, or split into several. |
| Both ways | Live in part | Read a mailbox on a schedule and turn each message into an event. Send notices out. | |
| Polled endpoints | Data in | Live | Call an endpoint of yours on a schedule and read records out of the response. |
| Agent stream | Data in | Live | Send what your own agent said, called, received, and observed. |
| Image, audio and video | Data in | In build | Read a picture, a recording, or a clip and turn what is in it into events. |
How a feed becomes an event
Every feed follows the same three parts. The connector fetches raw input. A delegate turns each raw input into one event about a watched thing. The event is then weighed against your rules.
| Feed kind | What arrives | What the event carries |
|---|---|---|
| CSV and files | One row | The row as fields, with the key column naming the watched thing. |
| Plain text | One block | The text, with the split marker applied when one is set. |
| One message | Sender, subject, body, and the message headers. | |
| Inbound webhooks | One JSON body | The body as fields. A list becomes one event per item. |
| Polled endpoints | One record from the response | The record as fields. |
| OpenTelemetry | One span | The span name, attributes, timings, and status. |
| Agent stream | One agent call | The kind, the payload, and the agent it is anchored to. |
The naming a feed produces
Every event is filed under a watched thing whose name has four parts: the word subject, the division, the type, and a slug you control.
| Type | Used for | How events are grouped into a story |
|---|---|---|
| chat | A conversation with a person or a bot. | By session. |
| sensor | A device or a service emitting readings. | By time window. |
| lead | A prospect moving through a funnel. | By stage. |
| ticket | A support or incident record. | By stage. |
| journey | A person moving through a process. | By stage. |