Bot Hub is the operational control room for the workflow currently open in the editor. It answers five questions quickly: is it healthy, what ran, what did the bot send, what can it access, and where should you work next on the current workflow?
Bot Hub does not replace bot or workflow settings. Changing tokens, identity, presence, the workflow graph, or its permanent Discord binding stays in the existing dashboard surfaces made for those jobs.
Press Ctrl + K anywhere in Bot Hub to find a tool, recent execution, or recent message by its Discord or Flowmatic identifier.
Overview
The dense Overview combines the bot connection, workflow deployment health, the selected server, runs from the last 24 hours, success rate, median duration, suppressed events, and recent sent messages. Its recommendation center computes an operational score and links each warning or suggestion to the exact tool that can explain it.
Executions
The Executions tab provides a master-detail run inspector. Filter runs by status, active state, or suppression, then inspect:
- the trigger and exact timestamps;
- every executed, skipped, or failed node and its duration;
- the failure message or suppression reason;
- messages produced by that execution;
- retry and cancellation controls when your workflow access allows them.
Selecting a step returns to the canvas and focuses that node.
Live Activity
Live Activity merges workflow executions, deliberately suppressed events, and bot ledger posts into one continuously refreshed timeline. Pause the feed while investigating a sequence, filter it by failures or suppressions, expand recent step logs in place, or copy a redacted diagnostic report for support.
Workflow Assist
Workflow Assist is a read-only extension of the canvas, not a second workflow editor. It analyzes the draft currently open in the editor, including unsaved changes, and combines that structure with the latest 100 stored executions.
Its priority queue ranks exact lint issues and observed runtime failures. A selection opens the relevant node and, when known, the precise configuration field in the editor. The change-impact lens shows every upstream and downstream step affected by one node, while trigger pathways reveal reachability, runtime capability gates, terminal paths, and actions behind each entry point. Runtime evidence identifies nodes that failed, were skipped, ran slowly, or have never been reached. A compact handoff report can be copied for support without changing the graph.
Messages
Choose a visible text channel and write directly in the Discord-style composer to send a one-off message with the workflow bot. Press Enter to send or Shift + Enter for a new line. The advanced composer adds visual embed, button, and select-menu builders with a live preview; it does not add nodes to the workflow.
Select a ledger message to reply, react, pin or unpin, create a public thread, or send a copy to another visible channel. Drafts survive tab changes on the current device, and an optional timer can automatically delete a new message.
Every Discord message sent through the workflow or direct composer is stored in the bot ledger with its server, channel, bot connection, workflow, execution, and live Discord link. The payload is redacted and size-capped before it is persisted.
The visual editor can update content, embeds, buttons, and select menus on the live message without assembling another workflow. You can also send a copy, delete the live message while keeping its audit tombstone, or forget only the ledger entry. Message content is owner-only on shared workflows.
Discord access
Discord access is read-only. It shows the resources the workflow owner's bot can currently see on the selected server: channels, roles, cached members, and webhooks. Owners also see gateway intents, missing permissions, the bot's highest role, and how many roles sit above it in the hierarchy.
Permission Solver checks one action in one channel after Discord category and channel overwrites are applied. Resource Health also detects static channel and role IDs used by workflow nodes that no longer exist in the selected server.
This view never grants a permission or moves a role. Apply those changes in Discord, then refresh the diagnosis.
Capabilities
Capabilities are runtime switches scoped to this workflow. Available families include slash commands, messages, members, reactions, components, voice, moderation, and other server events. Maintenance mode suppresses all of them at once.
Turning a capability off does not unregister commands or detach listeners. The gateway continues receiving events, filter matches are evaluated, and Bot Hub stores a terminal Suppressed execution instead of enqueuing the graph. For slash commands, buttons, menus, and modals, you can provide a private Discord response. A suppression may last indefinitely or automatically expire after a chosen duration.
Operational modes apply common groups of gates at once: Normal enables all families, Maintenance acknowledges everything without running the graph, and Commands only keeps slash commands and components while suppressing passive Discord events. Each family shows how many events it suppressed during the last 24 hours.
Analytics and audit
Analytics reports execution volume, success rate, P95 duration, trigger distribution, recurring failures, suppressions, and bot message activity from the latest 100 executions over 24 hours, 7 days, or 30 days. Precision insights call out degraded deployment, slow interaction paths, unusual suppression volume, and repeated failures. The operational audit combines runs, bot posts, edits, deletions, and capability changes without exposing bot credentials.