Skip to main content

Workflows

Workflows in Revelry Ai are structured workflows for artifact generation. Unlike chat's free-form conversation, workflows follow predefined steps that you configure.

What Are Workflows?​

Workflows are a set of predefined steps that execute AI operations in a particular order. Each step can:

  • Generate content using prompts
  • Call MCP tools for data retrieval
  • Process outputs from previous steps

Key difference from Chat: Workflows follow a predetermined sequence, while chat allows flexible exploration. Both can use MCP tools.

When to Use Workflows​

Use workflows when you need:

  • Repeatability - Same process every time
  • Quality control - Add validation steps between stages
  • Complex workflows - Break generation into manageable stages
  • Organization standardization - Ensure consistent processes

Use Chat instead when you need:

  • Free-form exploration and conversation
  • Highly iterative refinement
  • Flexibility without predefined steps
  • Quick, one-off artifact generation

How Workflows Work​

Workflows execute through these stages:

  1. Configuration - You define the workflow steps and links between them
  2. Execution - User triggers the workflow to start
  3. Processing - Each step runs in sequence, potentially using MCP tools
  4. Output - Results are saved as artifacts

Implementing Quality Control​

While workflows don't have built-in QA/QC or conditional logic, you can still add validation steps to your workflow:

  • Review steps - Create steps that analyze outputs from previous steps
  • Validation prompts - Design prompts that check for accuracy or completeness
  • Human review - Add steps that present results for manual inspection

Note: All steps execute sequentially. There's currently no way to stop execution based on validation results.

Workflow Components​

Steps - The building blocks of your workflow. Each step uses a skill that may require inputs.

Links - Connections between steps that determine how outputs flow from one step to another. You can link a source step's output to a destination step's input.

Triggers​

How workflow execution is initiated:

  • User-initiated - Run from the UI
  • API - Programmatic triggering via the Workflows API
  • Scheduled - Time-based execution (coming soon)
  • Event-based - Triggered by platform events (coming soon)

Note: Inputs are defined by the skills used in each step, not by the workflow itself. Steps can require user inputs (provided at runtime) or use outputs from previous steps via links.

Building Your First Workflow​

  1. Create skills for each step (these define what inputs are needed)
  2. Configure the workflow - Add steps and create links between them
  3. Test and refine - Run the workflow and improve based on results

Learn more: Creating Workflows

Workflow Runs​

Each time you trigger a workflow, it creates an Workflow Run that tracks:

  • Step-by-step execution progress
  • Success or failure status
  • Generated artifacts
  • Processing time and logs

Learn more: Workflow Runs

Next Steps​