Resources · Make integration

Printful Make integrationAutomate Printful with Make.

What if your Printful orders moved on their own? The Printful Make integration gives you 8 modules: 3 triggers that watch orders and 5 actions that create, read, update or cancel them. This page shows how to link your account and build your first scenario.

Try the Printful integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Printful Make integration do for you?

The Printful Make integration links your Printful store to Make, a no-code tool where you build a scenario: a chain of steps that runs by itself. Each step is a module, one brick that watches, creates or changes something. Here, every module works on the same thing: your Printful orders.

Orders created from somewhere else. A sale lands in a shop, a form or a sheet that Printful does not read. With Create an Order, Make builds the matching Printful order from that data, so nobody retypes addresses.

Shipping news passed along. Watch Fulfilled Orders spots orders whose items have all shipped. Add Get an Order to pull the full details, then send them to your support inbox or CRM.

Cancellations kept in sync. Watch Canceled Orders reports every canceled order, so your stock sheet or accounting tool can follow. When the cancel request starts outside Printful, Cancel an Order handles pending or draft orders.

What the page cannot promise: the 8 modules only cover orders. For anything else in the Printful API, Make an API Call is the way in. Make also notes that its Printful documentation is AI-generated from Printful's own docs, so double-check anything critical. Weighing another tool? The n8n vs Make comparison lays out the differences, and the Make pricing guide explains how operations are counted. Stuck on a failing run? Open Make troubleshooting.

Connect

How do you connect Printful to Make?

  1. 01

    Add a Printful module

    In your Make account, open a scenario, add any Printful module and click Create a connection. A connection is your Printful account linked to Make once, then reused by every Printful module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when you run more than one store. Something like the store name is enough to pick the right account later in the list.

  3. 03

    Enter your credentials

    You need an active Printful account and either a private API token or a public app with OAuth credentials. Paste what you copied from Printful, or follow the on-screen steps, and Make saves the connection.

First scenario

Your first scenario: turn a sale into a Printful order

GoalWhen a new sale shows up in the app where your orders land, Make creates the matching order in Printful.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to place the first module. That first module is the app where your sales arrive: a sheet, a form or a shop.

  2. 02

    Set up the starting app

    Pick that app's module that watches new rows or new sales and link its account. Once connected, Make lists the sheets or objects it can read, so you choose from a menu.

  3. 03

    Add Create an Order

    Click the + on the right of the first module, search Printful and choose Create an Order. Map the customer and product data from the first module into the Printful fields Make shows you.

  4. 04

    Test with Run once

    Click Run once and add a test sale. Each module shows the bundles it received, one bundle per item passed along. Check the new order in Printful before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and 15 minutes is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

Which Printful triggers can start a scenario?

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

Printful1Watch Canceled Orders

Watch Canceled Orders

Scheduled trigger

In Make“Watches for new canceled orders.”

This trigger hands your scenario every order that has just been canceled in Printful, so other tools can react without you noticing it first. Each canceled order comes through as its own bundle, one item you can pass to the next module.

How it fires
it is a scheduled trigger. Make checks Printful on the scenario's schedule, not the moment the order is canceled.
When to use it
you want a cancellation to free up a line in your stock sheet or flag a refund to handle in your accounting tool.
Watch out
it only reports cancellations, so pair it with Watch Orders if you also need the orders that stay active.
Printful2Watch Fulfilled Orders

Watch Fulfilled Orders

Scheduled trigger

In Make“Watches for orders which have been fulfilled (all items shipped successfully).”

Here you get the orders Printful has fully shipped, meaning every item left successfully. It is the cleanest signal that a customer's parcel is on its way, which makes it a natural start for follow-up messages.

How it fires
scheduled. Make asks Printful for newly fulfilled orders each time the scenario runs.
When to use it
you want a shipping note in your help desk or a status update in your CRM once everything is out.
Watch out
an order with one item still pending does not count as fulfilled yet, so it will not show up here.
Printful3Watch Orders

Watch Orders

Scheduled trigger

In Make“Watches for new orders.”

