Skip to main content

What conditional actions do

The If / Else action lets you branch your automation into different paths based on field values. Each branch has its own set of actions that only run when the branch’s condition is met. If no branch matches, the fallback (else) actions run.

How branches work

A conditional action contains:
  • Branches with a label, a filter condition, and a list of actions
  • Fallback actions (else) that run when no branch condition matches
Each branch is evaluated in order. The first branch whose condition matches runs its actions. If none match, the fallback runs.

Setting up conditional actions

1

Add an If / Else action

In the Automations tab, add an action and select If / Else.
2

Define a branch

Give the branch a label (e.g., “High priority”) and set a filter condition using the filter builder. For example: Priority is High.
3

Add actions to the branch

Add one or more actions inside the branch. These only run when the branch condition is met. Available actions include Update Submitted Record, Generate PDF, Webhook, and Wait.
4

Add more branches (optional)

Add additional branches for other conditions. Each branch has its own label, condition, and actions.
5

Set fallback actions

Add actions to the fallback (else) section. These run when none of the branch conditions match.

Example

You have a form that collects support requests with a “Category” select field. You want to:
  • Send a webhook to the billing team when Category is “Billing”
  • Send a different webhook to the technical team when Category is “Technical”
  • Update a status field to “Unrouted” for everything else
Set up an If / Else action with two branches and a fallback:
  1. Branch “Billing”: Condition Category is Billing, action: Webhook to billing endpoint
  2. Branch “Technical”: Condition Category is Technical, action: Webhook to technical endpoint
  3. Fallback: Update Submitted Record, set Status to “Unrouted”

Limitations

  • Branches contain leaf actions only. You cannot nest an If / Else action inside another If / Else action.
  • Each branch’s condition uses the same filter builder used in display conditions and other Filla features.

On-submit automations

Overview of the automation system and action types.

Building filter rules

How to build the filter conditions used in branches.