Channels

Accessible via: Main Menu -> Sammy -> Channels

Channels are where workflow output lands. A workflow publishes its result to a channel, and everyone who reads that channel sees it — no Slack or Teams required, though you can still send there as well.

The pages live under /feed, and the CLI and API call this the feed — in the app the column section is Channels.

It answers the question automation usually leaves open: the run succeeded, but where did the result go?

Channels

Channels organise output by what it’s about — one per team, client, or process. All shows everything you have access to; individual channels narrow it.

/feed                    # everything
/feed/<channel-slug>     # one channel

An empty channel says “This channel is quiet” — nothing has published to it yet.

Publishing to a channel

A workflow publishes to a channel as part of its definition, so the routing is set once by whoever builds it rather than per run. Point a workflow at a channel when its output is something a person needs to read — a summary, a report, a list of exceptions to work through.

Output that only another automation consumes is better written to a table.

Working with output

Items are grouped by day, newest last, each one showing who produced it (the agent), an UPDATE badge, the time, a title like “Concierge Harvest — completed”, and the output payload itself.

From an item you get:

• View the run — jumps straight to that execution, which is where you go when the output isn’t what you expected.
• A delivery note — in-platform only means the output was published here and nowhere else, as opposed to also being sent to Slack or email.

The search box at the top takes a description rather than keywords — “describe what you’re looking for” — so you can find an output by what it was about instead of remembering its title.

Failed runs publish here too, carrying the raw error from whatever broke. That’s your cue to open the run and read the failed step.

Channels vs Executions

If a workflow ran but nothing appeared in the channel, check its executions — the run may have failed, or may not be publishing to a channel at all.