This one gives your scenario each new Printful order at the next run. You get a steady feed of fresh orders to log, share or check, without opening the dashboard.

How it fires
scheduled. Make polls Printful at the interval set on the first module, so an order appears at the next run.
When to use it
you log every order in a sheet, or you alert the team channel when a sale lands.
Watch out
if you only care about shipped or canceled orders, pick the dedicated watcher instead of filtering this feed later.
Modules

What can Make do in Printful?

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

Printful1

Cancel an Order

Action

In Make“Cancels a pending or draft order.”

Stops an order in Printful from your scenario, so a cancellation decided in another tool reaches Printful without a manual step.

When to use it
a customer cancels through your support form and the order has not gone to production.
Watch out
it only works on orders still pending or in draft, so an order already in production stays out of reach.
Printful2

Create an Order

Action

In Make“Creates an order.”

Builds a brand new Printful order from data coming out of an earlier module. That is how sales from a channel Printful does not read still end up in production, with no copy and paste in between.

When to use it
orders reach you through a form, a sheet or a shop that has no direct link with Printful.
Watch out
test with Run once first, since every run creates a real order.
Printful3

Get an Order

Action

In Make“Returns information about an order.”

Reads one order and returns the information Printful holds on it, so the following modules have full details to work with. Triggers give you the event; this module fills in the rest when you need it.

When to use it
after Watch Fulfilled Orders, to pass complete order data to your help desk or CRM.
Watch out
it reads a single order per run, so point it at the order the previous module found.
Printful4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Printful API from your scenario, reusing the same connection. Whenever the 8 ready-made modules stop short, this is how you reach any other part of the Printful API.

When to use it
you need something outside orders, and none of the listed modules covers it.
Watch out
you write the request yourself, so keep the Printful API reference open next to Make while you set it up.
Printful5

Update an Order

Action

In Make“Updates an unsubmitted order and optionally submits it for fulfillment.”

Changes an order that has not been submitted yet, and can submit it for fulfillment in the same step. Handy when an order sits as a draft and needs a check before it goes to production.

When to use it
a draft waits for approval, and once it is approved you want it sent out right away.
Watch out
the module is built for unsubmitted orders, so aim it at drafts rather than orders already in production.
Need help

Need help automating Printful with Make?

A person reads every message.

FAQ

Printful and Make: common questions

01Is the Printful Make integration free?
Yes, Printful is a standard app in Make, so it is available from the Free plan. The Free plan lets you keep 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and caps files at 5 MB with 512 MB of data transfer. Every module run counts as one operation on your plan. Paid plans drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Your Printful subscription is separate and depends on Printful's own pricing.
02What do you need to connect Printful to Make?
You need an active Printful account and one of two ways in: a private API token, or a public app with OAuth credentials. With a token, you paste it when Make asks after you click Create a connection. With OAuth, you first create an app from the Apps section of the Printful developer dashboard, enter the callback URI Make expects, then copy the Client ID and Client secret. Naming the connection is optional but handy if you run several stores.
03Do the Printful triggers in Make fire instantly?
No. All 3 Printful triggers are scheduled, and Printful has no instant trigger in Make. Make checks Printful each time the scenario runs, so a new, canceled or fulfilled order shows up at the next check. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan; paid plans go down to 1 minute. If you need a faster reaction on a paid plan, lower the interval on the first module.
04What if the Printful module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Printful API with the connection you already have, so you are not limited to the 8 modules that cover orders. You write the request yourself, which asks for a look at the Printful API reference. Make also warns that its Printful documentation is AI-generated from Printful's docs and may contain mistakes, so verify the details that matter before relying on them.
05Should you use Make or n8n for Printful?
It depends on what you need. On the Make side, you get 8 Printful modules focused on orders: 3 scheduled triggers, 5 actions, and Make an API Call for the rest of the API, all available from the Free plan. n8n often has a node for the same app, so check what it offers for Printful before choosing. Compare the modules each tool gives you for your exact use case, how you connect your account and how each one counts runs on its plans.
Same platform

Other docs you might need on this stack.

Browse all integrations