Workflows that can be triggered off marketing events.
For example:
Trigger: Marekting Event ‘Start Date’ is Tomorrow
Send Email to (choice) All contacts, Registered, attended, cancelled
Availblilty to branch off contacts status on events set delays based on dates of the event and then use items in marketing email (or sales templates) personalization tokens eg.
Hi {{contact.first_name}},
It was great to see you at {{marketing_event.event_name}}.
Yadda yadda yadda,
From,
{{contact.onwner.first_name}}
In addition, using marketing events like another object in workflows. E.g using as a data source to popoluate properties, use in branches
This is a great idea as leveraging workflows actions are (I believe) HubSpot’s most powerful feature. As this idea is submitted, I can share how our app event•hapily does this with it’s Registrant object.
The Registrant object is one of the custom objects installed with the app, and has many powerful uses. It represents and instance of a Contact registering for an event. For your particular use case you can send confirmation emails to Registrants from a single template, but leverage the properties on the Registrant AND its associated Event object.
As seen below, all of the variables are Registrant based properties like event name and qr code, along with calendar links (automatically generated!) from our Event object.
You don’t have to update the confirmation since it’s completely dynamic. HubSpot’s flexibility ftw!
Still not native HubSpot functionality, but with Mobly you can do all of that. Plus they associate everything back to the marketing event and an event segment. Lifesaver if you’re doing a bunch of in-person events.
Upvoted. Quick disclosure, same as the hapily reply above: I build an events app for HubSpot (EventEngine).
Here’s what works today, app or no app. When someone registers, copy the event details onto the contact. A workflow writes properties like Event Start Date, Event Location and Days Until Event. Then your emails just use normal contact tokens. One template covers every event.
Branching works the same way. We use one contact property called Email Communication Status, and one workflow that switches on it: confirmation, reminder, attended, missed, cancelled. Whatever sets that status picks the email.
It’s still a workaround. The data is already sitting on the marketing event record. Workflows just can’t read it. Native triggers and {{marketing_event.event_name}} tokens would kill this whole copying step, and I’d happily delete that part of our own setup.
