Resources · Make integration

Printavo Make integrationAutomate Printavo with Make.

Can Make take the repetitive clicks out of Printavo? The Printavo Make integration gives you 49 modules, 10 of them triggers, covering orders, customers, payments and tasks. This page walks you through the connection, a first scenario and every module.

Try the Printavo integration on Make See the 49 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Printavo Make integration automate?

The Printavo Make integration links your Printavo account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single brick that watches, creates, reads or changes something. Printavo brings 49 of those bricks, so orders, customers, inquiries and payments can move between Printavo and your other apps without copy and paste.

Every new order gets its follow-up. Watch Orders spots each order created in Printavo, and Create a Task adds the matching to-do so nobody has to remember it. The same pattern works with Watch Inquiries when a request comes in before any order exists.

Payments land where finance looks. Watch Payments picks up each new payment, and a module from your accounting or messaging app records it or tells the right person. When the amount needs checking first, Get an Order pulls the full order into the scenario.

Customer records stay in sync. A lead captured in a form or a CRM becomes a Printavo customer with Create a Customer, and Search Customers checks beforehand that the person is not already there, which avoids duplicates.

Know the limits before you start. All 10 triggers are scheduled, so Make checks Printavo on a timer instead of being called the moment something happens. Make also flags its Printavo documentation as AI-generated and asks you to verify important details with Printavo. For anything the 49 modules skip, Make an API Call reaches the rest of the API with the same connection.

New to the editor? The Make training covers the basics, n8n vs Make helps if you are weighing both tools, and Make troubleshooting is there when a run fails.

Connect

How do you connect Printavo to Make?

01
Add a Printavo module
Log in to Make, open a scenario and add any Printavo module. In the module panel, click Create a connection. A connection is your Printavo account linked to Make once, then reused by every Printavo module you add later.
02
Name the connection
The Connection name field is optional, but a clear label such as the account owner or the shop helps a lot once several people share the same Make team and more than one Printavo account shows up in the list.
03
Paste your credentials
Enter the authentication details you copied from your Printavo account, or follow the instructions Make shows on screen. You need an active Printavo account and an API key before you start. Save, and the connection appears in the module.

First scenario

Your first scenario: a task for every new Printavo order

GoalWhen a new order is created in Printavo, Make adds a Printavo task so the follow-up is never forgotten.

01
Create the scenario
From the Scenarios page, create a new scenario and click the big + to add the first module. This first module is the one that starts everything.
02
Pick Watch Orders
Search for Printavo, choose Watch Orders and click Create a connection if you have not linked your account yet. Then fill the fields Make shows for the module.
03
Add Create a Task
Click the + to the right of Watch Orders and pick Printavo Create a Task. Map data from the order into the task fields, so each task points to the order that created it.
04
Test with Run once
Click Run once. Make runs the scenario one time, and you can open each module to read the bundles it received: one bundle per order, one item passing from a module to the next.
05
Schedule and switch on
Open the clock on the first module. A new scenario checks every 15 minutes by default; on the Free plan that is also the shortest interval. Pick your timing, then switch the scenario on.

Triggers

What can start a Printavo scenario?

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

Printavo1Watch Customers

Watch Customers

Scheduled trigger

In Make“Triggers when a new customer is created.”

Each customer added to Printavo can kick off a scenario, so the new contact reaches your mailing list, CRM or welcome email without anyone retyping the details.

How it fires

scheduled. Make checks Printavo on the scenario's schedule, every 15 minutes unless you change it, and collects the customers created since the last check.

When to use it

your team creates customers directly in Printavo and other tools need to know about them.

Watch out

it reacts to new customers only; edits to an existing record do not start the scenario.

Printavo2Watch Expenses

Watch Expenses

Scheduled trigger

In Make“Triggers when a new expense is created.”

Spending logged in Printavo can flow straight into a spreadsheet or an accounting tool, which keeps your cost tracking in one place instead of two.

How it fires

scheduled. On every run of the scenario, Make asks Printavo for expenses created since the previous check.

