Channels: everything that talks to the outside

A channel is any way data crosses the edge of your workspace — in from people who have no login, or out to the systems you run. Forms, Email In mailboxes, Webhook In endpoints, chat widgets, booking pages, automation webhooks, connectors, outgoing webhooks, shared view links and API clients are all channels, and Channels lists every one of them in a single place. What counts as a channel Ten things, and they divide by direction rather than by which part of the app happens to build them. Coming in: a form (a public link people fill in), Email In (an address people write to), Webhook In (a URL your own systems POST to — each JSON POST becomes a record, in a format RowFold publishes), and an automation webhook (a URL that fires an automation — for payloads whose shape the sender dictates). Both ways: a chat widget (visitors write, you answer), a booking page (it publishes your availability and sends confirmations), a connector (a tool you already run), an API client (your own code, doing whatever its scopes allow). Going out: an outgoing webhook (we POST the moment a record changes) and a shared view link (a read-only public page for one saved view). The question this page answers What of ours is reachable right now, and what does it write to? Every row names the table it files into, so you can see at a glance that the form somebody published last quarter is still open and still filling up a table nobody watches. The count at the top says how many addresses answer a stranger who has the link. That is the number worth knowing: seven of these surfaces are protected by an unguessable token rather than a login, so the address is the key. The count never changes when you filter the list — it is always about the whole workspace. Public, Live, Paused Three states, and the difference matters. Public means anyone holding the address gets a real answer right now. Live means the channel is running but exposes nothing of yours — an outgoing webhook reaches out to you, and an API client needs a secret as well as the client id you can see here. Paused means it answers as closed; nothing is deleted, and the address is never reused for anything else. Adding and changing one Booking pages and chat widgets are most often born from the + New menu — Take bookings and Run a help desk — which set up the table behind them at the same time. Forms, and any of the three added to a table that already exists, are born in a table's view bar, under the Channels group — open the table you want records filed into and add one there. Email In and Webhook In are set up from that same group, on their own pages. Connectors live in Integrations, API clients and outgoing webhooks in Developers, and an automation webhook is an automation with a “webhook received” trigger, created in the automation editor. Channels itself is a list, not an editor. Every row links to the page that already manages that channel, so pausing, editing and deleting all happen where the rules for them live. Who can see it Workspace admins. The rows carry the public tokens that are the whole authentication for the anonymous surfaces, so the list is closer to a set of credentials than to a report. Members see an ask an admin note instead — which matches the view bar, where adding a channel already needs admin. Tips • Filter by table to answer "how does anything get into this table?" in one screen. • Copy any address straight from the list — the button next to it copies the full URL, ready to paste into a site or an email. • The last-activity column is the fastest way to spot a channel nobody uses any more: sort your eye down it and pause what has been silent for a year. • A channel that shows a warning — a webhook failing repeatedly, a connector needing reauth, an expired share — says so on its row rather than waiting to be discovered. Good to know • The Channels group in a table's view bar creates the three kinds a view can host, and links to Email In and Webhook In, which have their own pages. Automation webhooks, connectors, API clients and outgoing webhooks live elsewhere — the full picture is on /Channels, which is what the group heading links to. • The total beside each channel is its whole life, not the last week. A busy form and a form that was busy two years ago can show the same number; the last-activity column is what tells them apart. • Pausing a form, widget or booking page stops it answering but keeps everything already collected. Deleting one is different — the public link stops working immediately and cannot be restored, though the records it created are untouched. • A shared view link with a date on it reads as Paused once that date passes. It has not been turned off by anyone; it has simply expired, and the row says so. • A connector can sync into several tables at once. Where that happens the table column says how many rather than naming one, because naming one would be a half-truth.