Jobs

Orchestrate complex data operations by combining workflows

Overview

Jobs are collections of workflows organized with a specific execution order. They allow you to orchestrate complex, multi-step data operations by combining multiple workflows into a coordinated sequence.

Jobs serve as the primary mechanism for executing workflows. Rather than running individual workflows in isolation, you create a job that defines which workflows to run and in what order. When you execute a job (and therefore create a job run), Anon executes each workflow in sequence.

Key Concepts

Job Configuration

A job consists of:

• Name: A descriptive identifier for the job
• Source Provider: The primary system the job operates on
• Job Config JSON: A configuration object containing the workflow execution order

The jobConfigJson field contains:

• workflowExecutionOrder: An ordered array of workflow IDs that defines the sequence of execution

Example:

{
  "workflowExecutionOrder": [
    "550e8400-e29b-41d4-a716-446655440000",  // Workflow ID for login workflow
    "661f9511-f3ac-52e5-b827-557766551111",  // Workflow ID for the 'Extract Employees' workflow
    "772fa622-g4bd-63f6-c938-668877662222"   // Workflow ID for the 'Payroll Journal' workflow
  ]
}

Job Purpose

Jobs represent what you want to accomplish, while workflows represent how to accomplish individual steps. For example:

• Job: “Daily sales report extraction”
• Workflows:
  1. Authenticate with POS system
  2. Extract sales data
  3. Extract payments reports
  4. Download gift card transactions

Sequential Execution

Workflows in a job execute sequentially based on the workflowExecutionOrder, but each workflow runs in complete isolation. No data, state, or context is shared or transferred between workflows in a job—each operates independently. This ensures:

• Strict separation between workflow executions
• No implicit dependencies between workflows
• Predictable and reproducible behavior regardless of execution order

Use Cases

Jobs are ideal for:

• Complete data migration workflows from authentication to extraction
• Periodic data synchronization tasks (daily, weekly, monthly reports)

API Operations

Create a Job

Create Job

Create a new job with a defined workflow execution order

List Jobs

List Jobs

Retrieve all jobs for your organization with pagination support

Get a Job

Get Job

Retrieve complete details for a specific job, including its workflow execution order

Update a Job

Update Job

Modify a job’s name or workflow configuration

Delete a Job

Delete Job

Remove a job from your organization

Schema Reference

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