Resources · Make integration

SendOwl Make integrationAutomate SendOwl with Make.

Every sale in your SendOwl store can start work somewhere else. The SendOwl Make integration gives you 17 modules: 4 instant triggers and 13 actions. This guide is for sellers of digital products who want orders, refunds and catalog changes handled without code, starting with one working scenario.

Try the SendOwl integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the SendOwl Make integration do for your store?

The SendOwl Make integration links your SendOwl account to Make, a visual tool where you chain apps together without writing code. SendOwl tells Make the moment a payment, refund, subscription change or completed order happens, and Make can create, read, change or delete your products, bundles and discounts in return.

Reward buyers right after checkout. Watch Order Completed fires when an order is done, and Create a Discount prepares a coupon you can hand to that customer for their next purchase. A course creator can turn every first sale into a second one this way.

Keep an eye on money going back out. Watch New Refund pairs well with a spreadsheet or a team chat from another app, so nobody has to open the SendOwl dashboard to notice that a customer asked for their money back.

Run the catalog from somewhere else. Create a Product, Update a Product and the bundle modules let a planning table in another tool drive what SendOwl sells. The Airtable Make integration is a common starting point for that kind of list.

What Make will not do: the documentation lists no search module for SendOwl, so the Get modules need an ID you already have. For anything the 17 modules skip, Make an API Call reaches the rest of the SendOwl API with the same account link. SendOwl may also have an n8n node; the n8n vs Make comparison helps you pick a tool, and the Make training covers the editor from zero.

Connect

How do you connect SendOwl to Make?

  1. 01

    Copy your API key and secret

    In SendOwl, open the Settings section of your dashboard, then click the API link under Advanced. Copy the API key and the API secret shown there. The API has to be switched on in your SendOwl account for this page to show both values.

  2. 02

    Add a SendOwl module in Make

    Inside a scenario (the automation you build in Make), add any SendOwl module and click Create a connection. A connection is your SendOwl account linked to Make once, then reused by every SendOwl module you add later.

  3. 03

    Paste the credentials and save

    Give the connection a clear name in Connection name if you run more than one store; that field is optional. Paste the key and the secret you copied, confirm, and Make starts listing your SendOwl data in the module fields.

First scenario

Your first scenario: a thank-you coupon after each completed order

GoalWhen an order is completed in SendOwl, Make creates a discount the buyer can use on the next purchase.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. Every module is one brick: a trigger, an action or a search.

  2. 02

    Pick Watch Order Completed

    Search for SendOwl, choose Watch Order Completed, click Create a webhook, then link your account with Create a connection. This trigger is instant: SendOwl calls Make as soon as an order is done.

  3. 03

    Add Create a Discount

    Click the + on the right of the trigger and pick Create a Discount. Fill its fields, and map values from the order where it helps, so each coupon can be traced back to the sale that produced it.

  4. 04

    Test with Run once

    Click Run once, then let an order complete in SendOwl. Make shows the bundle each module received: a bundle is one item, here one order, passed from a module to the next.

  5. 05

    Switch it on

    If the discount looks right in SendOwl, switch the scenario on. From then on, each completed order runs it once, and every module that runs counts as one operation on your Make plan.

Triggers

What can start a SendOwl scenario?

4 modules start a scenario when something happens in SendOwl. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by SendOwl as soon as it happens.

SendOwl1Watch New Payment

Watch New Payment

Instant trigger

In Make“Triggers when a payment is made to order in SendOwl.”

Starts your scenario whenever money lands on an order in SendOwl, so the payment itself becomes the signal for whatever comes next, like a row in your bookkeeping sheet or a message to the person who handles invoices.

How it fires
instant, SendOwl calls Make through a webhook as soon as the payment is made, with no waiting for a polling interval.
When to use it
when what matters to you is the cash itself rather than the delivery of the product.
Watch out
Watch New Payment and Watch Order Completed describe two different moments of a sale, so choose the one that matches the moment your process cares about.
SendOwl2Watch New Refund

Watch New Refund

Instant trigger

In Make“Triggers when a refund is issued.”

