FlowRunner
PricingContact
Theme
Start Free

SendOwl

E-commerce

SendOwl sells and delivers digital goods: files, software licenses, bundles, subscriptions and drip content. Agents fulfill orders taken on another checkout, refund and revoke access, run discount campaigns, and validate software license keys from your own application.

55 actions Basic auth available
SendOwl website Platform Documentation Capability data verified 2026-08-26
A paid order arrives from the storefront or gateway that took the money
Agent reads the buyer email and the purchased variant from the order
Look Up Product By Shopify Variant resolves that variant to the SendOwl product or bundle
List Product Licenses confirms the pool still holds unallocated keys for the product
Issue Product Order creates the completed order, delivering the file and the license to the buyer
The order and its allocated license append to the operations record and confirm in the team channel
A support owner picks up any order whose variant matched nothing, and decides what the buyer actually bought

What This Integration Enables

SendOwl is built on a decision most commerce platforms do not make: the checkout is optional. Its issue operations create a completed order without SendOwl taking any payment at all, which means you can sell on a storefront, a marketplace, an invoice or a stage, and still hand the delivery to the system that is actually good at it. That is the point of the product. Handing a buyer a file is easy until you need expiring links, a download cap, a license key drawn from a pool, a drip schedule that reaches people who bought last month, and a way to take it all back when the payment reverses.

FlowRunner agents work both halves of that. They fulfill orders taken elsewhere, keep a warehouse or ledger in step by polling on an update window, run discount campaigns down to individual single-use codes, validate license keys on behalf of your own application so your account credentials never ship inside it, and handle the post-purchase queue: correcting a mistyped buyer email, resending a delivery notification, refunding, revoking, and restoring. The human-in-the-loop step sits where it belongs on a platform whose product is a copyable file, and that place is not where most people expect.

Without FlowRunner

Delivery tied to one checkout Selling anywhere else means rebuilding file delivery and license issue for that channel
Support requests answered by hand Every lost download, mistyped email and refund is a person clicking through the dashboard
License pools noticed when they run out Nobody watches the unallocated key count until a buyer gets an order with no key in it

With FlowRunner

Payment and delivery separated Money is taken wherever it makes sense, and one issue call still delivers the file, the key and the receipt
Post-purchase handled as a workflow The agent finds the order, corrects the address, resends the email, and escalates the calls that need judgment
Pools topped up before they stall sales A scheduled read counts what is unallocated and adds keys ahead of the shortfall

Use Case Scenarios

  • Fulfillment from a checkout SendOwl never saw

    An order is paid on Shopify, on an invoice, or through your own gateway. The agent takes the variant or the SKU, resolves it to a SendOwl product or bundle, checks that the license pool behind it still has unallocated keys, and calls the matching issue operation with the financial transaction detail recording what was actually charged. The buyer gets the file and the key immediately. The order id and the allocated license go to Google Sheets for the ledger, and a line posts to Slack. Where several items were bought together, the agent issues a bundle rather than a series of separate orders, because that is the shape the platform supports.

  • A campaign of single-use codes, tracked end to end

    Marketing needs codes for a partner list. The agent creates the discount with a generated batch of single-use codes, reads them back once they have been written, restricts the discount to the right products, and hands the codes out through Brevo or writes them into the partner's sheet. When one code leaks, the agent retires that single code and leaves the rest of the batch working, which is the difference between a contained incident and cancelling a campaign.

  • The lost download queue

    Customers write in saying their file never arrived or their downloads ran out. The agent finds the orders by buyer email, reads each one in full, and sorts them. A mistyped address is corrected and the delivery email resent, which is safe because it goes to the buyer's own address. A confirmed chargeback gets access revoked, which is safe because it can be granted back. Anything that asks for the download counter to be reset does not get resolved by the agent at all, and the next section explains why.

Human-in-Loop Highlight

