Conversations
Inspect observed external threads and message history
Conversations are the threads Fruxon has observed through messaging integrations: Slack channels or DMs, Telegram chats, Teams conversations, Twilio phone-number conversations, and similar provider addresses.
They are tenant-level resources in Agent Network. An integration config is the credentials lens that observed a thread, not the owner of the conversation.
What's a conversation?
A conversation represents one external provider thread identified by its provider and address. It can be observed through one or more integration configs and can be related to agents, participants, triggers, and messages.
| Field | Meaning |
|---|---|
| Address | Provider-specific thread address, such as a Slack channel id, Telegram chat id, Teams conversation id, or phone number. |
| Name | Best-effort human-readable name from the provider. |
| Messages count | Number of observed messages in the filtered view. |
| Last message | Most recent observed message timestamp. |
| Senders | Distinct inbound senders seen in the conversation. |
Address is intentionally the same shape as ParticipantChannel.address, so a picker can copy an observed conversation address directly into a participant channel.
Conversation list
Use the conversation list to find provider threads before or after they are wired to participants. The list supports filters that compose:
| Filter | Use it for |
|---|---|
integrationConfigId | Show conversations observed through one workspace, bot, app, or phone number. |
agentId | Show conversations tied to messages for one agent. |
participantId | Show conversations reachable through a participant's channels. |
triggerId | Show conversations linked to executions fired by one trigger. |
onlyDiscovered | Show provider-discovered rows with no real traffic yet. |
Messages
Open a conversation to read messages oldest-first. Message rows include:
- The text body and attachments Fruxon captured.
- The integration config and integration id.
- The agent that processed or generated the message.
- The external sender id for inbound messages.
- The execution record id for outbound agent replies, when available.
You can also use the tenant-wide message stream when you want a cross-cutting view, such as all traffic through a config or all messages for a participant.
How this differs from sessions
Sessions are agent-execution context: what the agent remembers between turns. Conversations are provider-thread observation: where the traffic happened and which messages Fruxon saw. A single conversation can produce many runs and traces.
API
List conversations, fetch a single thread, and stream messages through the Conversations API.
Next steps
- Agent Network — configure participants and triggers
- Access Requests — approve unknown senders
- Observability — inspect traces for individual runs