Single send API won't use BCC in sandbox

Developer Support APIs & Integrations
1

Hi,

I’m trying to 1) send an email using the single send api, and 2) have the content of that email recorded in the “Email” tab of the company.

I guess the only way to do this is to use the Hubspot BCC email address, but this results in this message: “Email not allowed to be sent to the specified recipient in a sandbox portal”. The sandbox only sends email to my company’s domain, and won’t send to @bcc.hubspot.com.

I can see where this would be by design, if not exactly an intended consequence. So I guess what I’m looking for is:

  1. Can I fix the issue with the BCC address?
  2. Is there some other way I can get the content of the email to show in the Email tab, while still using Hubspot tracking.

Thanks.

2

Hi @JCampbell6,

You’re correct, the sandbox environment in HubSpot has limitations.
Do this -
1. In HubSpot’s sandbox, you can’t send emails to external addresses like @bcc.hubspot.com. This is a built-in restriction.
2. Create test contacts using your company’s email domain. Send emails to these contacts so the emails are tracked and show up in the “Email” tab.
3. You can manually log the email content in HubSpot using the “Log Email” feature.
4. If you need to fully test the BCC feature, consider using your live environment.
This way, you can still test effectively within the sandbox’s limitations!

If you need more help, let’s talk!

Khushboo Pokhriyal

Growth & Operations

GroRapid Labs

LinkedIn | 9315044754 | Email | Website

3

Thanks for the reply! Okay, if I can’t do that, is there a way to specify the text/html of the email without using a template? What I’m trying to do seems pretty simple:

  1. Send an email.
  2. Add that email - with content - to the company email tab.

I can manage #2 with the engagements API, but in order to do that, I have to render the content of the email programatically. I’d kind of assumed this would be straightforward with the hubspot API, but it’s not looking like it’s possible.

The email doesn’t have to be a template. If I can’t get this to work, I’ll just use mailgun and the engagements API, I guess.

Thanks again.