I'm looking for an API endpoints to achive a rather straight forward flow:
- create a ticket (got that)
- associate ticket with deal, company, contact (got that)
- create an email (can be done with engagement endpoint, but not sure about this)
- associate email with ticket (got that)
- send that email (looking for that one especially!)
obvisouly, for those emails, if the recipient answers, I'd like to have the answer auto filled into the converstion & ticket again. I guess if I send the email via an external SMTP gateway, which would be straight forward, that doesn't work, as it lacks some email header magic to get the association right?
thanks for the feedback! As fas as I can see, the single send api will associate with the contact, the smtp api will not. But both won't associate with a ticket.
However I've now done a few experiemnts using BCC, looks like the following works as well and doesn't require the (pricy!) transactional email extension:
- create a ticket (got that)
- associate ticket with deal, company, contact (got that)
- create an email externally, send via our usual Google SMTP, BCC to hubspot
- fiddle with hubspot api to find email (to bad I can't serach for message-ID!) and then associate email with ticket
So it basically just works the other way round, but that sounds reasonable.
thanks for the feedback! As fas as I can see, the single send api will associate with the contact, the smtp api will not. But both won't associate with a ticket.
However I've now done a few experiemnts using BCC, looks like the following works as well and doesn't require the (pricy!) transactional email extension:
- create a ticket (got that)
- associate ticket with deal, company, contact (got that)
- create an email externally, send via our usual Google SMTP, BCC to hubspot
- fiddle with hubspot api to find email (to bad I can't serach for message-ID!) and then associate email with ticket
So it basically just works the other way round, but that sounds reasonable.
The key difference between the two is that using the Single Send API allows you to create/build emails from within HubSpot, save them for use with the Single Send API, and then programmatically trigger the send.
You can also pass through data to inject into the body of the email. This data can live inside (and outside) of HubSpot.
The SMTP API on the other hand is used if you want to create/manage email outside of HubSpot and simply send via our SMTP server.
All emails sent via either API would show as emails on the contacts record. It would look similar to the below:
Hi, I was looking into a way to create an email sent via API, and just happened to have found this. Would it be possible that the email sent using Single Send API, to appear as an associated conversation to an object (i.e tickets)?