Workflow order and firing logic

Understanding when and how workflows fire helps you predict exactly which calls will be processed, in which order, and what happens when multiple workflows apply to the same call.

When a workflow fires

• A workflow fires when a call, form submission, or SMS event matches its trigger and passes all its filters.
• Nimbata evaluates workflows at the moment the trigger event occurs
• E.g. At call end for a Call ends trigger, or at the moment a form is submitted for a Form submitted trigger.

• Each workflow is independent.
• If a call matches multiple workflows, all matching workflows will fire.
• There is no automatic exclusivity between them unless you build it in using filters.

Workflow evaluation order

When multiple workflows are enabled and a call qualifies for more than one, Nimbata evaluates them in the order they appear in your Workflows list, from top to bottom.

To reorder your workflows:

• Go to Workflows.
• [PLACEHOLDER: confirm whether drag-and-drop or a dedicated reorder control is available to change workflow list order.]

Trigger timing options

Each trigger has sub-options that control exactly when in the call lifecycle the workflow fires:

Inbound call / Outbound call:

• Call starts: Fires as soon as the call begins, before it is answered or ended.
• Call ends: Fires after the call has fully completed. Use this for transcription, summarization, conversion sending, or any action that needs the full call data.
• User updates property: Fires when a user manually changes a field, tag, rating, or value on a call record. Use this for manual approval workflows.

Form submitted:

• On submission: Fires immediately when a form lead is received.
• On property update: Fires when a field on a form record is updated manually.

SMS received:

• Fires as soon as an inbound SMS arrives on a tracking number.

Filters and how they affect firing

• Filters narrow which calls within a trigger actually proceed to the action steps.
• A call that matches the trigger but fails a filter condition stops at that filter and no actions are executed for it.
• If you use multiple filters in the same workflow, all filter conditions must be met for the call to proceed (AND logic).
• There is no built-in OR logic between separate filter blocks within a single workflow.
• To achieve OR behavior, create two separate workflows.

Actions and execution

• Actions run in the order they are stacked in the workflow builder, from top to bottom.
• If an action fails, subsequent actions in the same workflow still run.
• A failed action does not halt the rest of the workflow.

Re-running and manual triggers

Workflows do not re-run automatically on historical calls. If you need to apply a workflow to a past call, see:

Detailed guide: How to re-run a workflow or part of it

Detailed guide: Workflow rules and tasks: what's available and how they work

Detailed guide: How to set up your first workflow

Updated on: 03/04/2026