Resources · Make integration

Print.one Make integrationAutomate Print.one with Make.

Can a new customer in one tool trigger a printed postcard in Print.one? The Print.one Make integration offers 2 action modules, one of which sends a postcard. This guide is for marketers who start from zero in Make: connect your account, then build a first scenario and switch it on.

Try the Print.one integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Print.one Make integration do?

The Print.one Make integration lets Make send a postcard through your Print.one account, with no code. You build a scenario (the automation itself, a chain of modules), where each module is one brick: here, the Print.one step that mails the card. Another app, or a schedule, decides when it runs.

A thank-you card after a first order. An online shop can start the scenario from its store app, then hand the customer data to Send Postcard. Each order becomes one bundle, the Make word for one item passing from a module to the next, and each bundle becomes one card.

A physical touch in a campaign. A marketing team that tracks leads in a form tool can send a card when someone fills in the form, for example after starting from the 123FormBuilder Make integration. The card goes out without anyone opening Print.one.

A request the ready-made module does not cover. The Make API Call module sends an authorized request to Print.one through the same connection, for the cases where Send Postcard is not enough.

Keep the limits in mind. Print.one offers no trigger in Make, so nothing inside Print.one can start a scenario: the start always comes from another app or from the schedule. The documentation also warns that it is AI-generated from Print.one's own docs and may contain mistakes, so check anything important with Print.one. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted.

Connect

How do you connect Print.one to Make?

  1. 01

    Add a Print.one module

    In your scenario, click the +, search for Print.one and pick one of its two modules. Make then asks for a connection, meaning your Print.one account linked to Make once and reused by every Print.one module. Click Create a connection.

  2. 02

    Paste your API key

    Give the connection a name if you like, so you can tell accounts apart later. Then paste the API key that your Print.one account gives you. Without an active Print.one account and that key, Make has nothing to connect to.

  3. 03

    Save and reuse

    Click Save. The connection now appears in the module, and the second Print.one module picks it from the list too, so there is no need to paste the key again when you add it.

First scenario

Your first scenario with Print.one

GoalWhen a new contact arrives in another app, Make sends that person a Print.one postcard.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the +. Pick the app where your contacts live first, since Print.one cannot start a scenario on its own.

  2. 02

    Set up the starting module

    Choose the module of that app that returns the new contacts, click Create a connection for it and fill its fields. Make lists what it can read once the account is linked.

  3. 03

    Add Send Postcard

    Click the + to the right of the first module, search for Print.one and pick Send Postcard. Select your Print.one connection, then map the contact data from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time, and you can open each module to read the bundles it received. Check that one contact produced one postcard request before going further.

  5. 05

    Schedule and switch on

    Open the clock on the first module, which runs every 15 minutes by default, and adjust it to your plan. Then switch the scenario on. Every run of each module counts as an operation on your Make plan.

Modules

What the Print.one modules do

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

Print.one1

Make API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens a direct line to Print.one: you send any authorized request, and your saved connection handles the key for you. It is the way out when the other module does not do what you need.

When to use it
a Print.one action exists in their API but has no dedicated module in Make, and someone on the team can read the Print.one API documentation.
Watch out
this module expects you to know the request to send, so test it with Run once before wiring it to live data.
Print.one2

Send Postcard

Action

In Make“Sends a postcard.”

Turns a bundle of data into a real postcard sent by Print.one, so a customer or prospect receives something in the mail without anyone handling it. Each bundle that reaches it becomes one card.

When to use it
right after the module that brings in the recipient, such as a new buyer in your shop app or a lead from a form.
Watch out
the Print.one app in Make has no module to cancel a card, so check the mapping with Run once on a single test contact.
Need help

Need help automating Print.one with Make?

A person reads every message.

FAQ

Print.one and Make: common questions

01Is the Print.one Make integration free?
Yes, on the Make side. Print.one is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a gap of at least 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans lower the gap to 1 minute and allow runs of up to 40 minutes. Print.one itself needs its own active account and subscription, chosen on the Print.one pricing page, and this page quotes no price for it.
02What do you need to connect Print.one to Make?
Two things: an active Print.one account and the API key that comes with it. In Make, add a Print.one module, click Create a connection, paste the key and save. The connection is stored once and both Print.one modules reuse it. If you do not have an account yet, create one on Print.one and pick a subscription on their pricing page before you open Make, since the key only exists once the account does.
03Does the Print.one Make integration react in real time?
No, because Print.one has no trigger in Make at all. Its two modules are actions, so something else has to start the scenario. You have two options. Put another app's trigger first, for example the tool where orders or leads arrive; if that trigger is instant, the app alerts Make through a webhook as soon as something happens. Or let the schedule start it: a new scenario runs every 15 minutes by default, with 1 minute as the shortest gap on paid plans.
04What if a Print.one module is missing in Make?
It depends on what you need. Besides Send Postcard, the Print.one app ships a Make API Call module that sends an authorized request to Print.one using your existing connection, which covers actions without a dedicated module if you know the request. It is not the universal Make an API Call module found on some other apps. If that route feels too technical, another app may handle the step, or the team can look at the case with you.
05Should you use Make or n8n with Print.one?
It depends on the rest of your setup. On the Make side, the facts are known: 2 modules, both actions, a connection by API key and access from the Free plan. Before choosing n8n, check whether it offers a Print.one node at all, since this page does not confirm it. Then compare on the criteria that matter to your team, such as the tools you already automate and who will maintain the scenario. The n8n vs Make comparison page on this site sets those criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations