Skip to main content

Workflows

Workflows are repeatable Row-Bot tasks. Use them for things you want to run again: a morning brief, inbox follow-up, document digest, research check, report draft, or channel delivery.

For the execution model behind schedules, persistent runs, approvals, and delivery, read How Background Workflows Run.

Row-Bot Workflows tab.
The Workflows tab shows workflow cards, delivery defaults, run controls, and the New Workflow entry point.
Row-Bot New Workflow editor.
The editor brings prompts, schedules, delivery, Agent Profiles, multi-step behaviour, and approval policy into one reviewable workflow definition.

Where To Find Workflows​

Open Home -> Workflows. The Home tab is the dashboard; this page is the full guide.

UI Walkthrough​

  • Workflow list shows saved workflows, status, next run, and quick actions.
  • New Workflow opens the creation flow.
  • Delivery defaults choose where results go unless a workflow overrides them.
  • Run starts the selected workflow manually.
  • Pause/resume controls whether scheduled runs continue.
  • Edit opens the saved workflow for changes.
  • Delete removes a workflow after confirmation.
  • Status labels show whether a workflow is ready, paused, running, waiting for approval, or needs attention.

Basic Workflow Creation​

  1. Click New Workflow.
  2. Give the workflow a clear name.
  3. Describe the task Row-Bot should perform.
  4. Choose when it should run: manual, scheduled, or triggered when that option is available.
  5. Choose delivery: app only, a channel, or another configured destination.
  6. Save the workflow.
  7. Run it manually once and review the result.

Advanced Workflow Creation​

Advanced workflows can include richer instructions, required inputs, model/profile choices, delivery overrides, approval rules, and multi-step behavior. Keep each step observable: what information Row-Bot should gather, what it should produce, where it should save or send output, and what requires your approval.

What Is Saved​

Workflow definitions, schedules, run history, delivery defaults, and status are local Row-Bot data. Results may be sent to channels only when configured and selected.

Safety​

Avoid workflows that send messages, write files, start servers, or call external systems without a review point. Use approvals for actions that can affect files, accounts, channels, MCP servers, plugins, or external services.

Troubleshooting​

  • If a workflow does not run, check whether it is paused.
  • If delivery fails, check the selected channel and its Settings tab.
  • If a run waits for approval, decide from the thread prompt or open the Activity Center.
  • If results are too broad, split the workflow into smaller steps.