Conditional automation steps

Conditional automation steps

Use If when one trigger needs different actions. For example, when a website inquiry arrives, if its form name is Seller, create a seller follow-up task; otherwise create a qualification task.

Build a branch

  1. Open an automation and choose an event trigger or A record matches a saved view.
  2. Under Then, choose Add step → If a condition matches.
  3. Choose All conditions match or Any condition matches and set the conditions.
  4. Add actions to Then. Optionally add actions to Otherwise.
  5. Save the automation. Activate it when ready.

Only the selected branch runs. An empty Otherwise does nothing. After that branch finishes, later steps continue. Add multiple If steps to test independent conditions from the same trigger. Branches contain actions; nesting another If inside a branch is not supported. An automation supports ten actions total, counting both branches, and up to ten conditions per If.

Conditions you can use

  • Deal stage changes: new or previous stage, or whether the related property matches a saved view.
  • File uploads: file kind.
  • Website inquiries: form name, contact name, contact email, or whether the related property matches a saved view.
  • Matched records: whether the property, person, or company matches another saved view of the same record type.

Saved views use their current filters and members, including supported custom and formula fields, at the time the step runs. Create or edit those filters in Database. Changing a view also changes the automation's condition.

Text comparisons ignore letter case. Use Is, Is not, Contains, Is present, or Is missing. A missing value does not satisfy Is not; use Is missing explicitly. Scheduled automations have no trigger record, so they do not offer If conditions.

Review and missing data

Branch actions follow the same approval rules as other automation actions. Pre-approval still applies only to deterministic actions, not work composed by the assistant. If a required record or saved view is missing, or a view's filter cannot be evaluated, the automation stops for review instead of choosing a branch. A blocked action stops the remaining branch and later steps. Approving the prepared action replays that action; later steps are not automatically resumed.