# How do HubSpot Marketing Hub teams build workflow logic the standard filters don't cover?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">A question I keep coming back to is what <a class="a a--md" elv="true" href="https://www.g2.com/products/hubspot-marketing-hub/reviews">HubSpot Marketing Hub</a> teams do when the workflow logic they need goes beyond the standard filters. The visual builder handles if/then branches that route contacts down different email paths without code, and when a case falls outside the filter options, the workaround that comes up on G2 is a contact property used as a flag: one workflow sets it, and other workflows filter on it. That covers cases like stopping someone from answering the same survey twice.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Across <a class="a a--md" elv="true" href="https://www.g2.com/categories/marketing-automation">marketing automation</a> setups, the situations seem to split three ways:</p><ol>
<li>A single campaign with clear branches. The standard filters cover it, and the builder is quick to work in.</li>
<li>Logic that depends on something that happened earlier, like a survey answer. A property flag carries that state between workflows.</li>
<li>Several people building on the same account. Controlling who can build or change which workflows becomes the setup question, along with keeping duplicate contacts and companies out of enrolment.</li>
</ol><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Builders tend to lean either towards visual simplicity or towards open-ended scripting, and HubSpot sits on the visual side, which suits teams where marketers rather than developers own the workflows. The flag pattern is how those teams extend it without leaving that model.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For anyone running property flags, how do you keep track of what each one means? And who on your team owns that naming?</p>

##### Post Metadata
- Posted at: 1 day ago
- Author title: Marketing Executive
- Net upvotes: 1


## Comments
### Comment 1

We keep a simple doc listing every flag property and which workflow sets it, and one person owns the naming. Handovers got so much easier after that.

##### Comment Metadata
- Posted at: about 7 hours ago
- Author title: Marketing Executive





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4