SPOTTER | Your Hubspot Helper
📢 Announcement
Meetings Index Page & Custom Properties
If you have ever tried making meeting reports, or build better lists and workflows using the contact <> Meeting (or deal <> meeting) association, this update is for you.
A few weeks ago, we saw a beta introducing meeting workflows. Soon, we will see meetings become more of a real object with their own index and custom properties. Personally, I cannot wait.
✅ Tip
Quick fix for a common HubSpot headache.
Rollup Properties for Non-Standard Objects
What can I say about rollup properties that wouldn’t apply to a well designed multi-tool? Useful, versatile, and yet not always the perfect thing to use for a given job.
Recently, HubSpot has expanded the rollups to include more objects, even pseudo objects. This makes them a lot more powerful. Your source objects are now open to:
Company
Call
Campaign
Cart
Contact
Invoice
Deal
Meeting(in beta)
Order
Payment
Quote
Subscription
Survey Response
Ticket
Custom Objects
So go out there and replace your workflows with rollups!
⚠️ Trap
Mistake to avoid before it causes chaos.
Review Your Email Addresses for Job Hoppers
If you’re using HubSpot, there’s a pretty good chance you are B2B or you use professional email addresses.
People like professional emails because they are harder to make, and usually have a lower chance of being spam. And many people take the email that comes to their professional address more seriously.
The problem? People switch jobs. Then you’re emailing a dead inbox. And that person you built a relationship with? They forget you exist. Unless they have the conscientiousness to actually let you know they left their old job (no one does this).
So if you have an enrichment tool, you should be able to follow people across job changes via their Linkedin URL (It doesn’t change).
For certain situations, i like to make an “inactive” list to demonstrate that some of the people in the CRM have likely moved on from their old job.
🔄 Try
Something small to test or improve this week.
Use the “Go to Workflow” Action to Make Processes More Explicit
Before the “Go To” action, I would use properties in a very brittle way. I would say “Here this one property will only be changed by this workflow, and it changing will trigger the second workflow”.
For many intents and purposes, this approach works. But you end up with properties you don’t need, or someone will use the property you set aside for the workflows and break the system.
The “Go to workflow” action is a much simpler way to build process with clearly interconnected automations. It helps keep each workflow’s scope manageable.
👋 Need a Spot?
Want help cleaning up your HubSpot portal or setting up something smarter?
Let’s talk about what hands-on help could look like for your team.