When to use it

someone records supplier costs in Printavo and your bookkeeper works from another app.

Watch out

each expense found becomes its own bundle, and every module after the trigger spends one operation per bundle, which counts against your plan.

Printavo3Watch Inquiries

Watch Inquiries

Scheduled trigger

In Make“Triggers when a new inquiry is created.”

Fresh inquiries become to-dos elsewhere at the next check: a message to sales, a row in a lead sheet or a customer record prepared ahead of the quote.

How it fires

scheduled. Make polls Printavo at the interval set on the scenario and returns each inquiry created since the last poll.

When to use it

requests arrive in Printavo and you want a person notified before the lead goes cold.

Watch out

with the default schedule, an inquiry can wait up to one interval before Make sees it; shorten the interval on a paid plan if speed matters.

Printavo4Watch Orders

Watch Orders

Scheduled trigger

In Make“Triggers when a new order is created.”

This is the trigger most Printavo scenarios start from: each new order enters Make as a bundle you can turn into tasks, messages or records in other tools.

How it fires

scheduled. Make looks for orders created since its last check, at the rhythm of the scenario's clock.

When to use it

a new order should always cause the same next steps, like a task, a chat message or a line in a production sheet.

Watch out

it only sees new orders; to follow changes on existing ones, Watch Update Orders is the right trigger.

Printavo5Watch Order Status

Watch Order Status

Scheduled trigger

In Make“Triggers when a new order status is created.”

Your list of order statuses can be mirrored elsewhere, so a reporting sheet or a dashboard keeps the same labels your Printavo team uses.

How it fires

scheduled. On each scenario run, Make checks Printavo for statuses created since the last time it asked.

When to use it

someone adds a new stage to your order workflow and other tools must learn that label.

Watch out

Make describes it as firing when a new order status is created, which is not the same as an order moving to another status. For order changes, use Watch Update Orders.

Printavo6Watch Payments

Watch Payments

Scheduled trigger

In Make“Triggers when a new payment is created.”

Money received shows up in Make as soon as the next check runs, which lets you thank the customer, alert finance or update a cash sheet without logging in to Printavo.

How it fires

scheduled. Make queries Printavo on the scenario's timer and returns the payments created since the previous run.

When to use it

a payment should trigger a receipt email or a note in your accounting tool.

Watch out

when your message also needs the order behind the payment, add Get an Order after it.

Printavo7Watch Payment Terms

Watch Payment Terms

Scheduled trigger

In Make“Triggers when a new payment term is created.”

New payment terms created in Printavo can be copied to your billing or accounting setup, so both systems offer customers the same conditions.

How it fires

scheduled. The scenario's schedule decides when Make asks Printavo for terms added since the last check.

When to use it

finance defines a new term in Printavo and another tool needs the same option.

Watch out

terms rarely change, so a scenario built on this trigger often finds nothing; each empty check still runs the trigger, so keep an eye on your plan's operations.

Printavo8Watch Tasks

Watch Tasks

Scheduled trigger

In Make“Triggers when a new task is created.”

Tasks created in Printavo can reach the tool your team actually lives in, whether that is a chat channel, a project board or a calendar.

How it fires

scheduled. Make collects tasks created since its last visit, at the interval set on the first module.

When to use it

production staff prefer another app for their to-do list but tasks are born in Printavo.

Watch out

if another scenario of yours creates Printavo tasks with Create a Task, this trigger will pick those up too, so check you are not building a loop between two scenarios.

Printavo9Watch Update Orders

Watch Update Orders

Scheduled trigger

In Make“Triggers when an order is updated.”

Changes to existing orders become events you can act on: a new due date, an edited amount or a status change can all be passed on to the people who care.

How it fires

scheduled. Make checks Printavo on the scenario's rhythm and returns orders updated since the last run.

When to use it

customers or staff need to hear about order changes without watching Printavo all day.

Watch out

if the scenario itself uses Update an Order on the same orders, it can wake itself up again; add a filter so it only reacts to the changes you care about.

Printavo10Watch Users

