Outcome. Contacts who receive a marketing email with no campaign tag on record get flagged and escalated right after the send, so ungoverned, un-attributable sends get caught and fixed at the process level instead of quietly repeating.
Workflow map
Enrollment, branches and actions at a glance
marketing-ops-011
flowchart TD
A[Contact sent a marketing email] --> B{last_campaign_tag blank?}
B -->|Yes| C[Add to Ungoverned sends list]
C --> D[Notify marketing ops]
D --> E[Create review task]
B -->|No| F[No action, properly tagged]
When to use it, when not to
- UseUse once you have decided every marketing send should be tied to a Campaign for attribution reporting, and you need a way to catch the sends that were not.
- UseRead this fiche's limit carefully before building: HubSpot has no native action that blocks a marketing email from sending because a Campaign field is missing. This workflow is a detect-and-escalate control that runs after the send, not a hard stop before it.
- UseUse it alongside a manual pre-send checklist item ("campaign tagged: yes/no") if you need something closer to true enforcement. Automation alone cannot fully replace that checklist here.
- SkipDo not build this if your team already reliably tags every send with a Campaign at compose time and reviews it. The audit trail this workflow adds is only worth the setup if untagged sends are a real, recurring problem.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.4 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.5 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the marketing ops pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
