Single Send API - Access non-contact properties (deal or custom objects)

[antonjarl]

We are using the Single Send API to send transactional e-mail to customers. We personalize these the contact.firstname and also send in custom properties as payload in the API that we use using custom.customProperty.

Now we are expanding our product portfolio, and I want to customize these email further, by for example exposing the product name or switching out an image depending on which product the customer is interested in.

Can you confirm whether or not I should be able to access deal properties or properties from custom object when sending e-mail using the Single Send API?

I would love to avoid having to set up custom components for the API e-mails, and having to put too much logic and control on the API and instead keep the e-mail smart and dynamic.

Could anyone help?

[MuhammadAmjad]

I totally understand your challenge with expanding your transactional email capabilities. The Single Send API is primarily designed around contact properties and custom payload properties, so unfortunately it doesn't support direct access to deal or custom object properties in email personalization tokens.

However, here are some practical workarounds you could consider:

1. Sync key deal data to contact properties: Before triggering the email, you could use a workflow or custom integration to copy the most important deal properties you need for example product name to custom contact properties. This keeps your email templates dynamic without complex logic.

2. Use the custom payload approach more strategically: Instead of viewing it as too much logic, you could structure your API calls to pull the relevant deal or custom object data first, then pass those specific values through the custom properties in your Single Send API call. This way the email stays smart and you control the data flow in your application logic.

3. Consider HubSpot workflows for these scenarios: If your use case allows, you might trigger workflow-based emails that can natively access associated deal properties through personalization tokens. This wouldn't use the Single Send API but could handle your product-specific customization needs.

The reality is that the Single Send API's design focuses on contact-centric transactional emails, so for deal-heavy personalization, option 1 or 2 tends to work best while keeping things maintainable.

If you'd like to discuss this more in detail, feel free to DM me directly.

[Jaycee_Lewis]

Hey, @antonjarl 👋 The documentation mentions Contact and Custom Properties. Here's the specific link. And we'll keep this open in case other community members have other suggestions. — Jaycee