Sales & Marketing Hub
Build a branching CRM workflow with approved dependencies
Configure conditions, profile changes, scoring, follow-up work and approved email queueing in a valid workflow graph.
Where to start
Hub → Automation → Workflows → Create / Edit draft
Fields and options
- Access needed
- Manage automation resources; each action also needs its corresponding CRM, sales or delivery permission
- 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.
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
- Create a workflow and select its source. Add steps with unique identifiers and choose the starting step.
- Choose each step’s action and complete its fields. Connect Next; for a condition, also choose Otherwise. Leave an ending connection blank.
- 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.
- Validate the complete graph, save and use Test with a record. Review both condition outcomes where possible.
- Obtain independent approval and publish. Enrol a record manually or use the separately configured future-event trigger.
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.
Fields, 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.
Questions and answers
Does Queue marketing email bypass approval?
No. It requires a current published approved email and all normal delivery checks.
Can I put a loop back to an earlier step?
No. Workflow graphs must be acyclic.
Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.
Useful next steps
- Sales & Marketing Hub: complete CRM and campaign guide
- Build sales follow-up sequences and playbooks
- Edit and rehearse workflows on the visual journey canvas
Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.