Watch Users

Scheduled trigger

In Make“Triggers when a new user is created.”

Onboarding gets easier when each new Printavo user is spotted automatically, ready to be added to a chat workspace, a shared drive or an internal directory.

How it fires

scheduled. Make asks Printavo, on each run of the scenario, which users were created since the last check.

When to use it

an admin invites staff to Printavo and the same person needs accounts in other tools.

Watch out

it covers new users only; someone leaving the team does not start the scenario, so offboarding still needs another route.

Modules

What can Printavo do inside a scenario?

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

Printavo1

Create a Customer

Action

In Make“Creates a new customer.”

A lead from a form, an ecommerce store or a CRM becomes a real Printavo customer, ready for its first order, without anyone typing the name and email twice.

When to use it

right after a trigger in another app announces a new contact.

Watch out

run Search Customers first, or you will end up with duplicate customers each time the same person comes back.

Printavo2

Create an Expense

Action

In Make“Creates a new expense.”

Costs recorded somewhere else, like a receipt app or a supplier email, get logged in Printavo automatically so margins there stay accurate.

When to use it

your purchases are tracked in another tool and Printavo should hold a copy of each expense.

Watch out

test with Run once on a single item first, since every bundle that reaches this module creates one more expense.

Printavo3

Create an Inquiry

Action

In Make“Creates a new inquiry.”

Quote requests from your website form or a chat tool land in Printavo as inquiries, which gives sales a single inbox for new demand.

When to use it

the request is captured outside Printavo and you want it followed up in Printavo.

Watch out

if Watch Inquiries runs in another scenario, the inquiry you create here will start that one too, which is often what you want but worth knowing.

Printavo4

Create an Order

Action

In Make“Creates a new order.”

Orders placed in another channel, an online store for example, appear in Printavo without being keyed in by hand, so production sees them in the usual place.

When to use it

the sale happens in a shop or a form and the work is managed in Printavo.

Watch out

make sure the customer exists first; pairing Search Customers with Create a Customer before this module keeps orders attached to the right person.

Printavo5

Create a Payment

Action

In Make“Creates a new payment.”

Money collected through another tool, a payment processor or a bank feed, gets recorded against Printavo automatically, so the balance there matches reality.

When to use it

a payment app announces a successful charge and Printavo should know about it.

Watch out

map the order carefully from the earlier modules; a payment recorded on the wrong order is harder to spot than a missing one.

Printavo6

Create a Payment Term

Action

In Make“Creates a new payment term.”

Payment conditions defined elsewhere can be added to Printavo without opening its settings, which keeps both systems offering customers the same terms.

When to use it

finance maintains the reference list in a spreadsheet or accounting tool and Printavo must follow.

Watch out

this is a setup change, not daily data, so a scenario that creates terms should usually run from a manual start rather than loop over every bundle.

Printavo7

Create a Task

Action

In Make“Creates a new task.”

Follow-ups stop depending on memory: a task appears in Printavo whenever something in the scenario calls for it, like a new order or a paid invoice.

When to use it

behind Watch Orders or Watch Inquiries, to give the team its next step automatically.

Watch out

map the order or customer into the task text, otherwise the team gets a task with no context.

Printavo8

Delete a Customer

Action

In Make“Deletes a customer.”

Customer records you no longer need disappear from Printavo as part of a cleanup flow, for instance when a contact is removed from your main CRM.

When to use it

another system is the master list and Printavo should mirror its removals.

Watch out

Make offers no undo for a deletion, so treat it as final; add a filter before this module and test with Run once on a throwaway record.

Printavo9

Delete an Expense

Action

In Make“Deletes an expense.”

Expenses entered by mistake or cancelled in your accounting tool can be removed from Printavo too, keeping cost reports clean on both sides.

When to use it

a refund or cancellation elsewhere means the matching Printavo expense should go.

Watch out

treat the deletion as final, since nothing in Make restores it; make sure the expense you point it at really is the one to remove.

Printavo10

Delete an Inquiry

Action

