ThaiBulkMail
EmailThaiBulkMail is the email product of Thai provider ThaiBulkSMS. Agents send templated email, deliver one-time passwords by email, manage attachments, and check remaining credit.
What This Integration Enables
ThaiBulkMail is the email product of a Thai provider, and its most consequential design choice is one it does not advertise: there is no route that accepts a message body. Every send names a template identifier that someone published in the vendor's own interface, and supplies merge values to fill it. That is a constraint, and it is also a governance property most email APIs cannot offer. The set of things this connector can say to a customer is exactly the set someone already approved, which moves content review upstream of the automation rather than leaving it to whatever assembled the payload.
FlowRunner agents work inside that boundary. They fill templates with merge values, attach documents from a rolling upload window, read the credit balance before committing to a run, and handle the vendor's refusals as work rather than as noise, because an unsubscribed recipient and a content filter rejection both come back as explicit errors rather than as silent skips. The same host also carries one time passwords by email, with a verification token that appears in one response and nowhere else. Two of those facts, the credit that runs out partway through a run and the template the agent cannot read, are why FlowRunner's human-in-the-loop design has a specific job on this connector.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Order and appointment notifications that never improvise
A shipment confirmation in Shopify or a status change in the operations sheet reaches the agent. It resolves the customer's language and the matching published template, builds the merge values with every field expressed as text, and calls Send Email. The response reports credit used and credit remaining, which the agent records against the run rather than discarding. If the recipient has unsubscribed, the vendor refuses the send explicitly instead of dropping it, so the agent can write that refusal back to the customer record in HubSpot as a consent fact rather than as a delivery failure.
-
Documents attached inside a window that closes
An invoice or a delivery note is generated upstream. The agent calls Upload Attachment with the file contents and receives an identifier it can reference on a send, subject to the vendor's limits on file count, size, and accepted types. Because uploads live for seven days and then disappear along with their identifiers, the agent never caches one across runs. It uploads per run, confirms with Get Attachment that an identifier is still live before referencing it, and uses Get Attachments to see what the rolling window currently holds. When a document carrying customer data has served its purpose, Delete Attachment removes it early rather than waiting for the window to close.
-
A one time password with a person at the end of the ladder
A login or a high value change needs verification. The agent calls Send OTP, keeps the token from the response because it is the only value that will verify the code, and shows the recipient the reference number that arrives beside their code. Verify OTP checks the entered code against that token. When verification fails repeatedly, the agent does not keep sending codes. It opens a ticket in Zendesk with the reference number and the attempt history attached, so a support agent picks up a customer who is already stuck rather than a customer who has been retried into a lockout.
Human-in-Loop Highlight
A large run on this connector carries two risks the API cannot resolve on its own. The connector has no operation that lists or reads templates, because the template identifier is copied by hand from the vendor's interface, so an agent about to mail thousands of customers cannot see the words it is about to send. And running out of credit is reported partway through a run rather than up front, which leaves a split audience whose boundary exists only in the credit remaining value on each accepted response. So above an agreed run size, the agent stops before the first real recipient. It sends one message to the reviewer's own address with the real merge values, posts the result alongside Get Credit's balance and the recipient count, and asks: "This run is 4,200 recipients against a balance that covers roughly 3,800. Here is the rendered message for row one. Proceed and stop at the shortfall, split it across two days, or top up first?" That is a resource and content decision, made once, with the evidence in front of it. Everything after the answer is the agent's work.
Agent Capabilities
8 actionsSending
2- Send Email Sends a templated message to one recipient, filling the template's merge tags with the values supplied. Attachments are given either as a public URL or as the identifier of a file uploaded through this connector, and the response reports the credit used and the credit remaining.
- Get Credit Reads how much email credit the account has left. Worth calling before any sizable run, because exhaustion is otherwise reported partway through rather than up front.
Attachments
4- Upload Attachment Uploads one file and returns the identifier a send references. Uploads live for seven days, so workflows treat the identifier as short lived rather than storing it.
- Get Attachments Lists the files currently available for use as attachments, a page at a time. A rolling seven day window rather than a history.
- Get Attachment Reads one uploaded file's name and size by its identifier. The confirmation step that an identifier is still live before a send references it.
- Delete Attachment Permanently removes an uploaded file. Its identifier stops working immediately, so anything still referencing it fails from the next send onward.
One-Time Passwords
2- Send OTP Sends a one time password by email using an OTP template, and returns the token that verification depends on, the reference number shown to the recipient, and the message identifier. A workflow that keeps only the reference number cannot complete the verification.
- Verify OTP Checks a submitted code against the token returned when the password was sent. It takes the token rather than the reference number the recipient sees.
Frequently Asked Questions
What can FlowRunner do with ThaiBulkMail?
FlowRunner agents can run Send Email, Get Credit, and Upload Attachment in ThaiBulkMail, plus 5 more actions.
Does connecting ThaiBulkMail to FlowRunner require OAuth?
No. ThaiBulkMail connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can ThaiBulkMail trigger a FlowRunner workflow automatically?
ThaiBulkMail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email integrations
Start building with ThaiBulkMail
Free plan, no card required. Connect in minutes.