Yes, you can pull in HubSpot standard object data in automated emails. This feature lets you add contact, company, deal, and ticket info right into your email workflows. You use personalization tokens to make this happen.
This is a game changer for your marketing. Your emails can now feel like they were written just for one person. You can include deal stages, company names, or ticket statuses automatically.
I use this all the time for my own campaigns. It makes a huge difference in how people respond. The emails don’t feel like mass messages anymore.
What Does It Mean to Pull in a HubSpot Standard Object?
Let’s break this down in simple terms. A standard object is a core item in HubSpot.
Think of contacts, companies, deals, and tickets. These are the main things you track. When you pull in a HubSpot standard object, you are taking data from these items and putting it into an email.
The system does this for you automatically. You set up a token, and it fills in the info for each person. This is how you can pull in HubSpot standard object details without manual work.
For example, you can show a contact’s first name or a deal’s amount. You can even show a company’s industry. The goal is to make the email relevant.
This is a core part of making your CRM work for you. It connects your database with your communication.
Why You Would Want to Pull in HubSpot Standard Object Data
Personalization is the biggest reason. People ignore generic emails. They pay attention to messages that feel personal.
When you pull in HubSpot standard object properties, you reference things the recipient cares about. You can mention their company name or a recent deal they are working on. This shows you know them.
It also saves you a ton of time. You don’t have to write separate emails for each person. You create one workflow that feels personal to hundreds of contacts.
It helps with guiding people through a process. You can send an email based on a deal’s stage. Or you can update a contact when a ticket is solved.
The ability to pull in HubSpot standard object information makes your marketing smarter. It uses the data you already have to build better relationships.
Which Standard Objects Can You Pull Into Automated Emails?
You can use several main objects. The Contact object is the most common one. You can pull in a contact’s name, email, phone number, and any custom properties you have made.
The Company object is also very useful. You can pull in the company name, industry, or number of employees. This is great for B2B marketing.
The Deal object lets you bring in sales data. You can show the deal name, amount, or stage. This is perfect for automated emails to your sales team or to the contact associated with the deal.
The Ticket object is for customer support. You can pull in the ticket subject, status, or priority. This helps keep customers in the loop.
You can even pull in HubSpot standard object data from associated objects. For a contact, you can pull data from their associated company. This gives you even more context to work with.
How to Actually Pull in a HubSpot Standard Object Using Personalization Tokens
The magic happens with personalization tokens. These are little bits of code that HubSpot replaces with real data.
To use one, you just click the insert token button in the email editor. A menu will pop up showing you all the available objects and their properties.
When you select a property, the token is added to your email. It will look something like `{{ contact.firstname }}` or `{{ deal.amount }}`. When the email sends, it shows the actual first name or deal amount.
It is vital that the workflow is set up correctly. The email must be sent from a workflow that is based on the right object. If you want to use deal tokens, your workflow should be triggered by a deal.
This is the practical way you pull in HubSpot standard object info. You are not coding. You are just selecting from a list.
According to the HubSpot official website, their documentation provides a full list of these tokens. It’s a great resource for seeing all your options.
Setting Up a Workflow to Pull in HubSpot Standard Object Properties
First, you go to the Workflows section in your HubSpot portal. You click to create a new workflow and you must choose the enrollment trigger.
This trigger is key. It decides which object your workflow is based on. To pull in HubSpot standard object data for a Deal, you set the workflow to trigger based on Deal properties.
Next, you add the “Send email” action to your workflow. You then design that email and insert your personalization tokens. The system will only show you tokens for the object your workflow is using.
You should always test your workflow. Enroll a test record and see if the email populates correctly. This confirms you can successfully pull in HubSpot standard object information.
Remember to set up your suppression rules too. You don’t want to spam people. You only want to send relevant emails.
Common Use Cases and Examples for Pulling in Object Data
A common use is a welcome email for new contacts. You can pull in their first name and company name to make it friendly. This is a simple way to pull in HubSpot standard object data from the start.
For sales, you can set up a deal-based email. When a deal moves to a new stage, an email can go out. This email can pull in the deal name and amount to keep everyone informed.
Support teams can automate ticket updates. An email can be sent when a ticket is closed. It can pull in the ticket subject and thank the customer for their patience.
You can also create re-engagement campaigns. For contacts who haven’t been active, you can pull in the date they became a customer or their last activity. This adds context to your “we miss you” message.
The goal is always to make the message more relevant. Every time you pull in HubSpot standard object data, you increase the chance of engagement.
A study by the Marketing Profs community shows that personalized emails generate significantly higher transaction rates. Using object data is a direct path to that personalization.
Limitations and Things to Watch Out For
The main limit is data availability. You can only pull in HubSpot standard object data that actually exists in your CRM. If a property is empty for a contact, the token will also be empty in the email.
You also need to be aware of associations. To pull in company data for a contact, that contact must be associated with a company in HubSpot. If the association is missing, the data won’t flow.
There is a limit on how much data you can pull in from associated objects in a single go. You can’t create endlessly nested tokens pulling from objects associated with objects associated with other objects.
Always have a fallback for empty properties. HubSpot lets you set a default value for a token. So if a company name is blank, you can set it to show “Valued Customer” instead.
Be careful with your formatting. A number property for a deal amount might not include a dollar sign. You may need to add that in the text around the token.
Troubleshooting: When You Can’t Pull in HubSpot Standard Object Data
If your token is not working, check the workflow trigger first. Is the workflow based on the correct object? You can’t use a deal token in a contact-based workflow.
Check if the property has a value for the test record you are using. If the property is blank, the token will show nothing. You need data for the token to display.
Verify the property exists and is active. Sometimes, a property might be deleted or hidden. This will break the token.
Make sure you are using the correct token syntax. While the editor usually handles this, copying and pasting can sometimes introduce errors. It’s best to always use the insert menu.
If you are trying to pull in HubSpot standard object data from an associated object, double-check the association. The contact must be linked to a company, for example, for company data to appear.
Resources like the HubSpot Knowledge Base are excellent for solving these common issues. Don’t hesitate to use them.
Best Practices for Using Object Data in Your Emails
Don’t overdo it. Using too many tokens can make an email look strange and robotic. Use data sparingly to keep the email sounding natural.
Always provide context for the data you show. Don’t just say “Your deal {{ deal.name }} is active.” Instead, say “We see your deal, ‘{{ deal.name }}’, is making great progress.”
Keep your CRM clean. The quality of your personalized emails depends entirely on the quality of your data. Make it a habit to update and standardize your property values.
Segment your audiences. The power to pull in HubSpot standard object data is even greater when you send the right message to the right group. Use lists and smart criteria to define your segments.
Test different data points. See which pieces of information resonate most with your audience. Does mentioning a company’s industry work better than mentioning its size? Run A/B tests to find out.
As noted by the Neil Patel blog, testing and optimization are key parts of any successful marketing automation strategy. Your use of object data should be no different.
Frequently Asked Questions
Can you pull in HubSpot standard object data for custom objects?
Yes, you can. The process is very similar. If you have created a custom object in HubSpot, you can use personalization tokens for its properties in workflows based on that object.
Can you pull in HubSpot standard object information into a marketing email?
Yes, but there is a key difference. In a one-off marketing email (not a workflow email), you can mainly use contact and company properties. Deal and ticket tokens usually won’t work because the email isn’t tied to a specific deal or ticket record.
What happens if the data for a token is missing?
The token will appear blank in the sent email. This is why it’s a good practice to use default values for important tokens, so the email doesn’t have awkward empty spaces.
Is there a limit to how many tokens I can use in one email?
There is no hard limit on the number of tokens. However, for performance and readability, it’s best to use them thoughtfully. An email crammed with tokens can feel impersonal and may have delivery issues.
Can I use these tokens in the subject line of an automated email?
Absolutely. Using a token in the subject line, like a contact’s first name, is a great way to increase open rates. The process for adding the token is the same as in the email body.
Can you pull in HubSpot standard object data into a notification email for your team?
Yes, this is a very powerful use case. You can set up internal notifications that pull in deal, ticket, or contact details. This keeps your team updated with rich context automatically.
Conclusion
So, can you pull in HubSpot standard object in automated email? The answer is a clear and powerful yes. This functionality sits at the heart of what makes HubSpot’s automation so effective.
It transforms static, bulk messaging into dynamic, one-to-one communication. By leveraging the data you already store, you can create emails that are timely, relevant, and personal.
Start simple. Add a first name token to your next workflow email. Then, as you get comfortable, explore pulling in company details, deal stages, or ticket priorities. The more you use this feature, the more you will see its value in driving engagement and building stronger customer relationships.
