Overview
Workflows live at Workflows. Each workflow starts with a trigger, can branch through conditions, and then runs one or more actions. Use them to keep records moving without manual follow-up: notify an owner when a big deal is created, post a note when a stage changes, or generate an invoice on a schedule.
New workflows start as a Draft. A workflow can be Draft, Active, Paused, or Archived; only Active workflows run.
Triggers
| Trigger | Fires when |
|---|---|
| Module Event | A record is created or updated in Clients, Contacts, Tasks, Deals, Projects, Inventory, Invoices, or Expenses. Only this trigger offers Event Conditions to filter which events start the workflow. |
| Scheduled | On a repeating cadence: every so many minutes (10 at the least), hours, days, weeks, months, or years, in the timezone you choose. |
| Webhook | An external system calls the workflow's endpoint URL with its shared secret. |
| Form Submission | Someone submits one of your forms. |
| Lifecycle stage / Deal Stage Change | A contact, deal, client, project, or expense moves between stages, with optional from and to rules. |
| Status Change | A task, project, inventory item, or invoice changes status, with optional from and to rules. |
Conditions
Conditions compare fields, grouped with Match All or Match Any logic. For example, only continue when the deal amount is greater than 10,000 and the stage is Negotiating. A standalone Condition step on the canvas branches the run into True and False paths.
Actions
Actions do the work: Find Record, Create record, Update record, Send notification, Send email, Send SMS, Assign owner, Move Lifecycle Stage / Deal Stage, Post Note, Create task, Create invoice, Update inventory, Log time, and Delegate to AI Agent, which hands a task to one of your agent accounts with the result routed to human review. Each action can run Immediately, After delay, or At scheduled time.
Reliability
Turn on Retry on failure for any action that talks to something fallible. If it fails, Scrambl retries it up to your Max attempts (2 to 10, default 3), waiting the same number of minutes between tries (5 by default). Every run is captured in Run history with per-step status and logs.
Best practice: Start with one narrow workflow and watch its Run history for a few days before adding more. Small, observable automations are easier to trust than one giant one.
Plans and access
Workflows are included with the Pro and Business plans. By default only owners and admins see the module; see Who can do this on each how-to article.
Next steps
- Build your first workflow in the visual builder.
- Start from a template.