Reliable workflow design
Updated
A reliable workflow creates the right project from the right CRM record every time, and fails in a way you can see when it can't. Most of that comes from design choices you make while you build it: the trigger, the order of branches, what happens when nothing matches, and how you test and publish changes.
When to use it
Use these principles when you build a new workflow, when you add branches to an existing one, and before you publish changes to a workflow that's already creating projects.
How it works
Start with one clear trigger
A trigger is the CRM event and conditions that start a workflow. Start with one unmistakable moment in your CRM, such as:
Deal Stage = Closed Won
Opportunity Stage = Implementation Ready
Contract Signed = True
Avoid overlapping field conditions, broad pipeline rules and open-ended conditions until the simple version works. The narrower the trigger, the fewer records it catches by accident.
Make sure the CRM data is there
If the workflow depends on account lookups, owner mappings, custom fields or contract values, check them in your CRM. Fields should be filled in before the record reaches the trigger stage, and the integration user needs access to them. These settings live in your CRM, not in OnRamp.
Order branches from most specific to least
The playbook step checks its branches from the top, and the first branch that matches is used. Branches lower down never run for that record. Put the most specific conditions first, then broader ones, then the default branch:
Enterprise
Mid-market
Standard
Default
Conditional modules work differently. In that step, every condition block that matches adds its modules, not only the first.
Use Stop on purpose
Each branch of the playbook step uses either Playbook or Stop. A branch set to Stop ends the run for that record without creating a project. Use it for readiness gates, such as stopping when required data is missing.
The default branch has no conditions, so it handles every record that no other branch matches. Decide whether those records should get a project or stop. A branch can use Stop only if at least one other branch creates a project from a playbook.
Plan for fallbacks
Some settings decide what happens when a run can't complete a step as planned:
Round robin owners: when everyone is at capacity, a run can assign the project anyway, try the next condition, or fail the run. See Set up a workflow to create projects.
Workspace: when workspaces are turned on for your organization, a playbook branch has a Workspace setting. If you set it to From trigger object, each run matches a field's value to a workspace name. For a value that matches no workspace, When no workspace matches decides what happens: Use the playbook's workspace, Use a specific workspace, or Fail the run.
A failed run is visible and can be fixed. A quiet fallback is convenient but can hide a data problem, so choose on purpose.
Use approval mode while you roll out
The Create Project step has two modes: Create automatically and Wait for approval. A new Create Project step starts on Create automatically. While you roll out a workflow, set it to Wait for approval so each run waits for someone to review it. Check the playbook, owners and account on a few runs, then switch to Create automatically. To review waiting runs, see Troubleshooting workflow project automation errors.
Keep branching manageable
If a workflow has many branches or repeats the same logic, consider splitting it into separate workflows, simplifying the playbooks, or moving logic into conditional modules.
Publish changes deliberately
Your edits are saved to a single draft, which takes the next version number. Saving the draft again doesn't add more versions. The new version goes live only when you select Publish. Each run shows the version that handled it, and you can review earlier versions when behavior changes. Treat publishing like a production change.
Test the edge cases
Before you publish, test more than the ideal record. Try a record with a missing field, one that matches no condition, one that should stop, and one that should go to a different branch. The Debug button in the workflow editor runs the saved workflow against a record you choose. See Test a workflow with Debug.
After the workflow is live, check its runs. Each run shows how the record was handled, including which conditions matched.
Limits
Field requirements and integration-user access are set in your CRM, so OnRamp can't enforce them.
The first-match rule applies to the playbook step's branches only. Conditional modules add modules from every matching block.
A workflow always needs at least one branch that creates a project from a playbook.