Allow transactional emails to pull in dynamic content via API
For use on things such as cart abandonment emails / member statements / transaction details.
e.g. a user orders 3 items from your store. The following transactional email pulls in the item names, quantities, prices, order total, tax amount etc. Whatever fields are relevant to the transaction.
This data should not need to be stored directly inside autopilot (esp. as # of transactions within a certain type could be unlimited) and could also be frequently changing.
-
Philip commented
Yeah +1 on this. Similar to:
At minimum, we should be able to dynamically generate and send the raw HTML to an API endpoint that takes the contact id, journey id, and Autopilot wrap / track the links like traditional transactional email services like Mandrill, Sendgrid, etc.
Today, there is no way to send any meaningful dynamic emails which is honestly something I just assumed that was offered as that's kind of table stakes.
- Newsletters
- Daily/Weekly Digests
- Receipts
- Cart abandonments
- List goes onIterable offers a feature where you surface an api endpoint on your server that spits out json which they use to parse and populate the emails which is really nice as it's up to date whenever the person opens it, but I'd settle for being able to send json / html / handlebar variables with the payload.
Will likely have to switch providers soon due to this fact, which makes me sad because I really like other aspects of the product ; (
-
Casey Schorr commented
+1, trying to implement autopilot and our engineering team is very frustrated with the "flat" data structure in autopilot. Need to be able to loop through an array of items and insert them into the email. The use-case is very similar to notifying on shopping cart abandonment.