Hello, looking for some ideas on how I can create a workflow that generates a ticket when a marketing email from a specfic email address is sent to a contact. Hubspot removed the filter for from address and the filters for marketin emails are too limited. List wonât work either from what I can tell.
Any idea on why Hubspot made this change, and ideas for a workaround?
Hey @JRichard9 - thanks for posting in the Community!
Iâd like to tag in some Community experts to see what insight they may have on a possible workflow solution for your setup! @danmoyle, @Bryantworks, and @Kevin-C - any thoughts on a possible solution here?
Shane, Senior Community Moderator
Hi @JRichard9,
HubSpot rarely provides explanations when small changes like these are made in the platform, unfortunately.
As far as workarounds go, I would probably fall back on the contact property âLast marketing email nameâ and filter by keywords contained in the name of the email. If youâre following a solid naming convention, this is probably the best option.
Best regards
Hi @JRichard9, youâre running into a real limitation of how HubSpot models marketing email events now.
Karstenâs suggestion is honestly the most practical native workaround today.
The âLast marketing email nameâ contact property is one of the few consistently updated fields you can reliably trigger off, and if your team follows a strict naming convention, filtering by keywords is workable, even if it feels a bit hacky (Organize marketing emails with custom email properties )
A couple of other angles Iâve seen teams use, depending on how strict the requirement is:
If the email is sent via a specific campaign, you can trigger off campaign membership instead of the email itself. This works well if the âfrom addressâ correlates to a campaign or brand stream. Itâs not perfect, but itâs more stable than email-level filters.
If the email is always sent from a specific subscription type, you can sometimes infer intent by combining âLast marketing email nameâ with âMarketing email subscription statusâ logic. This narrows false positives when multiple emails share similar naming.
Why HubSpot removed the âfrom addressâ filter is mostly architectural. Marketing emails are increasingly abstracted behind event objects and privacy controls, and the platform has been slowly removing filters that rely on message-level metadata that isnât guaranteed to be consistent across sends. Unfortunately, that usually happens without much explanation.
If this needs to be bulletproof, the only fully deterministic option is a custom code workflow listening to marketing email events via the API and then creating the ticket when the sender matches, but thatâs a heavier lift and usually overkill unless this is mission-critical.
If you want, whatâs the real driver for the ticket? Is it compliance, support follow-up, or internal alerting? Sometimes reframing the trigger makes the workflow simpler.