In Make“Deletes an inquiry.”

Spam requests or duplicate inquiries get cleared out automatically, so sales only works through genuine leads.

When to use it

a filter in your scenario has identified an inquiry as junk or as a copy of one already handled.

Watch out

the filter does the real work here; if its rule is too loose, real prospects vanish, so check a few runs by hand first.

Printavo11

Delete an Order

Action

In Make“Deletes a specific order.”

An order cancelled in the channel where it was placed can be removed from Printavo as well, so production never starts on something nobody wants anymore.

When to use it

your store or form tool reports a cancellation and Printavo must follow.

Watch out

treat the deletion as final; Update an Order is the gentler option if you only need to mark it, and it keeps the history.

Printavo12

Delete a Payment

Action

In Make“Deletes a payment.”

Payments recorded twice or reversed at the processor can be taken out of Printavo, which keeps order balances honest.

When to use it

a chargeback or refund event in your payment tool should cancel the matching record.

Watch out

use Get a Payment or List Payments first to confirm you have the right one; a wrong deletion changes what the customer appears to owe.

Printavo13

Delete a Task

Action

In Make“Deletes a task.”

Tasks that no longer make sense, because an order was cancelled or a job was merged, can be cleaned away without anyone scrolling through lists.

When to use it

a scenario already knows a task is obsolete, for example right after Delete an Order.

Watch out

removing a task someone was about to work on causes confusion; marking it done with Update a Task is often the gentler option.

Printavo14

Get a Customer

Action

In Make“Gets a customer.”

Full details of one customer arrive in the scenario, useful when an earlier module only gave you a reference and you need the name, email or address.

When to use it

after Watch Orders or Watch Payments, to personalise a message with the customer's real details.

Watch out

it returns one customer; to find someone without knowing which record it is, Search Customers is the right module.

Printavo15

Get an Expense

Action

In Make“Gets an expense.”

One expense is fetched with all its information, handy for checking a cost before copying it to accounting or attaching it to a report.

When to use it

a trigger or a list handed you an expense and you need the complete record before the next step.

Watch out

to go through several expenses at once, List Expenses returns them all as separate bundles.

Printavo16

Get an Inquiry

Action

In Make“Gets an inquiry.”

The full content of one inquiry comes into the scenario, so the message you send to sales or the customer you create carries every detail of the request.

When to use it

you hold an inquiry reference from an earlier module and want the rest.

Watch out

each call is one operation; skip it when the trigger bundle already contains what you need.

Printavo17

Get an Order

Action

In Make“Gets information about a specific order.”

Everything about one specific order lands in the scenario, which turns a bare payment or task into a message that tells the reader exactly which job it concerns.

When to use it

after Watch Payments, to show the order behind the money.

Watch out

you need to know which order to ask for; map it from a previous module rather than typing it by hand.

Printavo18

Get an Order Status

Action

In Make“Gets an order status.”

The details of one order status are returned, so a scenario can display its readable name instead of an internal reference in emails or reports.

When to use it

an order bundle points to a status and you want its label for a customer update.

Watch out

to see every status at once, for a lookup table, List Order Statuses does it in one go.

Printavo19

Get a Payment

Action

In Make“Gets a payment.”

One payment is pulled in with its details, useful for confirming the amount before sending a receipt or updating a finance sheet.

When to use it

a scenario must double check a payment before it acts, for instance before Delete a Payment.

Watch out

Watch Payments already delivers new payments; add this module only when you start from a reference, not from the trigger.

Printavo20

Get a Payment Term

Action

In Make“Gets a payment term.”

The conditions attached to one payment term are fetched, so an invoice email or a reminder can state them clearly.

When to use it

an order carries a term and your message should spell out what it means.

Watch out

terms rarely change, so repeating this call on every run spends operations; List Payment Terms once can be enough.

Printavo21

Get a Task

Action

In Make“Gets a task.”

A single task arrives with its full information, ready to be copied into a project tool or checked before an update.

When to use it

you already know which task matters and need its latest state.

Watch out

