I’ve started to use your postmark template plugin. I need to use Postmark for both broadcast and transaction email.
Is that possible with your plugin?
If so, how do I define which is which in the workflows?
Thx,
Guy
If you are referring to this (Postmark) plugin, you can send both, broadcast and transactional.
Broadcast is emails that are sent to a larger groups ideally, whereas transactional is more on individual basis.
For broadcast group sending through Bubble I suggest to check out more about Recursive Scheduled Workflows (in the backend), especially if you are sending to a group more than, let’s say 200 (member) emails.
1 Like
I was not refering to this plugin, but this one: Postmark Template Plugin | Bubble
Right. I know about recursive workflows. I have a few set up with sendgrid.
I was wondering how to direct the plugin to a postmark broadcast stream.
I did find that parameter, eventually, in the plugin editor.
Thanks for your answer.
Guy
Hi @gyangting,
I made that plug-in to help me make dealing with transactional email easier and not have to fiddle around with json. I hadn’t really considered bulk email till you mentioned it. 
It is probably quite straightforward to add it to the plug-in. I’ll have a look and update the plug-in in the next day or so.
1 Like
Looking forward to it!
This would be great! It’s the only thing holding me back from buying the plugin, honestly. The other Postmark plugin works fine, but I’m having to write most of the HTML by hand (which I hate) to make the emails look acceptable per our branding, and being able to send broadcast emails with templates would be HUGE for us. I’d gladly give your plugin a try if it had broadcast support.
1 Like
Thanks for the encouraging prod @samnichols 
I’ll ping you when it’s done.
1 Like
Do it! 
1 Like
Done it @samnichols @gyangting Deals with Batch email. It’s very similar to the Transaction email action, except the Batch action takes lists, not single values. So you can send up to 500 customised emails. Very quick to add additional fields if you let me know what you need. Built into the plugin are all the standard Postmark custom fields.
https://postmark-template.bubbleapps.io/version-test - has a video explaining how to use it also.
2 Likes
Cool! I’ll try it out. Question: the other free plugin has an issue when used in backend workflows. When postmark sends an error because of a hard bounce, the recursive workflow stops and does not send other emails
The error is silent and there’s no error handling for backend workflows…
1 Like
No need for any recursive workflow other than batching up requests to Postmark of up to 500 emails. The Postmark API takes all the emails request (up to 500) and deals with them.
I was able to update it! Had to refresh the plugin page to see the update option.
Hi @lindsay_knowcode, I’m not sure how to use batch email with your plugin:
- I tried to find a new plugin in the bubble plugins, but there’s only your transactional email plugin available.
- I looked for an update of your existing plugin to check if the new feature would be in it. But there’s no update.
- I went to your page, watch your video, but did not understand how to install the plugin.
Can you help?
Thx
Another issue: I can’t use the batch action in backend workflows.
This videos shows the issue: Loom | Free Screen & Video Recording Software
@gyangting The reason you can’t add single values (like a text like “cc@mail.com”) is that the Batch action in my plugin takes Lists. (Bubble Lists - like the results from a Bubble search). So the Bubble editor will only let you input List type things into the parameter fields.
The reason for this is that with a batch of emails, you can have different values for every email in the batch. eg the first email is to
john1@mail.com and the customised name is “John”
the second email is to
jane2@mail.com and the customised name is “Jane”
If you want to send an email with the same parameter values (ie the same email content) to up to 50 recipients - use the Transactional email action and use a comma separated value of the recipients eg john1@mail.com, jane2@mail.com
Here is an example of how you could do that.
I’ll check it out! I actually realized for our use-case, batch wasn’t 100% necessary (since there’s a 500 email limit), but I created a frontend admin page for us to craft email content to specific user groups when there are changes to the platform that affect them. It was going to be a lot easier to do this with Bubble than trying to figure out how to appropriately tag the right people in an email marketing service like SendGrid.
We’re sending each email 5s apart and using the doHTML (doHTML Plugin | Bubble) plugin to change the admin email content input so it’s email-friendly and retains line breaks, links, etc. Combining that with Postmark templates will be awesome to get the branding right. Thank you!
I understand that and it’s relevant for the variable examples you gave.
But for Template ID, Template Alias, Message Stream, Track-opens, Track-links, etc.
It makes things more complicated by having to create a specific data type and data things and then do a search to retrieve a single item.
In my opinion, entering these as single items rather than lists would make the plugin much more usable.
I agree actually @gyangting . I thought that defaulting to the first item in the list would be the “easy” way to deal with this - ie just supply a list with 1 entry - but there is no simple way to convert a single Text type to a List type when you are entering parameters. (that I could find)
So for those variables that are probably going to be identical - I’ll convert them to a single (non List type) type. I can’t imagine for a batch use case that those types of parameters would be different per email.
I’ll probably do this in the next few days.
Cool. Looking forward to it.
1 Like
Done @gyangting So now there are two Batch Template actions.
-
Send a batch with the parameters you’d expect to be the same in a batch (eg Template) taking those as single values. Saves the pain of clunky conversions of single values to list types.
-
Send a batch - if within the batch you had different templates, message streams per email etc - these can be custom per email as they are lists. Maybe someone will have this use case.
So far, so good!
I still have to test using metadata for statistics follow up per customer.
Otherwise seems to work like a charm.
1 Like