Skip to main content

​
Overview

Workflows are the fundamental building blocks of Anon. Each workflow represents a customizable, AI-powered sequence of browser automation steps that performs a specific task within a source system (e.g., logging in, extracting screenshots, retrieving reports). Anon empowers you to create, define, and modify your own workflows through the API or through the dashboard.

​
Key Concepts

​
Workflow Definition

A workflow consists of:
  • Name: A descriptive identifier for the workflow
  • Source Provider: The system of record the workflow operates on (e.g., gusto, toast, quickbooks)
  • Steps: A structured JSON definition of the actions the AI agent should perform
  • Type: Either LOGIN (for authentication workflows) or USER_DEFINED (for custom operations)
The stepsJson field is the heart of a workflow. It defines:
  • The sequence of steps to execute
  • Input parameters required for execution
  • Workflow analysis and metadata
  • Version information

​
Workflow Types

Login Workflows are special workflows designed to authenticate with source systems. They typically:
  • Handle credential input
  • Navigate authentication flows
  • Verify successful login
  • Store session state
User-Defined Workflows are custom workflows you create for specific data operations. Examples include:
  • Extracting employee records from HRIS systems
  • Downloading daily sales reports from a POS system
  • Retrieving invoice data from Amazon Business accounts
  • Updating payroll configuration settings

​
API Operations

​
Create a Workflow

Create Workflow

Create a new workflow with custom step definitions

​
List Workflows

List Workflows

Retrieve all workflows for your organization with pagination support

​
Get a Workflow

Get Workflow

Retrieve complete details for a specific workflow, including its full step definition

​
Update a Workflow

Update Workflow

Modify an existing workflow’s name or steps
Updating a workflow affects future executions but does not change already-running workflow runs, which use a snapshot of the workflow at execution time.

​
Delete a Workflow

Delete Workflow

Remove a workflow from your organization

​
Workflow Execution Flow

Workflows are executed as part of jobs. Here’s how workflows fit into the broader Anon flow:
  1. Define Workflows: Create workflows for each operation you need (login, data extraction, etc.)
  2. Create a Job: Organize workflows into a job with a specific execution order
  3. Execute the Job: Create a job run, which triggers workflow runs for each workflow in sequence
  4. Monitor Workflow Runs: Track the status of individual workflow executions
  5. Access Artifacts: Retrieve data and files generated by successful workflow runs

​
Relationship with Other Resources

  • Jobs: Reference workflows in their workflowExecutionOrder configuration
  • Workflow Runs: Created when a workflow is executed as part of a job run
  • Artifacts: Generated by workflow runs and linked to the workflow that created them

​
Best Practices

​
Workflow Design

  1. Keep Workflows Focused: Each workflow should accomplish a single, well-defined task
  2. Make Workflows Reusable: Design workflows that work across different accounts or contexts
  3. Use Clear Naming: Choose descriptive names that indicate the workflow’s purpose and provider
  4. Document Input Schemas: Clearly define required inputs in your workflow definition

​
Workflow Management

  1. Test Before Production: Execute workflow runs in test mode before using in production jobs
  2. Update Incrementally: Make small, incremental changes and test after each modification
  3. Maintain Login Workflows: Keep authentication workflows separate from data operation workflows
  4. Monitor Execution: Regularly review workflow run results to identify needed improvements

​
Schema Reference

See the API Reference for complete schema definitions and field descriptions for the Workflow resource.