Product feeds in Venom Chat
Post Incidents, Tasks, Flags, Experiments and Forms events to a channel as messages with buttons. Acknowledge a page or approve a flag change from the channel, with your own permissions.
A product feed makes one of your products post its events to a channel in Venom Chat. The team sees "Page: checkout is down" where it already talks, and presses Acknowledge there. Slack stays optional; a feed needs nothing outside Venom.
Set a feed
Open a channel's details (click its name) and find Product feeds. A channel owner turns a product on and picks which of its events post. A direct message cannot have a feed.
| Product | Events | Buttons |
|---|---|---|
| Incidents | an incident is declared or resolved; someone is paged | Open incident, Acknowledge, Open on-call |
| Tasks | an issue lands in a team's Triage | Triage it |
| Flags | a flag change waits for approval | Approve, Reject, Open flag |
| Experiments | an experiment is decided; a guardrail is breached | Open experiment |
| Forms | a response arrives | Open responses |
Messages come from an agent member called, for example, "Incidents feed", which joins the channel when you set the feed and leaves when you remove it. An event that is retried posts once.
What a feed shows, and to whom
- A feed posts titles and numbers only. A form's answers, an issue's description and a page's details stay in the product.
- A feed never widens who sees something. It only posts for a product your organisation has. In a private channel it posts only while every person in the channel is still in the organisation with a role that reads that product; a person who left the organisation but is still listed in the channel stops the feed there until they are removed. Owners and admins do not read private channels, and a feed does not change that.
Buttons
A link button opens the product. An action button does something once: Acknowledge a page, Approve or Reject a flag change. Pressing it runs the product's own check as you, with your role: a billing member who may read Incidents cannot acknowledge a page, and the button stays for someone who can. When it works, the message shows who did it and the buttons go away for everyone. Approving a flag change approves the request; applying it stays a step in Flags.
For agents
Three tools on the workspace MCP server and REST API: chat_feed_list (a channel's feeds and what could
be set), chat_feed_set (set, change or remove: true; channel owners) and chat_feed_press (press a button by its
position; it runs as the member the credential acts for, and needs chat:write). REST: GET and PUT /api/v1/chat/channels/{channel}/feeds and POST /api/v1/chat/messages/{message}/actions.