Skip to main content

What each of this workspace's channels can send

GET 
/api/flows/channel-actions

The flow palette's app tier: press WhatsApp and get WhatsApp's actions, press Telegram and get Telegram's. Backs the channel_send node kind.

Published per channel ROW rather than per source, because that is the grain the answer has: two WhatsApp numbers in one workspace differ by whether a catalog is linked and whether a Flow is published, and a list drawn from the source alone would offer one number an action that belongs to the other.

Read from the channel's own live capabilities — the same table the agent's share sheet is drawn from — so the palette cannot offer an action the send would drop in silence. A channel with nothing to offer is omitted rather than listed empty.

fields is the config keys each action reads, so the node's form is drawn from the server's answer rather than from a second table in the panel.

Responses​

The channels that can carry at least one composable action.