FlowRunner
PricingContact
Theme
Start Free

Zoho ZeptoMail

Email

Send transactional email through Zoho ZeptoMail from a verified sending domain. Agents deliver single HTML or plain-text messages, send template emails with merge data, and dispatch batch template sends with per-recipient personalization.

3 actions API key available
A new order lands from the storefront
The agent assembles the merge data: customer name, order lines, totals, delivery estimate
The merge fields are validated against the template's placeholders so no customer sees a blank {{name}}
Send Template Email delivers the order confirmation from the verified sending domain
The returned request_id and client reference log to the audit sheet for delivery correlation
Failures post to the operations channel with the recipient and error attached
When a batch send targets more than the usual daily volume, an operator reviews the recipient list before Send Batch Template Email dispatches it

What This Integration Enables

Transactional email is the mail people actually open: receipts, resets, confirmations, shipping updates. ZeptoMail exists to keep that traffic on dedicated infrastructure with a verified sending domain, separate from marketing blasts, and this connector makes it the sending arm of any FlowRunner workflow. Agents deliver single HTML or plain-text messages, fill ZeptoMail templates with merge data, and dispatch batch template sends where each recipient gets their own personalized copy in one request. - Send transactional messages from a domain verified in the ZeptoMail account - Fill template placeholders with workflow data via merge-info objects - Batch a template to many recipients with per-recipient personalization - Track opens and clicks where the message type warrants it - Correlate sends with your own records via the client reference echoed in responses Because everything this connector does reaches a customer's inbox under your domain's reputation, the batch path runs behind FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) checks whenever volume or audience departs from the pattern.

Without FlowRunner

Transactional email is buried in app code Changing a receipt template means a developer, a deploy, and a wait
Batch personalization is a mail-merge ritual Someone exports recipients, runs a merge, and hopes the columns lined up
Sends are unaccounted for Nobody can answer "did customer X get their confirmation" without grepping logs

With FlowRunner

Workflows own the sending Order events, signups, and status changes trigger template sends with merge data, no deploy involved
One batch call, per-recipient personalization Send Batch Template Email carries individual merge-info per recipient in a single request
Every send leaves a reference Request IDs and client references log automatically, so delivery questions have answers

Use Case Scenarios

Order confirmations that write their own audit trail

A [Shopify](/integrations/shopify) order triggers the agent, which maps the customer name and order details into merge info and calls Send Template Email. The response's request_id and the order number as client reference append to [Google Sheets](/integrations/google-sheets). When support asks whether order 4821's confirmation went out, the answer is a row, not an investigation.

Welcome sequences from real account events

When [Stripe](/integrations/stripe) creates a customer, the agent sends the welcome message through Send Email with open and click tracking enabled, from the verified domain rather than a founder's personal inbox. Account notifications, payment receipts, and dunning notices follow the same path, each triggered by the event that makes it true, not by a schedule that guesses.

Event confirmations, batched but individual

Registrants come in from [Typeform](/integrations/typeform). The agent builds one Send Batch Template Email call where each recipient carries their own merge info: name, session time, join details. One API request, hundreds of individually personalized confirmations. Before dispatch, the agent verifies each recipient's merge object fills every placeholder, holding back rows that would render broken, and posts those to a human instead of sending them wrong.

Human-in-Loop Highlight

Send Batch Template Email is a one-way door with a wide opening: a single call delivers a template to an entire recipient list, and a bad merge mapping does not send one embarrassing email, it sends hundreds, each addressed personally and each impossible to recall. So batch dispatch earns a checkpoint. The agent assembles the batch, renders a sample against the template, verifies per-recipient merge info covers every placeholder, and posts the summary: "312 recipients, template order-confirmation-v3, 4 rows held for missing merge fields, sample render attached." An operator approves, and only then does the batch leave. Single-message sends triggered by verified events flow without ceremony, because the blast radius of one receipt is one inbox. The gate scales with the consequence.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

3 actions

Sending

3
  • Send Email Sends a single transactional email with an HTML and/or plain-text body, a named sender, multiple to, cc, and bcc recipients, and optional open and click tracking. Recipients accept bare addresses or Name and address pairs, comma-separated. The sender must belong to a verified domain.
  • Send Template Email Sends a single email built from a ZeptoMail template, identified by template key or alias, with a merge-info object filling the template's placeholders. The default path for receipts, confirmations, and notifications with a stable layout.
  • Send Batch Template Email Sends a template to many recipients in one batch request, each recipient carrying an address, optional name, and optional merge-info for individual personalization. The high-volume path, and the action this page's human gate exists for.

Frequently Asked Questions

What can FlowRunner do with Zoho ZeptoMail?

FlowRunner agents can run Send Email, Send Template Email, and Send Batch Template Email in Zoho ZeptoMail.

Does connecting Zoho ZeptoMail to FlowRunner require OAuth?

No. Zoho ZeptoMail connects to FlowRunner with an API key, no OAuth flow required.

Can Zoho ZeptoMail trigger a FlowRunner workflow automatically?

Zoho ZeptoMail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Zoho ZeptoMail

$100 in credits. No card required. Connect in minutes.