Zagomail
Email MarketingZagomail is an email marketing platform for growing lists and sending campaigns. Agents manage lists, subscribers and tags, send campaigns, read form submissions, and react to subscriber events in real time through webhooks.
What This Integration Enables
Zagomail is built around the list and the tag as the unit of segmentation, and it is the one connector in this group that ships a real-time trigger rather than asking a workflow to poll. That combination is what makes it worth wiring an agent to: a form submission or a tag change can start work in seconds rather than at the next scheduled sweep. FlowRunner agents read lists and their fields and segments, create and update subscribers, apply and remove tags, read campaign statistics and form definitions, and manage the webhook subscriptions themselves.
The care in this connector goes into making Zagomail's failures visible. Every refusal arrives on an HTTP 200 with the real answer in the body, including an invalid API key and a subscriber who does not exist in the list, and one route reports success with a different capitalization from every other route. A workflow reading only the status code would hand all of that to the next step as a clean empty result. The connectors layer reads the in-body status first and raises it, case-insensitively, so an agent is never reasoning about a result that was actually a rejection. That is the precondition for trusting anything else on this page.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Store customers tagged by what they actually bought
An order completes in WooCommerce. The agent calls Search Subscriber By Email to resolve the buyer, or Create Subscriber if they are new, writing custom values against the list's own uppercase field tags rather than the labels shown in the interface, because those are what the payload uses. Get Tags resolves the product-category tag, and Add Subscriber Tag applies it. Repeat buyers accumulate tags that the marketing team's segments read directly, so a campaign aimed at people who bought twice in a quarter is a segment rather than a spreadsheet.
-
A form submission that becomes a routed lead
A submission arrives through a Zagomail form, and the New Zagomail Event trigger fires on the form-subscribe event. Get Forms tells the agent what that form collects, the subscriber is resolved and enriched, and the appropriate tag is applied. If the submission looks like an enterprise inquiry rather than a newsletter signup, the agent does not tag it into the nurture sequence at all; it posts the lead to Slack for a human to route. A parallel intake through Typeform feeds the same workflow, so the routing logic lives in one place regardless of which form the person found.
-
Campaign reporting that does not overstate itself
On a schedule the agent walks Get Campaigns and pulls Get Campaign Stats for each, landing the rows in Google Sheets. Zagomail's open rate counts repeat opens, so it can exceed one hundred percent, and the unique open rate is the figure that behaves like a percentage. The agent writes both, labels which is which, and builds the chart from the unique figure. A number nobody has to defend in a meeting is worth more than a flattering one.
Human-in-Loop Highlight
Delete Subscriber is the one operation here that combines an identifier switch with a delivery model that cannot tell two workflows apart. Every other subscriber route takes a subscriber UID. This one takes an email address instead, so a workflow carrying UIDs has to reach back for the address, and a stale address deletes whoever holds it today. Unsubscribe Subscriber, by contrast, takes the UID and leaves the record in place. On top of that, Zagomail does not put the webhook's ID in a delivery, so deliveries are matched to subscriptions by the event they name, and two triggers watching the same event both fire. A deletion wired to an unsubscribe event therefore runs once per listening flow.
So the agent proposes and waits. It posts: "17 addresses reached the unsubscribe event this week and are queued for removal from the Customers list. 3 of them still have open orders in the store. 2 resolve to a different subscriber UID than the one that triggered the event, which usually means the address was reassigned. Unsubscribe Subscriber keeps the record and the opt-out; Delete Subscriber removes it. Which do you want, and for which 17?" The marketer answers once. The tagging, the resolving, the enriching, and the reporting all ran without them. The call that removes a record on an identifier the agent cannot fully verify did not.
Agent Capabilities
23 actionsLists
4- Get Lists Lists the account's lists. A list record is grouped rather than flat, with the name, the default sender, and the notification settings in separate sections.
- Get List Reads one list's full configuration.
- Get List Fields Reads a list's custom fields, returning both the uppercase tag the payload uses and the label the interface shows. The read that runs before any subscriber write.
- Get List Segments Lists the segments defined on a list. Used to size and target an audience.
Subscribers
7- Get Subscribers Lists the subscribers on a list with paging.
- Get Subscriber Reads one subscriber by UID, including the dates that the create route does not return correctly.
- Search Subscriber By Email Resolves an email address to a subscriber. The bridge between an inbound event and the UID every other route wants.
- Create Subscriber Adds a subscriber to a list with custom field values keyed by field tag.
- Update Subscriber Updates a subscriber by UID.
- Unsubscribe Subscriber Marks a subscriber unsubscribed by UID and leaves the record in place. The reversible removal that preserves the opt-out.
- Delete Subscriber Removes a subscriber, keyed on the email address rather than the UID every sibling route uses. The operation this page's human gate exists for.
Tags
5- Get Tags Lists the account's tags with their tag IDs.
- Create Tag Creates a tag.
- Get Subscriber Tags Lists the tags on one subscriber, and is the only source of the link identifier that removal requires.
- Add Subscriber Tag Applies a tag to a subscriber, addressed by the tag's own ID.
- Remove Subscriber Tag Removes a tag from a subscriber, addressed by the link identifier rather than the tag ID. Passing the wrong one removes the wrong thing or nothing at all, which is why the preceding read is not optional.
Campaigns
2- Get Campaigns Lists campaigns and their state.
- Get Campaign Stats Reads a campaign's figures. The open rate counts repeat opens and can exceed one hundred percent, so the unique open rate is the one that behaves like a percentage.
Forms
1- Get Forms Lists the account's forms and their structure. Used so a workflow handles a form's real fields rather than assumed ones.
Webhooks
4- Get Webhooks Lists registered webhooks and the single event each one carries.
- Create Webhook Registers a webhook for one event, with the extra identifier that three of the six events require.
- Update Webhook Changes a webhook's target URL and its extra identifier. The event itself cannot be changed, so a different event means a new registration.
- Delete Webhook Removes a webhook registration.
Triggers
1 triggersEvent Triggers
1- New Zagomail Event Fires on one Zagomail webhook event: a subscriber activating, a subscriber unsubscribing, a form submission, a tag being added or removed, or a link being clicked. Three of those need an extra identifier naming the specific form, tag, or link. Zagomail publishes no payload schema and does not include the subscription's ID in a delivery, so the whole callback body is passed through and deliveries are matched by the event they name. Two flows watching the same event will both receive it, which is worth knowing before either of them writes anything.
Frequently Asked Questions
What can FlowRunner do with Zagomail?
FlowRunner agents can run Get Lists, Get List, and Get List Fields in Zagomail, plus 20 more actions.
Does connecting Zagomail to FlowRunner require OAuth?
No. Zagomail connects to FlowRunner with an API key, no OAuth flow required.
Can Zagomail trigger a FlowRunner workflow automatically?
Yes. Zagomail supports 1 trigger that can start a FlowRunner workflow automatically.
Other Email Marketing integrations
Start building with Zagomail
Free plan, no card required. Connect in minutes.