> You are reading the Docusign Developer Documentation. For clean Markdown of any page, append .md to the page URL.
>
> Documentation indexes by section:
> - APIs and SDKs: https://docusign.docs.buildwithfern.com/docs/llms.txt
> - Platform 101: https://docusign.docs.buildwithfern.com/platform/llms.txt
> - Extension Apps: https://docusign.docs.buildwithfern.com/extension-apps/llms.txt
> - Docusign CLI: https://docusign.docs.buildwithfern.com/docusign-cli/llms.txt
>
> Authentication (OAuth, JWT Grant, M2M): https://docusign.docs.buildwithfern.com/platform/auth
> Webhooks and Connect: https://docusign.docs.buildwithfern.com/platform/webhooks
>
> OpenAPI specifications: https://docusign.docs.buildwithfern.com/openapi.json
> MCP server: https://docusign.docs.buildwithfern.com/_mcp/server

# Branching rules

> See how you can use branching rules to implement conditional paths in your workflows.

A *branching rule* is a step that branches your workflow into one of two different paths, depending on the result of an if/else step. You can add a branching rule before or after any app step (such as identity verification or a web form), and then define the next actions to take if the branching rule is met or not.

For example, you could add a branching step after a web forms step, to check whether a customer-supplied account number matches the account number on record. Depending on the result, the customer can be directed to a signature process or additional identity verification steps.

![Screenshot of an example branching rule.](/_fern-files/_img/369a6811be32b2475cb6e3edd6a06e169ec581dc1813b5e6bbcb2c93d791f50b.webp)

## Next steps

* [Steps](/docs/workflow-builder-api/workflow-builder101/steps)
* [Workflows](/docs/workflow-builder-api/workflow-builder101/workflows)
* [Variables](/docs/workflow-builder-api/workflow-builder101/variables)
* [Participants](/docs/workflow-builder-api/workflow-builder101/participants)