Tells you the moment a refund goes out, which lets you react while the customer is still fresh in mind: flag the account in your CRM, update a revenue sheet, or warn support before the angry email arrives.

How it fires
instant, SendOwl sends the refund to Make through a webhook as soon as it is issued.
When to use it
any store where refunds need a human look, such as a course where a refund should also end access elsewhere.
Watch out
the scenario has to be switched on to receive anything, so leave it active once Run once has shown a clean refund bundle.
SendOwl3Watch New Subscription

Watch New Subscription

Instant trigger

In Make“Triggers when a subscription order reaches complete or cancelled state in SendOwl.”

Follows your recurring customers: the scenario starts when a subscription order reaches the complete state or the cancelled state, so both a new member and a lost member reach Make.

How it fires
instant, SendOwl notifies Make by webhook as soon as the subscription changes to one of those two states.
When to use it
a membership or a paid newsletter where access in another tool must follow the subscription.
Watch out
both outcomes arrive through the same trigger, so add a filter after it and send completions and cancellations down different paths.
SendOwl4Watch Order Completed

Watch Order Completed

Instant trigger

In Make“Triggers when an order has been completed.”

Hands Make every order the moment SendOwl marks it as completed, which is the cleanest starting point for anything that follows a sale: a welcome sequence, a coupon, a line in a sales table.

How it fires
instant, SendOwl calls Make through a webhook as soon as the order is completed.
When to use it
the default choice when you want one run per finished sale, and the trigger used in the first scenario above.
Watch out
it only fires once an order is completed, so for a signal at the moment money comes in, Watch New Payment is the closer fit.
Modules

What can Make do inside SendOwl?

SendOwl gives you 13 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

SendOwl1

Create a Bundle

Action

In Make“Creates a new bundle.”

Builds a new bundle in SendOwl, a package that sells several of your products together, without you opening the store to assemble it by hand.

When to use it
a launch planned in a table somewhere else, where a new row should turn into a ready bundle.
Watch out
a SendOwl bundle is not a Make bundle (one item flowing between modules), so keep the two apart when you read the results.
SendOwl2

Create a Discount

Action

In Make“Creates a new discount.”

Generates a fresh discount in SendOwl, so a coupon can appear exactly when an event in your process calls for it instead of being prepared ahead in bulk.

When to use it
right after Watch Order Completed, to give a returning buyer a reason to come back, or when a partner signs up in another app.
Watch out
each run creates one more discount, so test with Run once before switching on a busy store.
SendOwl3

Create a Product

Action

In Make“Creates a new Product.”

Adds a product to your SendOwl catalog from data that lives elsewhere, which saves retyping product details your offer already holds in another tool.

When to use it
a creator who drafts new ebooks or templates in a spreadsheet and wants them listed once the row is marked ready.
Watch out
Update, Get and Delete all work from the product ID, so store that ID as soon as the product exists.
SendOwl4

Delete a Bundle

Action

In Make“Deletes a bundle by ID.”

Removes a bundle from SendOwl by its ID, which keeps the store tidy once a package has done its job and should no longer be sold.

When to use it
the end of a limited offer tracked in another app, when the offer's row switches to closed.
Watch out
no SendOwl module brings a bundle back, so run Get a Bundle first if you want a record of what you removed.
SendOwl5

Delete a Discount

Action

In Make“Deletes a discount by ID.”

Retires a discount by its ID, so a code that should no longer work stops working without anyone remembering to do it in the dashboard.

When to use it
when a refund arrives through Watch New Refund and the coupon tied to that sale should disappear with it.
Watch out
the module needs the exact ID; since there is no search module, store that ID when the discount is created.
SendOwl6

Delete a Product

Action

In Make“Deletes a Product by ID.”

Takes a product out of SendOwl by its ID, the step to use when an item is discontinued in the place where you manage your offer.

When to use it
a product retired in your planning table that must leave the store at the same moment.
Watch out
no SendOwl module restores a deleted product, so for one that may come back, Update a Product is often the gentler choice.
SendOwl7

Get a Bundle

Action

In Make“Returns a specified bundle.”

