Automation Builds
Part of Marketing workflow version control
Recording changes to trigger conditions
Document the old and new entry rules, timing, repeat behaviour and expected audience difference for a workflow trigger edit.
Record a trigger change as a before-and-after rule, not “updated audience”. State what starts evaluation, which records qualify, when conditions are checked and what should happen to records already eligible or enrolled. It helps an operator explain a changed entry population later.
Capture the rule being replaced
Before editing, record the workflow ID and current revision. Write the existing trigger in plain language: event, filter or schedule; record type; operators and values; AND or OR relationships; exclusions; and any re-entry rule.
Write the proposed rule in the same format and mark each difference.
“Interest equals Product A” and “interest is known” are different conditions. Changing AND to OR can admit records that previously needed both conditions. These are illustrative differences, not rules for a particular campaign.
| Change-log field | Question it answers |
|---|---|
| Old and new expression | Which criterion changed? |
| Evaluation time | Is it checked at the event, a later branch or a scheduled run? |
| Existing records | Could previously eligible records enter after the edit? |
| Repeat rule | Can a completed record enter again? |
| Expected difference | Which records should newly enter or stay out? |
| Approval and effective time | Who accepted the edit, and when should it apply? |
Before-and-After Workflow Trigger Changes
- Old and new expressionChange from 'Interest equals Product A AND interest is known' to 'Interest equals Product A OR interest is known'
- Evaluation timeEvent-triggered at contact interaction; no re-evaluation after event
- Existing recordsRecords that met the old rule before change remain enrolled; no automatic re-entry
- Repeat ruleDefault: one-time enrolment unless re-enrolment is explicitly enabled
- Expected differenceNew records qualifying under OR logic may enter; some previously excluded records now eligible
Record the timing and cutover
HubSpot offers event, filter and scheduled enrolment. For an event trigger with additional filters, the record must meet those filters when the event occurs; changing a property later does not re-run that earlier event.
HubSpot enrols a record only the first time it meets a trigger by default unless re-enrolment is configured. These are HubSpot rules, not assumptions to carry into another platform.
Record the cutover time and intended treatment of contacts who qualified before it. Distinguish records already enrolled from records that have not entered.
Before changing an existing HubSpot workflow's trigger type, capture the old rule, then inspect the complete new entry configuration.
Make the difference checkable
Prepare a decision table with a record matching only the old rule, one matching only the new rule, one matching both, an excluded record and a repeated occurrence if repeats matter. State the expected entry decision for each. Record a later branch decision separately.
HubSpot revision history can be filtered for changed enrolment triggers and shows the associated time and user. Its workflow test previews a route without executing actions. Use those views to compare the configured revision with the written rule; check actual enrolment or sending as separate observations.
Close the log with the production revision, first observed entry review and any discrepancy. Preserve the original release note and append a correction under a new version if the observed population differs from the approved rule.
