interlocute.ai beta
Surfaces & Channels

Your node, everywhere

Surfaces are how your node talks to the world — and how the world talks back. Conversations go out. Events come in. One node handles both sides, with shared memory and governance across every channel.

Inbound Channels

Where events flow into your node

Your node can also listen. Inbound events — emails, text messages, webhook payloads — are normalized, matched to a trigger, and processed through the same intelligence pipeline as any conversation.

Email

Coming soon

Forward messages to a node-bound mailbox. The platform parses headers, body, and attachments, then triggers your node to process or respond.

Attachments supported Thread mapping

SMS

Coming soon

Receive inbound text messages via Twilio. Signature-validated at the edge, then normalized and routed to your node for processing or reply.

MMS media supported Signature validation

Webhooks

Coming soon

POST any JSON payload to a node-bound endpoint. Ideal for connecting third-party services, CI/CD events, or custom application triggers.

Any JSON payload Secret validation

One node, every direction

Conversational surfaces and inbound channels converge on the same node. Shared memory, shared policies, shared cost attribution — regardless of how the interaction started.

01

Event arrives

A user sends a chat message, an email lands, an SMS arrives, or a webhook fires. The platform normalizes every event into a common envelope.

02

Node processes

Your node runs inference with full context — memory, RAG, tools, guardrails. The same intelligence pipeline handles every channel.

03

Response flows back

Streamed to a chat UI, stored as an artifact, or queued for outbound delivery. Every interaction is logged, metered, and attributable.

Connect your node to everything

Start with a surface. Add inbound channels as your use case grows. One node handles it all.