The scary-sounding operation on this connector is not the one that stops. Revoking a buyer's access sounds final and is not: Grant Order Access puts it straight back, so an agent responding to a chargeback signal can act now and be corrected later. The operation that stops is the friendly one. Reset Order Download Restrictions clears an order's download attempt count and expiry, and there is no way to un-give a download. Those caps exist because the product is a file, and the request that arrives is identical in both directions: a customer who reinstalled a laptop and a link being passed around a forum both write in saying they ran out of downloads. The agent gathers everything that can be gathered, the order, the purchase date, the buyer's other orders under that email, the licenses issued against it and whether any of them sit on a refunded order, then posts to the support owner: "Order 9931, buyer [email protected], download limit reached, five attempts against a three-attempt cap, two other orders under this email. Reset the counter, or resend the delivery email to the address on file instead?" The owner picks. The agent does the rest.

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

55 actions

Products

8
  • List Products Returns a page of products in the account, and doubles as the cheapest proof that the connection works.
  • Search Products Finds products by name, for workflows that know what something is called but not its id.
  • Look Up Product By Shopify Variant Resolves a Shopify variant id to the SendOwl product attached to it, which is how an order taken on Shopify becomes something to fulfill here.
  • Get Product Returns one product with its price, type, attachment detail, drip items and its buy and sales page links.
  • Create Product Creates a product of any of the supported types, uploading the file for digital and software products in the same call.
  • Update Product Changes writable fields on a product, and replaces the attached file when a new one is supplied.
  • Delete Product Permanently removes a product. Buyers holding orders for it lose access, so this belongs in reviewed cleanup rather than routine hygiene.
  • Issue Product Order Creates a completed order for one product without taking payment, delivering the file and the license immediately. This is the fulfill-from-elsewhere primitive the whole integration is built around.

Bundles

8
  • List Bundles Returns a page of bundles with the product ids each one contains.
  • Search Bundles Finds bundles by name when the workflow does not hold the id.
  • Look Up Bundle By Shopify Variant Resolves a Shopify variant id to the bundle attached to it.
  • Get Bundle Returns one bundle with its price, its component products and its buy and sales page links.
  • Create Bundle Creates a bundle of existing products sold at one price, which is also how several files are delivered together without zipping them.
  • Update Bundle Changes a bundle. The product list replaces the contents rather than adding to them, so read the bundle first and send the whole list.
  • Delete Bundle Permanently removes a bundle while leaving its component products alone.
  • Issue Bundle Order Creates a completed order for a bundle without taking payment, delivering every product in it at once. The way to fulfill a multi-item purchase.

Subscription Products

7
  • List Subscriptions Returns the recurring offers the account sells, rather than the individual buyers subscribed to them.
  • Search Subscriptions Finds a subscription offer by name.
  • Get Subscription Returns one offer with its trial terms, recurring price, frequency, granted products and drip items.
  • Create Subscription Creates a recurring offer with an optional trial, granting either the whole account or a named subset of products.
  • Update Subscription Changes an offer. New terms apply to new signups, while existing buyers keep what they agreed to.
  • Delete Subscription Removes the offer so nobody new can subscribe. It does not cancel anyone's existing subscription.
  • Issue Subscription Order Grants a buyer access against a subscription offer without SendOwl collecting the recurring charge, which leaves the billing responsibility with the workflow that issued it.

Orders

