Automation Builds
Part of Testing marketing automations before launch
Creating test contacts for different workflow branches
Build controlled contacts for each workflow branch, including overlaps, exclusions and missing values.
Create controlled contacts whose field values explain each expected branch decision. Cover every intended path, then add cases for overlapping rules, missing values and exclusions. Record the expected outcome before using a preview; otherwise a plausible path becomes its own pass criterion.
Turn branch rules into a case sheet
Read the configured conditions in order. For each branch, record the exact fields, accepted values and expected path. Add a record that matches none and one that meets more than one rule. An illustrative interest workflow might use this sheet:
| Contact | Interest value | Eligibility | Expected result |
|---|---|---|---|
| A | Product A | Eligible | Product A path |
| B | Product B | Eligible | Product B path |
| C | Blank | Eligible | Agreed neutral or review path |
| D | Product A | Excluded | No campaign action |
| E | Values matching two rules | Eligible | Agreed precedence outcome |
Use the real property type and values. A multi-select field can behave differently from a single-value field. In HubSpot, a “Value equals” branch based on a multi-checkbox property can send a record with several selected values to “None met” because it is not an exact match.
In HubSpot, branch logic can vary by branch type, so check the configured branch type before predicting the path.
An exclusion may prevent entry rather than form a branch. Record the entry decision separately from the branch decision. An empty “None met” path can let an entered contact finish without an intended review action.
Keep records identifiable and contained
Give each test contact an ID, purpose, owner and starting values in the case sheet. Use fictional details or staff-controlled addresses. Before creating records in a production account, check other active workflows and connected systems they might enter.
A test marker alone does not isolate them. Retire or restore fixtures under the account’s data rules after use.
If the workflow starts from an event, a stored property cannot reproduce the event. HubSpot’s event-enrolment test checks additional filters but cannot simulate the occurrence. Check the event-to-contact association separately when it affects entry.
Test values that change over time
For a delayed branch, record both the value at entry and the value when the record reaches the branch. Change one field during a controlled run and inspect the resulting path. Records must match the branch criteria before reaching the branch in the workflow, so confirm the values at that point.
Use a fresh fixture or reset history carefully for each critical case. An earlier enrolment, goal or suppression can affect whether the contact enters again. HubSpot’s criteria test can show a current match even when a completed contact will not re-enrol because re-enrolment is disabled.
Compare prediction with evidence
Record the entry-test result and the predicted path. HubSpot’s workflow test simulates how a specific record will go through a workflow after enrolment. Where a branch depends on the output of a previous action, mark that prediction as unconfirmed until a controlled run establishes the actual output and path.
