Skip to main content

Using branch blocks in workflows

Control workflow paths by routing execution based on conditions.

Joe Hatchett avatar
Written by Joe Hatchett
Updated over 2 weeks ago

Branch blocks allow a workflow to make decisions by splitting execution into two paths based on whether conditions are met.

They are useful for approvals, validations, and conditional notifications.


How Branch Blocks Work

  • A branch block evaluates configured conditions

  • If conditions are met, the true branch is executed

  • If conditions are not met, the false branch is executed

Each branch can contain its own actions, waits, or additional logic.


Branch Conditions

Branch conditions can be based on:

  • Is first created

  • Is updated

  • Is waiting review

  • Is completed

  • Is archived

  • Form field values

Conditions depend on the resource being evaluated.

Example:
If a form is completed correctly, send a confirmation email.
If not, request changes from the worker.


When to Use a Branch Block

Use a branch block when you need to:

  • Apply conditional logic

  • Handle approvals vs rejections

  • Send different messages based on form responses

  • Prevent unnecessary notifications


Best Practices for Branch Blocks

  • Keep conditions clear and easy to understand

  • Use branches to reduce duplicate workflows

  • Review workflow runs to confirm expected behaviour


Need Help?

If you have questions or need assistance using branch blocks, use the black chat box in the bottom-right corner to contact the BuildPass support team.

Did this answer your question?