Building & Scheduling Workflows
A bot answers. A workflow acts — chaining triggers, bots, AI steps, logic, and integrations into one automation that runs on demand or on a schedule. This guide covers both ways to build one and how to put it on autopilot.
The two ways to build
Option A — Ask HiveMind (fastest)
In HiveMind, just describe what you want:
"When a lead comes in, score it with AI, and if it's a 7 or higher, alert my sales team in Slack."
HiveMind builds the graph and shows a workflow card in the chat. Click Open in builder to drop it on the canvas, adjust anything, and save. If you name your own bots ("have my Triage bot handle it"), they're wired in as real Bot nodes — running with their full tools and memory.
Option B — Build it visually
Open the Orchestrator, then:
- Drag nodes from the left palette onto the canvas.
- Connect them by dragging from one node's handle to the next.
- Click any node to configure it (the prompt on an AI step, the cron on a trigger, the operation on a database node).
- Hit Run to test, then Save. Reopen anything from My Workflows.
Node types at a glance
| Node | What it does |
|---|---|
| Starts the run — webhook, email, or schedule (cron) | |
| Runs one of your bots, with its own tools + memory | |
| A raw model call (Fast / Standard / Smart) | |
| Condition, switch, loop, filter — branches the flow | |
| Slack, Gmail, Notion, GitHub, DB, HTTP |
Branching with logic
A Condition node evaluates an expression and routes down its true or false edge. Set the branch on each outgoing edge so the executor knows which path a result takes.
textTrigger ──▶ Score (AI) ──▶ Qualified? (Condition) ├─ true ──▶ Alert Sales (Slack) └─ false ──▶ Ignore
A Switch routes by case; a Loop runs its body per item in a list.
Putting it on a schedule (cron)
Add a Schedule trigger and give it a 5-field cron expression. Set a Goal on the trigger too — on scheduled runs there's no live user input, so the goal gives the first step a concrete task.
text┌─ minute (0-59) │ ┌─ hour (0-23) │ │ ┌─ day of month (1-31) │ │ │ ┌─ month (1-12) │ │ │ │ ┌─ day of week (0-6, Sun=0) 0 9 * * 1-5 → 9:00am every weekday
Scheduled workflows are evaluated by Bothive's cron sweep and rate-limited against your plan. Sub-daily schedules (hourly, etc.) require a paid plan.
Running, history & credits
Hit Run to watch each node light up, or let a schedule/webhook fire it. Every run is recorded — open the Executions panel for per-node output and logs. AI and Bot steps consume credits (1 credit = 1K tokens) from your shared monthly pool; check the Usage page to see where you stand.
Tips
- Put a Fast model on routine steps (classification, yes/no) and reserve Smart for the hard reasoning — it keeps credit usage low.
- Chain bots for specialization: a Researcher → Writer → Publisher pipeline beats one do-everything bot.
- Start from a template in the templates gallery and customize, rather than from a blank canvas.
Use the test pane to iterate quickly. Every change you make is live — no need to save first.
API keys are shown only once. Store them securely and never commit them to version control.
Test your bot with edge cases before deployment. Try empty inputs, long messages, and special characters.
Chain multiple specialized bots in a workflow for better results than one general-purpose bot.