Build a branching CRM workflow with approved dependencies

Before you begin

Choose the source type first: contact, company or lead. Plan a small journey with a clear starting step and ending paths before adding branches.

Follow these steps

1. Create a workflow and select its source. Add steps with unique identifiers and choose the starting step.
2. Choose each step’s action and complete its fields. Connect Next; for a condition, also choose Otherwise. Leave an ending connection blank.
3. For Recalculate score, select a published approved model for the same source. For Queue marketing email, choose a published approved email and explicitly authorise delivery.
4. Validate the complete graph, save and use Test with a record. Review both condition outcomes where possible.
5. Obtain independent approval and publish. Enrol a record manually or use the separately configured future-event trigger.

Fields and options

Nine step types

Condition, Set lifecycle, Add score, Recalculate score, Queue marketing email, Task, Note, Draft and Delay.

Graph

1–40 steps, unique IDs, a valid start, no cycles and no unreachable steps. Only a condition has an Otherwise branch.

Action limits

Score changes are −100 to 100, with profile totals bounded to −1,000…1,000. Delay is 1–525,600 minutes.

Rules and limits

• Queued marketing requires contact or lead source, current permission, recipient consent, no suppression and the outbound setting. A company is not a marketing recipient.
• Saved dependency revisions are checked again; changing a referenced email or model can block execution until the workflow is reviewed again.
• A workflow cannot call arbitrary external APIs or generate external AI content in this release.

Check the result

• Dry-test a record that follows each branch and inspect the proposed actions.
• After a deliberate live enrolment, check that only the expected profile, activity, task or queue rows were created.

If something does not look right

• A cycle or unreachable-step error needs the graph repaired, not a different record.
• If a dependency is unavailable, check source type, current publication, revision and your visibility.

Common questions

Related tasks

Browse all Sales & Marketing Hub guides