fetching a task does not change it; pair it with Update a Task when the goal is to edit.

Printavo22

Get a User

Action

In Make“Gets a user.”

Information about one Printavo user comes back, so a scenario can address the right colleague by name or email when it routes a task or an alert.

When to use it

an order or task points to a user and you want to notify that person directly.

Watch out

for a full team list, List Users is cheaper than one Get a User per person.

Printavo23

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the Printavo API offers that the listed modules skip becomes reachable, using the same connection you already set up.

When to use it

you need a Printavo feature that no listed module covers.

Watch out

you write the request yourself, so read Printavo's own API docs; Make labels its Printavo documentation as AI-generated and asks you to verify important details with Printavo.

Printavo24

Update a Customer

Action

In Make“Updates a customer.”

Changes made to a contact in your CRM or support tool are pushed to the matching Printavo customer, so shipping and billing details never drift apart.

When to use it

another app is where customer data gets edited first.

Watch out

find the right record with Search Customers before updating; a mismatch overwrites someone else's details.

Printavo25

Update an Expense

Action

In Make“Updates an expense.”

Corrections to a cost, such as a new amount or a fixed category, are carried over to Printavo so reports there match your accounting.

When to use it

a bookkeeper adjusts an expense in another tool after it was first recorded.

Watch out

run it on one test expense with Run once and compare the record before and after, so a wrong mapping does not overwrite good numbers.

Printavo26

Update an Inquiry

Action

In Make“Updates an inquiry.”

An inquiry follows the conversation happening elsewhere: new details from an email thread or a chat get written back to the Printavo record.

When to use it

sales talks to prospects in another tool and Printavo should stay current.

Watch out

if Watch Inquiries feeds this same scenario, only new inquiries trigger it, so updates will not loop back.

Printavo27

Update an Order

Action

In Make“Updates an existing order.”

Existing orders change without manual edits: a due date from the customer portal, a note from support or a status from your shipping tool reaches Printavo on its own.

When to use it

an outside event should move an order along.

Watch out

Watch Update Orders sees these edits too, so if both sit in scenarios that feed each other, add a filter to stop the ping pong.

Printavo28

Update a Payment

Action

In Make“Updates a payment.”

A recorded payment gets corrected automatically, for example when the processor settles a different amount or adds a reference.

When to use it

your payment tool sends a change after the payment was already logged in Printavo.

Watch out

an edited amount rewrites a figure your team relies on, so test on a sample payment with Run once first.

Printavo29

Update a Payment Term

Action

In Make“Updates a payment term.”

When finance rewrites the conditions of a term in its reference file, the same wording reaches Printavo without a trip to the settings page.

When to use it

another system owns the list of payment terms and Printavo mirrors it.

Watch out

changing a term can affect every order that uses it, so check which orders rely on it before the scenario runs.

Printavo30

Update a Task

Action

In Make“Updates a task.”

Progress made outside Printavo, a job ticked off in a project board or a message in chat, is reflected on the Printavo task automatically.

When to use it

staff complete work in another tool and managers watch Printavo.

Watch out

map the right task from earlier modules; Get a Task or List Tasks helps you find it.

Printavo31

List Expenses

In Make“Lists all expenses.”

All expenses come back as separate bundles, one per expense, ready for a spreadsheet export or a total in a later module.

When to use it

you want a full snapshot rather than only the new items Watch Expenses picks up.

Watch out

every bundle flows through the next modules and each one costs operations, so an aggregator or a filter keeps a long list under control.

Printavo32

List Inquiries

In Make“Lists all inquiries.”

Every inquiry is returned, which makes it simple to rebuild a lead sheet or review the requests still open.

When to use it

a one-off import, or a check on inquiries that never became orders.

Watch out

the module can return zero, one or many bundles; plan the next step for each case, including an empty result.

Printavo33

List Order Statuses

In Make“Lists order statuses.”

Your status list, the stages an order goes through, is returned in full so another tool can use the same vocabulary.

When to use it

building a report or a dropdown in another app that must match Printavo stages.