12
  • List Orders Returns orders filtered by creation window, update time, state, product, bundle, subscription or affiliate. The update filter is what an incremental sync is built on, because it catches later changes such as refunds.
  • Search Orders Searches orders across buyer and giftee details, business name and gateway transaction id in one query, which is how a payment in your gateway is traced back to the order it paid for.
  • Find Orders By Buyer Email Returns every order under an exact buyer email, the reliable way to pull one customer's purchase history for a support conversation.
  • Get Order Returns one order in full: buyer details, settled amounts and fees, cart contents, refunds, custom checkout answers and the time-limited download links.
  • Update Order Corrects the fields SendOwl allows to be changed after the fact, including a mistyped buyer email and the shipping address.
  • Refund Order Refunds an order in full or in part at the gateway, optionally cancelling the subscription behind it and revoking access. The result carries a warning when the money went back but the subscription did not stop, so workflows read it rather than trusting the status.
  • Cancel Order Subscription Stops the recurring billing on a subscription order at the gateway. It does not revoke access on its own.
  • Resend Order Email Sends the delivery notification, the receipts, or both again to the buyer's address on file. The safe half of the lost-download queue, because it can only reach the buyer.
  • Reset Order Download Restrictions Resets the download attempt count and expiry back to the product or account settings. There is no way to reverse a download that has already happened, which is why this page gates it.
  • Override Order Country Corrects the buyer country recorded on an order, which is what determines place of supply for tax.
  • Grant Order Access Restores access to a previously revoked order, including any linked membership.
  • Revoke Order Access Cuts off access to an order's files and linked membership immediately. Reversible, which is what makes it safe for an agent to act on a chargeback signal without waiting.

Discounts

12
  • List Discounts Returns the account's discounts, with the codes and product limits living on their own routes.
  • Get Discount Returns one discount with its amount, usage limit, minimum cart value and expiry.
  • Search Discounts By Code Turns a code a customer quoted into the discount record behind it.
  • Create Discount Creates a percentage or fixed-amount discount, optionally generating a batch of single-use codes in the same call.
  • Update Discount Changes a discount's amount, limits or expiry, and is also how extra single-use codes are added to an existing batch.
  • Delete Discount Permanently removes a discount and every code belonging to it, so anything already handed out stops working.
  • List Discount Codes Reads back the individual codes in a batch, which is how generated codes reach the campaign that hands them out.
  • Add Discount Codes Attaches codes of your own choosing to a discount, for codes that must match something printed or issued elsewhere.
  • Delete Discount Code Retires one leaked code while leaving the discount and the rest of its batch working.
  • List Discount Products Returns the products and bundles a discount is restricted to. An empty result means the discount is unrestricted, not that it applies to nothing.
  • Add Discount Product Restricts a discount to one more product or bundle. The first call narrows it from the whole catalog to a single item, so add the rest before advertising the code.
  • Remove Discount Product Lifts one restriction. Removing the last one widens the discount to the whole catalog rather than disabling it.

Licenses

4
  • List Order Licenses Returns the keys allocated to one order, with the product each belongs to and whether the order was refunded. This is how a fulfillment workflow reads back the key a buyer was just given.
  • List Product Licenses Returns the keys held against a product, allocated and unallocated. Counting the unallocated rows is how a workflow spots a pool running low before it stalls sales.
  • Add Product Licenses Uploads a batch of keys for future orders. Duplicates are skipped rather than refused, so workflows check the rejected list rather than the status.
  • Check License Key Validates a key against a product and reports whether it was issued, which order holds it and whether that order was refunded. Running this through a flow is how your shipped application asks the question without carrying your account credentials.

Drip Content

4
  • Add Drip Item To Product Schedules a product or bundle for release a set time after a buyer orders a drip product. Existing orders are updated too, so a new lesson reaches everyone already enrolled.
  • Add Drip Item To Subscription Schedules a release against a subscription, so new material reaches current subscribers on their own timeline rather than all at once.
  • Update Drip Item Changes when an item is released or which item it releases. The change reaches every existing order, so shortening a delay can publish content immediately to people who were still waiting.
  • Delete Drip Item Removes a scheduled release. This also reaches existing orders, so buyers waiting for the item never receive it and buyers who have it lose it.

Frequently Asked Questions

What can FlowRunner do with SendOwl?

FlowRunner agents can run List Products, Search Products, and Look Up Product By Shopify Variant in SendOwl, plus 52 more actions.

Does connecting SendOwl to FlowRunner require OAuth?

No. SendOwl connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can SendOwl trigger a FlowRunner workflow automatically?

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

Start building with SendOwl

Free plan, no card required. Connect in minutes.