Workflows

Use Workflows to turn repeated tasks into reliable operations. This page helps you create the workflow, run it, debug it, and schedule it.

​

Questions this page should answer

1. Which recurring task should become a workflow first?
2. Are runs completing with useful outputs, not just green status?
3. Where should we fix steps, inputs, or schedule to improve reliability?

​

Before you automate

• Start with one repeated task your team already does manually.
• Define the exact output you expect before building.
• Keep version one short and clear.

​

What this page gives you

• A workflow library with reusable cards.
• Fast creation from templates or from scratch.
• A full editor for step logic and sequencing.
• Per-workflow run, execution, and history views.
• Schedule controls for recurring runs.

​

How to read the workflow library

In the top section:

• Each card is one automation.
• The card title and subtitle tell you the business job.
• Last or Never run tells you adoption and recency.
• The three-dot action on cards helps with quick maintenance actions.

Use the table below cards as your global operations feed:

• Status: run health.
• AI credits: cost per run.
• Inputs: confirms run context.
• Started and Duration: speed and timing consistency.

When a run fails, inspect Inputs first, then step output.

​

Create workflow (template or scratch)

Use Create workflow to start from:

• Start from scratch for custom logic.
• Templates for common execution patterns.

Template-first is faster for most teams. Start from scratch only when your flow is unique.

​

Edit workflow (builder)

The editor is where you design and refine execution:

• Left panel: available step types.
• Center canvas: step order and flow.
• Right panel: AI assistant and properties.
• Top actions: run test, save, and chat-guided edits.

Keep steps explicit. Each step should do one clear job.

​

Workflow run tab (inputs and output)

This is the control panel for a specific workflow:

• Set run inputs (for example, Current Date).
• Confirm brand context before run.
• Click Run workflow to execute.
• Read final output in the right panel.

Use this view when you need a clean rerun with controlled inputs.

​

Execution tab (live step progress)

Execution helps you debug in real time:

• Left side shows each step and status.
• Right side shows details for the selected step.
• Running steps reveal where time is spent.

Use this tab to find bottlenecks, stalled steps, or weak step prompts.

​

Run progress state

During a live run, watch for:

• Step stuck in running too long.
• Empty or partial step output.
• Unexpected transitions between steps.

If one step repeatedly slows or fails, simplify that step before scaling schedule.

​

Workflow history tab (single workflow)

Use this tab to review reliability over time for one workflow:

• Compare run outcomes.
• Track AI credit trend.
• Validate cadence against business needs.
• Re-open older runs for QA checks.

This is the best view for per-workflow quality review.

​

Schedule a workflow (command action)

From workflow detail actions, open Schedule workflow and define cadence:

• Daily
• Weekly
• Bi-weekly
• Monthly
• Inactive

Set schedule only after the workflow is stable in manual runs.

​

What to automate first

Start with tasks that are frequent and rules-based:

• Daily or weekly priorities for SEO and content.
• Content refresh candidate detection.
• Alerting for major movement or failures.
• Structured summaries for stakeholders.

Keep one-off strategy prompts in New chat.

​

What to fix first

If runs are unstable, fix in this order:

1. Inputs (wrong or missing context)
2. Step prompt clarity
3. Step order and dependencies
4. Schedule frequency

Most failures come from bad inputs or vague step instructions.

​

Weekly workflow checklist

1. Review failed runs.
2. Check output quality for completed runs.
3. Improve one weak step in the top-used workflow.
4. Remove duplicate workflows and keep one source of truth.
5. Reconfirm schedule only for proven workflows.

​

Keep in mind

• Small reliable workflows beat large fragile workflows.
• Naming matters for discoverability and adoption.
• A successful status does not always mean useful output.
• Schedule is an operations tool, not a quality fix.

​

Where to go next

• Agents: assign the right specialist to each step
• Schedule: run workflows automatically
• New chat: prototype tasks before turning them into workflows