AcyMailing
Email MarketingAcyMailing is the newsletter extension for Joomla and WordPress sites. Agents manage users, lists, and subscriptions, send emails and transactional messages, run campaigns and follow-up sequences, and read statistics from your own site.
What This Integration Enables
AcyMailing is the newsletter that lives inside your own site. There is no vendor host: every call goes to your Joomla or WordPress installation, the subscriber records sit in your database next to the CMS accounts they belong to, and the REST API is switched off until you turn it on. For teams who chose a self hosted CMS deliberately, that is the whole point, and it changes what an agent is actually doing here. It is not syncing a customer into somebody else's platform. It is writing to your own site.
FlowRunner agents create and update subscribers, manage lists and the subscribe and unsubscribe records against them, build and send campaigns, read the click detail behind the headline numbers, maintain templates, and assemble follow up sequences step by step. The platform also draws a distinction worth knowing: an email is a mail record, a campaign points at one, and sending one message to one address takes a mail identifier rather than a campaign identifier. Agents work with that grain, and the human-in-the-loop gates on this page sit where a write to your own site becomes a send from your own domain.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
Post purchase onboarding that respects what is already there
An order completes in WooCommerce on the same site. The agent calls Get User Subscriptions to see which lists the buyer already sits on, then Create Or Update User to write or refresh the subscriber record, choosing explicitly whether the confirmation email goes out and whether follow ups fire. Subscribe Users adds the buyer to the customer list, with the welcome email switched on for genuinely new customers and off for a repeat buyer who has had it three times already. Get List Subscribers confirms the result, and the summary posts to Slack.
-
A follow up sequence maintained as data rather than by hand
Marketing wants a five step onboarding sequence adjusted. The agent reads Get Follow Ups and Get Follow Up to recover the existing trigger, conditions and attached emails, calls Create Or Update Follow Up for the sequence itself, then Attach Email To Follow Up for each step. The delays are counted from the trigger rather than from the previous email, which is exactly the arithmetic that goes wrong when a person edits it in a hurry, so the agent computes the cumulative values. Delete Email From Follow Up removes a step that is no longer wanted, and subscribers partway through simply skip it rather than stalling. Delete Follow Up retires the whole sequence when the campaign ends.
-
Reporting that outlives the campaign
On a schedule, the agent walks Get Campaigns, then pulls Get Campaign Statistics for the headline numbers, Get Campaign Statistics Detailed for the per recipient rows, Get Campaign Clicks By User for who clicked and Get Campaign Clicks By Link for what they clicked. Everything lands in Google Sheets as a running record. This matters more here than it usually does, because Delete Campaign takes the campaign's statistics with it, so a cleanup that runs before the export destroys the reporting history. The agent exports first, then proposes the cleanup list.
Human-in-Loop Highlight
Four switches on this API turn a quiet write into a send, and all four default to true. Create Or Update User sends the confirmation email and fires follow ups and automations. Subscribe Users sends each list's welcome email. Unsubscribe Users sends each list's unsubscribe email. Leaving them out is not the same as turning them off. That is survivable on one signup and it is not survivable on a backfill: importing a few years of historic customers with the defaults intact mails every one of them a confirmation and a welcome, starts every armed follow up sequence at once, and does it from your own site's sending domain, where the reputation damage lands on you rather than on a vendor. There is no undo, because the mail is already in AcyMailing's queue. So the agent builds the import, resolves the list memberships, and stops before the first write: "This backfill covers historic customers, most of whom have never received mail from this site. I have Send Confirmation, Trigger, and Send Welcome Email set to off, which writes the records silently. Confirm, or tell me which of these should send." A named owner answers, the agent runs the import with those settings recorded in the run, and the sequences are armed afterwards for new signups only. The reconciliation work is the agent's. The decision to mail several years of people at once is not.
Agent Capabilities
33 actionsUsers
3- Get Users Reads a page of AcyMailing users with their subscription state, confirmation state and engagement timestamps, including the link back to the underlying Joomla or WordPress account.
- Create Or Update User Creates a user, or updates the existing one with that address. Two switches decide whether this is a quiet write or a send: one fires the confirmation email, the other fires follow ups and automations, and both default to on.
- Delete User Deletes an AcyMailing user by address or identifier. This removes the subscriber record and does not touch the CMS account behind it.
Lists and Subscriptions
8- Get Lists Reads a page of subscription lists with their color, visibility and the welcome and unsubscribe emails attached to them.
- Create List Creates a subscription list. An invisible list is hidden from subscription forms, which is how a list is kept for internal segmentation.
- Delete List Deletes a subscription list. The users on it are not deleted; they lose that subscription.
- Get User Subscriptions Reads which lists one user is subscribed to. The lookup that keeps a write from duplicating a membership that already exists.
- Get List Subscribers Reads a page of the users subscribed to one or more lists.
- Get List Unsubscribers Reads a page of the users who have unsubscribed from one or more lists, which is the set the subscriber listing deliberately leaves out.
- Subscribe Users Subscribes existing users to lists. The addresses must already be AcyMailing users, and the welcome email defaults to sending wherever a list has one attached.
- Unsubscribe Users Unsubscribes users from lists. The unsubscribe email defaults to sending wherever a list has one attached.
Emails
2- Get Emails Reads a page of the emails defined in AcyMailing. These are mail records rather than campaigns, and their identifiers are what the single send operation takes.
- Send Email To User Sends one email to one address immediately. It takes a mail identifier rather than a campaign identifier, and by default it does nothing for an address that is not already a subscriber.
Campaigns
5- Get Campaigns Reads a page of campaigns with their sending type and state.
- Get Campaign Reads one campaign in full.
- Create Or Update Campaign Creates a campaign, or updates an existing one. It does not send: releasing the campaign is a separate call, and the sending type decides what happens when it is made.
- Send Campaign Sends a campaign to its lists. There is no confirmation step and no undo, and because AcyMailing delivers through its own queue, success here means queued rather than delivered.
- Delete Campaign Deletes a campaign. Its statistics go with it, so any report that depends on them has to be exported first.
Statistics
4- Get Campaign Statistics Reads a campaign's headline numbers: sent, opened, clicked, bounced and unsubscribed.
- Get Campaign Statistics Detailed Reads the per recipient rows behind those numbers.
- Get Campaign Clicks By User Reads which users clicked in a campaign, and how often.
- Get Campaign Clicks By Link Reads which links were clicked, and how often. The other half of the click picture.
Templates
5- Get Templates Reads a page of email templates.
- Get Template Reads one template in full, including its body and default sender details.
- Create Template Creates an email template with its default sender details and body. The body is the body part only; the surrounding markup and stylesheet are applied by AcyMailing.
- Update Template Changes an email template's content or defaults.
- Delete Template Deletes an email template. Emails already built from it keep their content.
Follow Ups
6- Get Follow Ups Lists the account's follow up sequences.
- Get Follow Up Reads one sequence with its trigger, conditions and attached emails.
- Create Or Update Follow Up Creates a follow up sequence, or updates one. The loop setting re-triggers the sequence for a subscriber who has already finished it, so a loop without a delay repeats immediately.
- Attach Email To Follow Up Adds an email to a sequence, or updates one already attached. The delay is counted from the trigger rather than from the previous email, so a sequence's delays are cumulative.
- Delete Email From Follow Up Removes one email from a sequence. Subscribers already partway through keep going and skip the step that is gone.
- Delete Follow Up Deletes a sequence together with the emails attached to it.
Frequently Asked Questions
What can FlowRunner do with AcyMailing?
FlowRunner agents can run Get Users, Create Or Update User, and Delete User in AcyMailing, plus 30 more actions.
Does connecting AcyMailing to FlowRunner require OAuth?
No. AcyMailing connects to FlowRunner with an API key, no OAuth flow required.
Can AcyMailing trigger a FlowRunner workflow automatically?
AcyMailing doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Other Email Marketing integrations
Start building with AcyMailing
Free plan, no card required. Connect in minutes.