Reads one bundle from SendOwl and passes its details to the next module, so you can copy what a package contains into a report or a message.

When to use it
before changing or deleting a bundle, to keep a snapshot of how it looked.
Watch out
it returns a single bundle you name by ID; it does not list all of them.
SendOwl8

Get a Discount

Action

In Make“Return a specified discount.”

Pulls the details of one discount out of SendOwl, handy when a later module needs to show or check the code instead of guessing it.

When to use it
after Create a Discount in another scenario, when you only kept the ID and now want to send the coupon to a customer.
Watch out
without a search module, this only works with an ID stored earlier.
SendOwl9

Get a Product

Action

In Make“Returns a specified product.”

Fetches one product from your SendOwl catalog so its information can travel on, to a table, a newsletter tool or a support note.

When to use it
to enrich a message with product details when all you hold is the product ID.
Watch out
each call costs one operation, so avoid placing it in a path that runs for every item of a long list when one read is enough.
SendOwl10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the SendOwl API to your scenario, using the same connection as the other modules, for the cases the other SendOwl modules do not cover.

When to use it
when you need something like a list of items and no listed module returns it.
Watch out
you write the request yourself, so read the SendOwl API documentation first and test with Run once.
SendOwl11

Update a Bundle

Action

In Make“Updates a bundle by ID.”

Changes an existing bundle by its ID, so the package in the store keeps up with the plan you edit in another place.

When to use it
a bundle whose content you adjust in a planning table, with SendOwl following along.
Watch out
point it at the right ID; updating the wrong bundle changes a live offer that buyers can see.
SendOwl12

Update a Discount

Action

In Make“Updates a discount by ID.”

Edits a discount that already exists, letting a promotion stretch or shrink without creating a new code that customers would have to learn.

When to use it
when a campaign gets extended in your marketing calendar and the same coupon should keep working.
Watch out
buyers who already hold the code see the change too, so edit with care on a code that is out in the wild.
SendOwl13

Update a Product

Action

In Make“Updates a product by ID.”

Rewrites the details of a product by its ID, which keeps SendOwl in line with the source you trust for your product details.

When to use it
a product change decided in a shared sheet that must reach the store without a manual copy.
Watch out
the module changes a product buyers can see right away, so run it once on a test product before letting a whole sheet flow through it.
Need help

Need help automating SendOwl with Make?

A person reads every message.

FAQ

SendOwl and Make: common questions

01Is the SendOwl Make integration free?
Yes, SendOwl is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits and count usage in credits per month. Your SendOwl subscription is separate and is not covered by Make.
02What do you need to connect SendOwl to Make?
You need an active SendOwl account with the API enabled, plus its API key and API secret. In SendOwl, open Settings, then the API link in the Advanced section, and copy both values. In Make, add a SendOwl module, click Create a connection, and paste them. For a trigger, click Create a webhook first. The connection is then shared by every SendOwl module in your scenarios, so you only do this once per account.
03Do the SendOwl triggers in Make react in real time?
Yes, all 4 SendOwl triggers are instant. SendOwl calls Make through a webhook as soon as a payment, a refund, a subscription change or a completed order happens, and the scenario starts right away instead of waiting for a polling interval. This is why adding a trigger asks you to create a webhook before the connection. The 13 actions have no schedule of their own: they run when a trigger or an earlier module reaches them.
04What if a SendOwl module you need is missing in Make?
It depends on the need, but the Make an API Call module is the usual answer. It sends any request to the SendOwl API with the connection you already set up, which covers actions the 17 listed modules leave out, such as a list where only single-item Get modules exist. You write the request yourself, so check the SendOwl API documentation. The Make documentation for SendOwl lists no specific limits.
05Should you use Make or n8n for SendOwl?
It depends on your criteria rather than on SendOwl itself. On Make, SendOwl comes with 17 modules, including 4 instant triggers, a visual editor and a Free plan to start. SendOwl often has an n8n node as well, so both tools can usually handle it. Compare the modules each one offers for your exact case, then how you prefer to build and pay. The comparison page linked above lays out the differences.
Same platform

Other docs you might need on this stack.

Browse all integrations