Each platform has its own section under Bots in the sidebar: Discord, Twitch and YouTube. Pick the bot or channel at the top of the section; every page below it then shows that account only.
Where to go
| Task | Destination |
|---|---|
| See a bot's health and workflows | Bots → platform → Overview |
| Install or configure a module | Bots → Discord → Installed / Browse modules |
| Compose or find a sent publication | Bots → platform → Messages |
| Inspect information saved between runs | Bots → platform → Data |
| Follow the runs of one bot | Bots → platform → Activity |
| Follow every run of the workspace | Operations |
| Connect a bot or repair its access | Connections |
| Diagnose the current draft | Editor → Diagnose |
| Inspect workflow Discord resources | Diagnose → Discord resources and access |
| Configure runtime maintenance | Workflow Settings → Runtime controls |
Modules
Modules are ready-made features installed in one Discord server for the selected bot: welcome and goodbye messages, autorole, role picker, custom commands, word filter, server logs, leveling and live alerts. Pick the server at the top right, then install a module from Browse modules. A module that still needs a setting stays off until the setting is filled.
Every module is a step group of one workflow per server and bot, so its runs appear in Activity and Operations like any other workflow. Customize in editor opens it on the canvas. After a change on the canvas, the module page stops rewriting it and shows Edited in the editor; uninstalling such a module is done in the editor too, so no manual change is lost.
Messages
Each Discord bot's Messages page lists its outgoing publications; a Twitch channel's page lists the chat messages its workflows posted. Select the server and channel explicitly before composing as a Discord bot. You can publish content, embeds and supported components without creating a workflow.
Search and filter the retained history by connection, destination, origin, workflow or execution. A manual publication stays manual even when it links to a source workflow. A manual copy links to its source without inventing an execution.
Open a publication to compare its saved snapshot with its live state. Compose and edit directly in the page, with the same rich content controls as the workflow editor and a Discord preview. Depending on access and availability, you can reply, react, pin, open a thread, send a copy, delete the Discord publication or remove only its history entry. The saved snapshot may differ from the current remote message.
Drafts are kept on the current device for your account and selected destination. An optional deletion timer is stored on the server; an offline bot can delay deletion until it reconnects.
History retains up to 5,000 entries per account. Stored content is redacted and limited to 64 KiB, with up to 20 previous snapshots. This history is not an incoming message inbox.
Data
Data lists values, records, lists and rankings saved in your account. A saved name is shared across workflows that use it; changing the workflow filter does not create a separate copy or change ownership.
Use search and filters to find your saved data, then open its values and workflow uses. Internal Discord runtime keys are hidden from the default list. The optional system data view is read only; these keys cannot be created, edited, imported or deleted here. Known workflow uses can be incomplete while older data is being indexed. Only the account owner can access persistent account data; sharing a workflow canvas does not share its saved values.
The typed detail supports creation, editing, import and export where the stored kind allows them. Concurrent writes produce a conflict instead of silently replacing a newer revision, and edits preserve the existing expiration. Managed state, masked content and truncated previews remain protected.
Inspection is limited to 200 elements and 64 KiB per item. A partial preview is identified and is not offered as a complete editable value. Temporary variables and execution samples stay in their workflow or run context.
Activity
Activity has four views:
- Live follows active and recent runs. Pause the display while inspecting a sequence.
- Runs searches and filters execution history. Open a run to inspect its steps, data, errors and available retry or cancellation actions.
- Ongoing shows tickets, giveaways, waits and sessions for the selected workflow.
- Analytics reports execution volume, success rate, duration and trigger distribution for the chosen period and workflow. Lists ranked by lifetime activity are labelled separately.
A Suppressed event was blocked by a runtime policy before the workflow ran. Its recorded gate and reason explain the decision; it is distinct from a normal cancellation and does not create a fictitious successful step.
Diagnose and Discord access
Open Diagnose in the editor to inspect problems in the current draft. Workflow insights combines the draft structure with recent execution evidence and links issues to their relevant step.
Discord resources and access inspects channels, roles, cached members, webhooks and other available resources. Select a server locally for inspection; this does not save new workflow defaults. Missing static channel or role references link back to their step.
The owner can inspect effective channel permissions and follow Manage selected bot to Connections. Collaborators retain only the inventory and diagnostics their workflow access allows. Apply permission or role changes in Discord, then refresh the diagnosis.
Runtime controls
Workflow Settings → Runtime controls configures maintenance and gates for Discord trigger families. These controls remain specific to that workflow; they do not pause every connected service.
Use the workflow's published status and deployment state to check what is actually live. Saving a draft and publishing it remain separate actions.
See getting started, workflow extensions and testing and debugging for the full build, test and publication path.