--- title: "Newsman Integration" description: "Newsman is a Romanian email service provider that puts marketing email, transactional SMTP, SMS, automations, coupons and ecommerce remarketing behind one API. Agents manage lists and subscribers, send newsletters and transactional messages, and sync store data for remarketing." url: https://flowrunner.ai/integrations/newsman date_modified: 2026-09-04T14:28:58-07:00 --- # Newsman [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) Newsman is a Romanian email service provider that puts marketing email, transactional SMTP, SMS, automations, coupons and ecommerce remarketing behind one API. Agents manage lists and subscribers, send newsletters and transactional messages, and sync store data for remarketing. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 174 actions · API key · available [Newsman website](https://ssl.newsman.app/) · [Platform Documentation](https://kb.newsman.com/api/1.2/) · Capability data verified 2026-08-19 1. A monitoring flow finds a newsletter stalled part way through its audience 2. Get Newsletter Status Actions returns the state changes the send has been through 3. Get Newsletter Stats reports how many messages have already gone out 4. Agent compares the delivered count against the segment size to size the remainder 5. Agent posts the two available recoveries and what each one would mail 6. A campaign owner chooses between resuming from the stopping point and starting again ## What This Integration Enables Newsman is a Romanian email service provider that declined to split its product into separate purchases. Marketing email, transactional SMTP, SMS, automations, coupon pools and ecommerce remarketing all sit behind one credential and one list object. For a retail team that matters more than it sounds: the same subscriber record that receives the newsletter is the one an abandoned cart automation chases, the one a coupon code is issued to, and the one whose order is recorded against the store. There is no reconciliation layer between those, because there is nothing to reconcile. The price of that breadth is that almost everything in Newsman is a state machine, and an agent has to drive it correctly. A newsletter is created, given segments, confirmed, and only then sent or scheduled. A segment is not live, so a send aimed at a rule based segment reaches whoever matched the last time it was recalculated. Bulk order imports save only the rows that validate and do not say which ones failed. Transactional sends answer with one row per recipient, so a partial failure looks like a clean success at the call level. FlowRunner agents handle exactly that kind of sequencing and reconciliation without getting bored, and then hand the consequential choices to a person. This connector ships no trigger, because Newsman allows only one webhook slot per list and a managed trigger would silently displace whatever was already there. ### Without FlowRunner **Six products, six credentials**: Email, SMS, transactional mail, automations, coupons and store data live in separate tools **Segments look live and are not**: A campaign goes to whoever matched the last time the segment was calculated **Bulk writes report success they did not earn**: An import of five thousand orders drops the invalid rows without naming them ### With FlowRunner **One account, one flow**: Newsletters, texts, transactional sends and store events are driven from the same workflow **Recalculation is a step**: The segment is refreshed and counted before anything is aimed at it **Partial outcomes are reconciled**: The agent checks what actually landed instead of trusting a call that answered cleanly ## Use Case Scenarios ### A newsletter that goes to the audience it was meant for Sending to a rule based segment without recalculating it is the most common way a Newsman campaign reaches the wrong people. So the agent sequences it deliberately: Refresh Segment first, then Count Segment Subscribers to see what the recalculation produced, then Create Newsletter, Set Newsletter Segments and Set Newsletter Excluded Segments, because exclusion wins over inclusion and the suppression list belongs in the campaign rather than in somebody's memory. Confirm Newsletter moves it to the confirmable state. The audience size and the exclusions post to [Slack](https://flowrunner.ai/integrations/slack) for a look before Schedule Newsletter is called with a UTC timestamp. ### Store orders, coupons and cart recovery on one credential Orders from [WooCommerce](https://flowrunner.ai/integrations/woocommerce) or [PrestaShop](https://flowrunner.ai/integrations/prestashop) reach the agent, which records them with Save Order, sending the shipping and fee fields explicitly as zero when there is no charge because both are required and zero is a valid value that is easy to omit. When an order completes, Set Purchase Status updates it and, supplied with the customer's address, also clears that customer's cart, which is how an abandoned cart journey is closed rather than left running against somebody who already bought. Loyalty coupons come from the same account: Add Coupon builds the pool and Generate Coupon Codes schedules the minting. ### Transactional mail where a partial failure is not invisible An application sends receipts and password notices through Send Transactional Message. The response is a row per recipient carrying the address, the status, a reason and a send ID, and a batch where two of forty were refused still answers successfully at the call level. The agent reads every row. Refusals are checked with Get Email Reject Status, which reports the four counts behind a block, unsubscribes, hard bounces, spam complaints and soft bounces past the threshold, and anything that turns out to be a stale hard bounce on an address the customer is actively using is raised rather than cleared, because Remove Email Reject Status overrides a real signal. The reconciliation lands in [Google Sheets](https://flowrunner.ai/integrations/google-sheets). ## Human-in-Loop Highlight Newsman gives a stalled newsletter two recoveries whose names differ by one word and whose consequences do not overlap at all. Resume Newsletter continues from where the send stopped. Restart Newsletter starts from the beginning, which means every subscriber who already received the message receives it again. Nothing in the newsletter's status distinguishes the case where restarting is correct, such as a send that went out with a broken link and needs to reach everyone again, from the case where it is a duplicate mailing to thousands of people. That is a judgment about content and audience, and it belongs to a person. So a monitoring flow that finds a stalled send does the measurement and stops. It calls Get Newsletter Status Actions for the state history and Get Newsletter Stats for what has already gone out, then posts: "Newsletter 'October offer' paused after 8,300 of 21,400 recipients, four hours ago. Resume mails the remaining 13,100. Restart mails all 21,400, including the 8,300 who already have it. Which one?" A campaign owner answers in a sentence. The agent watched the send, gathered the counts, and named the exact cost of each option, and it did not decide which thirteen thousand or twenty-one thousand people hear from you tonight. That division of labor is what [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) orchestration is for. 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 174 actions ### Lists 14 - **Get Lists** Lists every subscriber list on the account. Their IDs are the first argument of almost every other operation, so this is where most flows start. - **Get Account List Info** Reads the account's lists with their usage information. The vendor documents this method's endpoint as a different method, and this action calls the name the page itself is filed under. - **Count List Subscribers** Returns how many subscribers a list holds. - **Get List Subscribers** Reads a page of a list's subscribers filtered by status. A status is required and there is no all option, so pick one of subscribed, unsubscribed, bounced, spam or inactivated. Paging starts at zero, and the subscriber ID comes back under a Romanian key rather than an English one. - **Get List Properties** Reads a list's sending configuration: from address and name, reply-to, the link parameters appended to every tracked URL, and where an unsubscriber is redirected. - **Get List Property** Reads one of a list's properties by name. - **Update List Property** Changes one of a list's properties. - **Update List Properties** Changes several of a list's properties at once. The link parameter field is a query string appended to every tracked link, so a malformed value breaks every URL in the next send. - **Update List Name** Renames a list. - **Get List IPs** Lists the sending IP addresses assigned to a list. - **Get List Moderators** Lists the moderator addresses on a list. - **Set List Moderators** Replaces the moderator addresses on a list. Anyone left out stops being a moderator, so read the current set first. - **Get Subscriber Variables** Lists the custom variable names in use on a list's subscribers. This is what tells a flow which property keys the list actually understands, and the same keys are what segment criteria are built from. - **Refresh Subscriber Variables** Rebuilds the list's cache of subscriber variable names. Run it after writing a property key that has never been used on the list, or segment building will not offer it. ### Subscribers 18 - **Get Subscriber** Reads one subscriber by its numeric ID. - **Get Subscriber By Email** Reads one subscriber by address within a list. A subscriber belongs to a list, so the same address on two lists is two different records with two different IDs. - **Get Subscribers Batch** Reads several subscribers at once, by address or by ID, returning their properties and segment membership together. Much cheaper than one read per subscriber. - **Search Subscribers** Finds subscribers in a list by keyword and status. Paging starts at zero and the page size is capped. - **Save Subscriber** Subscribes an address directly, with no confirmation email. Properties become segment criteria, and a key carrying the tag prefix sets a tag rather than a property of that name. - **Start Subscribe** Starts a double opt in, which sends a confirmation email to the address. The subscriber is not on the list until they click, and the IP given here is overwritten by the one they confirm from, which is the point: the recorded consent is theirs rather than yours. - **Save Unsubscribe** Unsubscribes an address directly, with no confirmation email. - **Save Unsubscribe By ID** Unsubscribes by subscriber ID rather than address. The vendor documents this method's endpoint as a different method taking an address, and this action calls the name the page is filed under. - **Start Unsubscribe** Starts a confirmed unsubscribe, which sends the recipient an unsubscribe confirmation email rather than acting immediately. - **Update Subscriber** Changes a subscriber's address and name. Leaving the address empty keeps the current one, and an invalid one is refused. - **Update Subscriber Property** Sets one custom property on a subscriber. A key carrying the tag prefix sets a tag instead of a property. - **Update Subscriber Properties** Sets several custom properties on one subscriber. - **Update Subscriber Properties Batch** Sets properties on many subscribers in one call, keyed by subscriber ID or address. The vendor caps the batch size, and this action refuses an oversized call rather than letting it fail halfway. - **Add Subscriber Tag** Adds one tag to a subscriber. - **Add Subscriber Tags** Adds several tags to a subscriber in one call. - **Remove Subscriber Tag** Removes one tag from a subscriber. - **Remove Subscriber Tags** Removes several tags from a subscriber in one call. - **Get Subscriber History** Reads everything that has happened to one subscriber: sends, views, clicks, bounces and unsubscribes. ### Consent and Erasure 5 - **Get Subscriber Profiling Allowed** Reads whether a subscriber has consented to behavioral profiling. This is a consent flag rather than a preference, so honor it before building a behavioral segment. - **Set Subscriber Profiling Allowed** Records whether a subscriber consents to behavioral profiling. - **Anonymise List Subscriber** Scrambles a subscriber's identity beyond recovery for an erasure request. This is not a delete and not an unsubscribe, and it cannot be undone. - **Anonymise Subscriber By Email** Erases a subscriber's identity by address. Irreversible. - **Anonymise Subscriber By ID** Erases a subscriber's identity by subscriber ID. Irreversible. ### Segments 14 - **Get Segments** Lists a list's segments. - **Search Segments** Finds a list's segments by regular expression on the name. - **Create Segment** Creates a segment on a list. It is created empty and with no criteria, because criteria are built in the Newsman interface and subscribers can be added to a manual segment by hand. - **Update Segment Name** Renames a segment. - **Delete Segment** Deletes a segment. The subscribers in it are untouched. - **Clear Segment** Empties a segment without deleting it. The subscribers themselves are untouched. - **Refresh Segment** Recalculates a rule based segment against the list as it stands now. A segment is not live, so a newsletter sent without refreshing first goes to whoever matched last time. - **Count Segment Subscribers** Returns how many subscribers a segment currently holds. The cheapest way to size an audience before aiming anything at it. - **Get Segment Subscribers** Reads a page of a segment's subscribers. Paging starts at zero and the page size is capped. - **Add Subscriber To Segment** Puts a subscriber into a segment. This only works on a manual segment, because a rule based one is recalculated and will drop the subscriber again. - **Remove Subscriber From Segment** Takes a subscriber out of a segment. - **Mass Unsubscribe Segment** Unsubscribes every subscriber in a segment. Count the segment first, and remember that a rule based segment may have grown since it was last refreshed. - **Mass Deactivate Segment** Deactivates every subscriber in a segment. Deactivated is a separate state from unsubscribed and is usually used for addresses that keep failing. - **Mass Anonymise Segment** Erases every subscriber in a segment. Irreversible, and the segment membership is the only record of who it applied to. ### Newsletters 24 - **Get Newsletters** Lists a list's newsletters, optionally narrowed to a date range and a status. The status is a number running from unconfirmed through sent, and leaving it empty returns every status. - **Create Newsletter** Creates a newsletter in a list and returns its ID. Creating it does not send it: the sequence is create, set segments, confirm, then send or schedule. The subject is required and lives inside the properties, and the resend-to-unopened option targets a different audience than the segments do. - **Update Newsletter** Replaces a newsletter's content and properties. Only works before the newsletter is sending, so pause it first if it is scheduled. - **Get Newsletter Properties** Reads a newsletter's sender configuration and campaign name. - **Get Newsletter Property** Reads one of a newsletter's properties by name. - **Update Newsletter Property** Changes one of a newsletter's properties. - **Update Newsletter Properties** Changes several of a newsletter's properties at once. - **Get Newsletter Segments** Lists the segments a newsletter is aimed at. - **Set Newsletter Segments** Replaces which segments a newsletter goes to. This is the audience, so getting it wrong sends to the wrong people. - **Get Newsletter Excluded Segments** Lists the segments a newsletter deliberately skips. Anyone in an excluded segment is left out even if another segment includes them. - **Set Newsletter Excluded Segments** Replaces which segments a newsletter skips. Exclusion wins over inclusion. - **Confirm Newsletter** Moves a newsletter from unconfirmed to confirmed, which is the state it has to reach before it can be sent or scheduled. - **Send Newsletter Confirmation** Sends the newsletter to its audience now. Despite the name this is the send rather than a confirmation email to you. - **Schedule Newsletter** Schedules a newsletter to send at a given moment. The time is UTC rather than the account's zone. - **Pause Newsletter** Pauses a sending or scheduled newsletter. - **Resume Newsletter** Resumes a paused newsletter from where it stopped. This is almost always what a recovery flow wants. - **Restart Newsletter** Restarts a newsletter from the beginning rather than from where it stopped, so people who already received it can receive it again. - **Cancel Newsletter** Cancels a newsletter so it will not be sent. - **Send Newsletter Test** Sends a test copy of some content to named addresses without creating or touching a real newsletter. It takes the content rather than a newsletter ID, so it tests what you pass rather than what is stored. - **Set Newsletter Alternate Content** Stores an alternate version of a newsletter, viewable online through the view-online link. The vendor documents this write as a GET, which is what this action sends. - **Get Newsletter Stats** Reads a newsletter's aggregate results: sent, delivered, opens, clicks, bounces, unsubscribes and spam complaints. - **Get Newsletter Links Clicked** Reads which links in a newsletter were clicked and how often. - **Get Newsletter Status Actions** Reads the state changes a newsletter has been through, which is how a flow tells a paused send from a finished one. - **Get Newsletter Subscribers History** Reads what individual recipients did with a newsletter, newest first. Paging is a time cursor rather than a page number, so pass the oldest timestamp you have seen to get the next slice. ### Split Testing 7 - **Create AB Variant** Adds a variant to a newsletter's split test. A variant is itself a newsletter, so the ID that comes back is a child newsletter ID, and anything left empty is inherited from the parent. - **Get AB Variant** Reads one split test variant with the content and properties it was created with. - **Get AB Variant IDs** Lists the variant IDs of a newsletter's split test. - **Delete AB Variant** Removes a variant from a split test. - **Get AB Test Properties** Reads a split test's settings: how long the test runs, how the winner is picked and how big the test group is. - **Set AB Test Properties** Configures a split test. The duration is in minutes and measures how long the platform waits after the test group has been sent, and the test group size is a percentage of the audience. - **Set AB Test Winner** Declares a variant the winner, which is what sends it to the rest of the audience. Only needed when the winner method is manual. ### Imports 4 - **Import CSV** Imports subscribers from CSV text. The first row is a header and must contain the address column, some names are recognized and every other column becomes a subscriber property, and a segment entry carrying the tag prefix sets a tag rather than adding to a segment. Row, column and size limits apply per call. - **Schedule CSV Import** Queues a CSV import to run in the background, optionally after a delay. Use this rather than the inline import for anything large enough to time out. - **Schedule JSONL Import** Queues a JSON Lines import to run in the background. One JSON object per line, each carrying at least an address, and the vendor splits large files into several background tasks. - **Get Import Status** Reads how a scheduled import is going. ### Downloads 13 - **Download Subscribed** Returns a temporary CSV link with a list's subscribed addresses. The link expires within about an hour and works only from the IP that requested it. - **Download Unsubscribed** Returns a temporary CSV link with a list's unsubscribed addresses. - **Download All Unsubscribed** Returns a temporary CSV link with every unsubscribe on the account rather than just the list given. This is the suppression list a flow should check before importing anywhere. - **Download Bounced** Returns a temporary CSV link with a list's bounced addresses. - **Download Reported Spam** Returns a temporary CSV link with the addresses that reported a list as spam. - **Download Segment** Returns a temporary CSV link with a segment's subscribers. - **Download Search** Returns a temporary CSV link for a custom search of a list. The four criteria are flags whose defaults are not neutral, and this is the only download that lets a flow widen the one hour and single IP restriction. - **Download Newsletter Sent** Returns a temporary CSV link with the addresses one newsletter was sent to. - **Download Newsletter Viewed** Returns a temporary CSV link with the addresses that opened one newsletter. - **Download Newsletter Clicked** Returns a temporary CSV link with the addresses that clicked a link in one newsletter. - **Download Newsletter Bounced** Returns a temporary CSV link with the addresses that bounced from one newsletter. - **Download Newsletter Unsubscribes** Returns a temporary CSV link with the addresses that unsubscribed because of one newsletter. - **Download Newsletter Reported Spam** Returns a temporary CSV link with the addresses that reported one newsletter as spam. ### Confirmation Templates and Drafts 7 - **Search Mail Templates** Lists a list's confirmation email templates. These are only the subscribe and unsubscribe confirmation emails, not newsletter content templates. - **Get Mail Template** Reads one confirmation email template with its content. - **Add Mail Template** Creates a confirmation email template for a list. Leaving the text version empty is fine, because the vendor generates it from the HTML. - **Update Mail Template** Replaces a confirmation email template, so the list, type, subject and content all have to be sent again. - **Delete Mail Template** Deletes a confirmation email template. Any opt-in flow pointing at it falls back to the list default. - **Get Draft Info** Reads a draft's stored information. - **Render Draft** Renders a draft's template with the values given and returns the resulting HTML. Useful for previewing personalized content before a send. ### Automations 4 - **Get Automations** Lists a list's automation workflows. The date range filters on when a workflow was last updated rather than on when it ran. - **Get Automation Workflow** Reads one automation workflow and its definition. - **Set Automation Workflow Status** Turns an automation on or off. Turning one on starts sending to everyone who matches its trigger from that moment. - **Get Automation Stats** Reads how automations performed over a period, optionally narrowed to particular workflows or one trigger. ### Webhooks 3 - **Get List Webhook** Reads the webhook configured on a list, if any. - **Set List Webhook** Sets the webhook on a list. There is only one slot per list, so this replaces whatever was configured before without warning and with no way to have two. Read the current webhook first when anything else might be using it. - **Remove List Webhook** Removes a list's webhook. It takes only the list ID, because a list has at most one. ### Transactional 18 - **Send Transactional Message** Sends a transactional email over the API. The SMTP account is chosen from the list's from address unless one is named, so the list is not decoration. The answer is a row per recipient carrying address, status, reason and send ID, so a partial failure looks like a success at the call level and every row has to be read. - **Send Transactional Template** Sends a transactional email built from a stored template. The message needs a template reference alongside the sender and subject, and as with the inline route the answer is one row per recipient. - **Send Transactional Raw** Sends a pre-built MIME message as it stands. Nothing is templated or rewritten, so the headers, encoding and multipart structure are entirely yours to get right. - **Get Transactional Templates** Lists the stored transactional templates on an SMTP account, keyed by template ID. - **Get Transactional Template** Reads one stored transactional template with its type and content. - **Save Transactional Template** Stores a transactional template on an SMTP account. The vendor's parameters carry no template identifier, so an account appears to hold one template per content type and saving replaces it. - **Delete Transactional Template** Deletes a stored transactional template. As with saving, the vendor's parameters carry no template identifier, so this removes the account's template rather than a named one. - **Render Transactional Template** Renders the account's stored transactional template and returns the resulting HTML. - **Get Transactional Account History** Reads what an SMTP account has done, newest first. Paging is a time cursor, so pass the oldest timestamp you have seen. - **Get Transactional Account Stats** Reads an SMTP account's aggregate numbers over a period, grouped by day or hour. - **Get Transactional Tags** Lists the tags an SMTP account groups its transactional mail under. - **Create Transactional Tag** Creates a tag on an SMTP account, so transactional sends can be grouped and reported separately. - **Delete Transactional Tag** Removes a tag from an SMTP account. - **Get Transactional Tag Stats** Reads one tag's numbers over a period, grouped by day or hour. - **Get Email History** Reads what one address has done across an SMTP account's transactional mail, newest first. - **Get Email Reject Status** Reads why an address would be refused transactional mail. The answer counts unsubscribes, hard bounces, spam complaints and soft bounces, and any of the first three blocks the address outright while soft bounces block it past a threshold. Check this before blaming a send that reported nothing. - **Add Email Reject Status** Adds a reject status to an address, which stops transactional mail reaching it. This is the manual suppression switch. - **Remove Email Reject Status** Clears reject statuses from an address, which lets transactional mail reach it again. Clearing a hard bounce or a spam complaint overrides a real signal, so do it only when the cause is understood. ### SMS 27 - **Get SMS Lists** Lists the account's SMS type lists. An SMS campaign can only be created on one of these, not on an email list. - **Get SMS Credits** Reads how many SMS credits are left. Worth checking before a campaign, because a send that runs out of credit stops part way. - **Send One SMS** Sends a single text message immediately. The list must be an SMS type list. - **Get SMS Subscriber By Telephone** Reads an SMS subscriber by number. The vendor documents this method under a different namespace, and this action calls the name the page is filed under and falls back to the documented one. - **Save SMS Subscriber** Subscribes a number to an SMS list directly, with no confirmation message. - **Save SMS Unsubscribe** Unsubscribes a number from an SMS list. The vendor's own parameter table for this route describes the number as an address, which is a documentation defect rather than a different field. - **Get SMS Campaigns** Lists a list's SMS campaigns. The status accepts a comma separated combination as well as one value, and it carries a canceled state the newsletter statuses do not have. - **Create SMS Campaign** Creates an SMS campaign on an SMS list. Creating it does not send it: set segments, confirm, then send or schedule. - **Confirm SMS Campaign** Confirms an SMS campaign, which is the state it must reach before it can be sent. - **Send SMS Campaign Confirmation** Sends the SMS campaign to its audience now. - **Schedule SMS Campaign** Schedules an SMS campaign to send later. The time is UTC. - **Pause SMS Campaign** Pauses a sending SMS campaign. - **Resume SMS Campaign** Resumes a paused SMS campaign from where it stopped. - **Restart SMS Campaign** Restarts a canceled or already sent campaign, which means the whole audience can receive it a second time. Resuming is what a paused send needs. - **Cancel SMS Campaign** Cancels an SMS campaign so it will not be sent. - **Get SMS Campaign Segments** Lists the segments an SMS campaign is aimed at. - **Set SMS Campaign Segments** Replaces which segments an SMS campaign goes to. - **Get SMS Campaign Excluded Segments** Lists the segments an SMS campaign deliberately skips. - **Set SMS Campaign Excluded Segments** Replaces which segments an SMS campaign skips. Exclusion wins over inclusion. - **Get SMS Campaign Properties** Reads an SMS campaign's properties. - **Get SMS Campaign Property** Reads one of an SMS campaign's properties by name. - **Update SMS Campaign Property** Changes one of an SMS campaign's properties. The vendor lists only the campaign name as writable here. - **Update SMS Campaign Properties** Changes several of an SMS campaign's properties at once. - **Get SMS Campaign Stats** Reads an SMS campaign's aggregate results. - **Get SMS Campaign Links Clicked** Reads which links in an SMS campaign were clicked, how often and when last. - **Get SMS Campaign Status Actions** Reads an SMS campaign's state and which actions are currently allowed on it, which is the reliable way to know whether it can be paused, resumed or canceled. - **Get SMS Campaign Subscribers History** Reads what individual recipients did with an SMS campaign. The cursor here is a microtime with a fractional part rather than a whole second. ### Coupons 10 - **Get Coupons** Lists a list's coupons. - **Get Coupon** Reads one coupon by ID. - **Get Coupon By Name** Reads one coupon by name rather than ID. - **Add Coupon** Creates a coupon pool. The two types behave completely differently: imported codes are uploaded by you and configure low-stock notifications, while codes generated by API call a webhook of yours to mint them and configure the discount, currency and regeneration thresholds. - **Update Coupon** Changes a coupon's settings. The vendor's own prototype for this method carries no coupon identifier, which cannot be right for an update, so this action sends one because omitting an identifier the server needs fails loudly while sending one it ignores does not. - **Delete Coupon** Schedules the deletion of a coupon and its codes. The answer means the job was queued rather than that the coupon is gone. - **Get Coupon Codes** Reads a coupon's individual codes and who they went to. Paging here starts at one rather than zero, unlike the subscriber collections. - **Generate Coupon Codes** Schedules the generation of new codes for a coupon. Leaving the count empty uses the coupon's own regeneration settings rather than generating nothing. - **Import Coupon Codes** Schedules an import of codes into a coupon. The vendor's prototype leaves the codes parameter unnamed, so this action sends them under the expected key and exposes a hatch for an account that expects a different one. - **Clear Coupon Codes** Schedules the removal of every code from a coupon. Codes already sent to recipients stop working. ### Ecommerce Remarketing 6 - **Get Remarketing Settings** Reads a list's remarketing configuration, which is what links it to a website. - **Save Order** Records one order against the website a list is linked to. Seven fields are required and two of them are easy to miss because zero is a valid value: shipping and fees must be sent as zero when there is no charge rather than left out. The total is what the buyer actually paid, and every product line needs an ID, a quantity and a price. - **Save Orders** Records up to five thousand orders in the background. Only orders that pass validation are saved and the answer does not say which failed, so a batch that half succeeds looks like one that fully succeeded and needs reconciling afterward. - **Save Orders From XML** Records up to five thousand orders from an XML document, for shops that already export one. The same silent validation rule applies: invalid orders are dropped without being named. - **Set Purchase Status** Updates one order's status. The allowed values are platform dependent, so a WordPress shop, Magento and PrestaShop each use their own set. Supplying an address also clears that customer's cart, which is how an abandoned cart journey is closed. - **Clear Cart** Clears one customer's abandoned cart on the website a list is linked to, which stops the abandoned cart automation chasing them. ## Frequently Asked Questions ### What can FlowRunner do with Newsman? FlowRunner agents can run Get Lists, Get Account List Info, and Count List Subscribers in Newsman, plus 171 more actions. ### Does connecting Newsman to FlowRunner require OAuth? No. Newsman connects to FlowRunner with an API key, no OAuth flow required. ### Can Newsman trigger a FlowRunner workflow automatically? Newsman doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Newsman?** This integration exposes Newsman 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/newsman. Site index: https://flowrunner.ai/llms.txt