Creating a Workflow
A Process is your workflow's blueprint — the named, versioned graph of nodes and edges that defines what happens. You create Processes inside a Project, then create executable instances (ProcessThreads) from them.
Blank vs Template
When you click + New Process in the Processes panel, a dialog appears with two options:
Blank Canvas
Starts with an empty graph. You design every node and connection yourself. Best for unique or experimental workflows.
From Template
Start from a pre-built pattern (e.g., HR Approval, Invoice Processing). The template nodes are pre-wired but fully editable.
Process Fields
| Field | Required | Description |
|---|---|---|
| Name | Yes | Unique within the project. Used in the dashboard list and execution logs. |
| Description | No | Purpose and scope of this workflow. |
| Category | No | Tag for filtering in large projects (e.g., "HR", "Finance", "DevOps"). |
| Trigger Type | Yes | How this workflow starts: Manual, Webhook, Schedule, or Form Submission. |
| Version Label | No | Semantic version string (e.g., "1.0.0"). Defaults to "1.0.0" for new processes. |
Versioning
Processes maintain a version history. Each time you publish a ProcessThread, a snapshot is recorded. You can view all published versions and revert to any of them.
Draft
Every new Process starts as a draft. You can create threads from it, but draft processes cannot be triggered by scheduled or webhook triggers.
Published
A published Process version can be triggered externally and is visible to viewers. Publishing locks the version — changes require creating a new draft version.
Archived
Old versions can be archived to reduce clutter. Archived versions are read-only and cannot be executed, but their history is preserved.
Trigger Types
| Trigger | Description | Configured By |
|---|---|---|
| Manual | Started by a user clicking Run in the studio | No configuration required |
| Webhook | HTTP POST to a generated endpoint starts the workflow | Webhook URL generated after publishing |
| Schedule | Cron expression triggers at a regular interval | Cron expression (e.g., 0 9 * * MON-FRI) |
| Form Submission | Triggered when an Atlas Form is submitted | Select the Form ID in process settings |