--- title: "SlimEmail Integration" description: "SlimEmail is a Vietnamese email marketing platform from SlimCRM. Agents subscribe, unsubscribe, check and delete subscribers, count a list, and create campaigns on your installation." url: https://flowrunner.ai/integrations/slimemail date_modified: 2026-09-04T14:28:58-07:00 --- # SlimEmail [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) SlimEmail is a Vietnamese email marketing platform from SlimCRM. Agents subscribe, unsubscribe, check and delete subscribers, count a list, and create campaigns on your installation. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 6 actions · API key · available [SlimEmail website](https://user.slimemail.vn/) · [Platform Documentation](https://help.slimemail.vn/start/huong-dan-nang-cao/tich-hop-api) · Capability data verified 2026-08-19 1. A new customer completes checkout in the store 2. Agent reads the buyer's email address and full name from the order 3. Get Subscription Status reports whether the address is already on the list, and in what state 4. Agent confirms the address is not already unsubscribed, bounced, or complained before writing 5. Subscribe adds the address to the named list 6. Agent posts the day's additions and the current Get Active Subscriber Count to the team channel 7. Before the list is mailed, a marketer confirms the list IDs and the subject line, because Create Campaign with Send Now has nothing to retract ## What This Integration Enables SlimEmail is a list endpoint, not a marketing suite, and the API says so honestly. Six routes, all of them form POSTs, none of them able to enumerate anything: there is no route that lists lists, campaigns, or brands, so every identifier starts life as a string somebody copied out of the interface. That shape tells you what SlimEmail is for. The sending list lives here, the system of record lives somewhere else, and the useful work is keeping the two in agreement without a person retyping addresses between them. FlowRunner agents do that work continuously. They read the state of an address with Get Subscription Status before deciding anything, add and remove people from the list, report the list's size, and assemble a campaign. What they do not do is decide when mail leaves. Create Campaign has a Send Now switch and no draft to fall back on, so that call belongs to a person. This is the whole point of [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) as a default rather than an afterthought: the agent handles the part that is mechanical and stops at the part that reaches ten thousand inboxes and cannot be recalled. ### Without FlowRunner **Identifiers copied by hand**: List and brand IDs exist only on the SlimEmail settings screen, so they end up pasted into spreadsheets and stale **Status checked one address at a time**: Knowing whether someone is subscribed, unconfirmed, or bounced means opening the interface and searching for them **No rehearsal before a send**: A campaign is either a draft nobody has reviewed or mail that left the moment it was created ### With FlowRunner **Identifiers carried by the workflow**: The IDs a person copies once are held in the flow and reused on every run **Status read before every write**: Get Subscription Status answers first, so the agent knows whether to subscribe, leave alone, or escalate **A named person releases the send**: The agent assembles the campaign and a marketer approves the audience and the subject before it goes ## Use Case Scenarios ### Checkout to list, without duplicates or resurrections An order lands in [WooCommerce](https://flowrunner.ai/integrations/woocommerce). The agent reads the buyer's email and name, then calls Get Subscription Status before doing anything else. SlimEmail answers in sentences rather than codes, and one of the seven possible answers is that the address does not exist in the list at all. A genuinely new buyer gets Subscribe. Someone already subscribed is left alone. Someone who previously unsubscribed or complained is not quietly re-added, because that is not a data problem the agent is entitled to solve. Those addresses go to a review queue instead. ### A list size the finance team can see On a schedule, the agent calls Get Active Subscriber Count for each list and appends the number to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), then posts the week-over-week movement to [Slack](https://flowrunner.ai/integrations/slack). The count is a bare number from the API, parsed into something a chart can use. Nobody logs into SlimEmail to answer "how big is the list now," and the number in the deck matches the number in the platform because they came from the same call. ### Offboarding an account without destroying its history A cancellation posted from the billing system reaches the agent. Unsubscribe and Delete Subscriber look interchangeable and are not. Unsubscribe marks the record and keeps it, so the opt-out survives and a later import cannot walk over it. Delete Subscriber removes the record entirely and is not reversible, which also means the same address can be added again later and will receive mail. The agent takes the reversible path by default, records the change in [HubSpot](https://flowrunner.ai/integrations/hubspot), and routes any request for an actual deletion to the person who owns data requests. ## Human-in-Loop Highlight Create Campaign takes a comma-separated list of List IDs, and no route in this API can tell you what those IDs point at. They were copied off the Email lists screen by a person, possibly months ago. Send Now turns that string into mail with no draft state in between, and Title is the internal name while Subject is what recipients read, which are easy to swap when both are being assembled by a workflow. So the agent builds the campaign and then stops. It posts: "Campaign ready. Subject line reads \*Your March statement is available\*. Target list IDs 14 and 22, currently 8,431 and 1,190 active subscribers. From address hello@example.vn. Send now, or hold?" The marketer reads the subject as a recipient would, confirms the two list IDs are the audiences they think they are, and answers. The agent did the assembly. The person owned the moment the mail became unrecallable. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 6 actions ### Subscribers 5 - **Subscribe** Adds an email address to a named list with its single full-name field. Whether the address lands as subscribed or unconfirmed depends on the list's own double opt-in setting, which this route cannot see or override, so pair it with Get Subscription Status when the distinction matters. - **Unsubscribe** Marks an address unsubscribed and keeps the record. The reversible, consent-preserving way to stop mailing someone. - **Delete Subscriber** Removes the record entirely. Not reversible, and it does not leave an opt-out behind, so a later import can re-add the same address. - **Get Subscription Status** Reports the state of one address on one list as a sentence: subscribed, unsubscribed, unconfirmed, bounced, soft bounced, complained, or not present at all. The read that runs before every write decision. - **Get Active Subscriber Count** Returns the number of active subscribers on a list. Used for reporting and for showing a person the size of an audience before they approve a send. ### Campaigns 1 - **Create Campaign** Builds a campaign against one or more list IDs, or against a brand, with a subject, a from address on a verified domain, and content. Send Now is what turns it into mail, and there is no draft state to retreat to afterward, which is why this operation waits for a person. ## Frequently Asked Questions ### What can FlowRunner do with SlimEmail? FlowRunner agents can run Subscribe, Unsubscribe, and Delete Subscriber in SlimEmail, plus 3 more actions. ### Does connecting SlimEmail to FlowRunner require OAuth? No. SlimEmail connects to FlowRunner with an API key, no OAuth flow required. ### Can SlimEmail trigger a FlowRunner workflow automatically? SlimEmail doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at SlimEmail?** This integration exposes SlimEmail to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/slimemail. Site index: https://flowrunner.ai/llms.txt