Watch out

this lists statuses, not orders; to find orders in a given status, look at Search Orders.

Printavo34

List Payments

In Make“Lists all payments.”

The whole payment history arrives bundle by bundle, useful for reconciling Printavo against a bank export or an accounting ledger.

When to use it

an audit or a first sync, when Watch Payments would only show new items.

Watch out

a long history means many operations; filter early in the scenario to keep only the payments you need.

Printavo35

List Payment Terms

In Make“Lists all payment terms.”

Every payment term defined in Printavo is returned, a quick way to copy them to accounting or check they match your contracts.

When to use it

setting up another tool that needs the same terms as Printavo.

Watch out

the result rarely changes, so this suits a scenario you start by hand more than one that runs on a schedule.

Printavo36

List Tasks

In Make“Lists all tasks.”

All tasks come back as bundles, which lets you build a digest for managers or spot tasks nobody picked up.

When to use it

you need the whole picture, not just tasks created since the last check.

Watch out

add a filter or an aggregator after it; sending one message per task quickly floods a channel.

Printavo37

List Users

In Make“Lists all users.”

The full team roster in Printavo is returned, handy for matching staff to accounts in other tools or auditing who has access.

When to use it

comparing Printavo users with your HR list or chat workspace.

Watch out

treat the output with care; user details are personal data and should only reach tools that need them.

Printavo38

Search Customers

In Make“Searches for customers or lists them all.”

Finding a customer before acting on it saves you from duplicates: this search returns the matching records, or all of them if you leave it open.

When to use it

just before Create a Customer or Create an Order, to reuse an existing record.

Watch out

zero results is a normal outcome; add a router or filter so the scenario creates the customer only when the search comes back empty.

Printavo39

Search Orders

In Make“Searches for orders or lists them all.”

Specific orders can be located from inside a scenario, or listed in full, so updates and reports target the right jobs.

When to use it

an email or a payment mentions an order and you need to find it in Printavo.

Watch out

several orders may match; each becomes its own bundle, so a following Update an Order would run on every one of them.

Need help

Need help automating Printavo with Make?

A person reads every message.

FAQ

Printavo and Make: frequent questions

01Is the Printavo Make integration free?

Yes, Printavo is a standard app in Make, available from the Free plan. That plan gives you 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes and allows files up to 5 MB with 512 MB of data transfer. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits each month. Your Printavo subscription is separate and handled by Printavo.

02What do you need to connect Printavo to Make?

You need an active Printavo account and an API key from it. In Make, add any Printavo module, click Create a connection, optionally give it a name, then enter the credentials copied from Printavo or follow the on screen instructions. Once saved, the same connection serves every Printavo module in your scenarios, so you only do this once per account. If the connection fails, check that the account is active and that the key was copied in full.

03Do Printavo triggers in Make fire instantly?

No. All 10 Printavo triggers are scheduled: Make checks Printavo on the scenario's schedule and processes whatever was created or updated since the last check. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Paid plans can go down to 1 minute. There is no instant trigger for Printavo in Make, so plan for a short delay between an event in Printavo and the scenario running.

04What if a Printavo module you need is missing in Make?

Use Make an API Call. It sends any request the Printavo API accepts, with the connection you already created, so you are not limited to the 49 listed modules. You will need to read Printavo's API documentation to build the request. Keep in mind that Make marks its Printavo documentation as AI-generated and asks you to check important details with Printavo directly, so test each request with Run once before relying on it.

05Should you use Make or n8n for Printavo?

It depends on the tool your team already knows. Make offers Printavo with 49 ready modules, including 10 scheduled triggers and Make an API Call for anything else, all available from the Free plan. The same app often has an n8n node as well. The fair test is practical: check that the modules you need exist in the tool you prefer, build one small scenario, and keep the tool whose editor your team is comfortable maintaining.

Add a Printavo module

Name the connection

Paste your credentials

Create the scenario

Pick Watch Orders

Add Create a Task

Test with Run once

Schedule and switch on

Need help automating Printavo with Make?