Resources · Make integration

SellIntegro CloudPrint Make integrationAutomate SellIntegro CloudPrint with Make.

Can Make send your print jobs to SellIntegro CloudPrint for you? Yes. The SellIntegro CloudPrint Make integration gives you 2 action modules, Print and Make an API Call. This page shows how to link your account and build a first scenario that prints on its own.

Try the SellIntegro CloudPrint integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the SellIntegro CloudPrint Make integration do?

The SellIntegro CloudPrint Make integration lets a Make scenario, the automation you build as a chain of bricks called modules, hand work to CloudPrint without you opening it. There is no trigger on the CloudPrint side, so something else starts the scenario: another app, or a schedule set in Make.

Print when an order lands. Put the trigger of your shop or order tool first, then the Print module. Each new order becomes one bundle, the item that travels from one module to the next, and Print acts on it.

Print on a schedule. No app to listen to? Start with nothing but the clock of Make on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that interval.

Reach what Print does not cover. Make an API Call calls any endpoint of the CloudPrint API with the same connection, so a need the Print module misses can still be met.

A fair warning: Make itself says its documentation for this app is limited, because little public information exists about SellIntegro CloudPrint. Expect to discover the fields inside the module rather than in a guide, and keep Make troubleshooting close for your first runs.

Weighing tools? The n8n vs Make comparison helps, and the Make training walks through scenarios from zero.

Connect

How do you connect SellIntegro CloudPrint to Make?

  1. 01

    Open a CloudPrint module

    In your scenario, add the Print module and click Create a connection. A connection is your CloudPrint account linked to Make once; every module of the app reuses it afterwards.

  2. 02

    Name it if you like

    Giving the connection a name is optional. It pays off when you handle several CloudPrint accounts, say one per client, because you pick the right one from a list later.

  3. 03

    Authorize and save

    Either approve Make on the CloudPrint page that opens, or paste the key CloudPrint hands you, depending on what the app asks for. Then click Save and the module is ready to fill.

First scenario

Your first scenario with SellIntegro CloudPrint

GoalWhen a new order arrives in the app you already use, Make sends a print job to SellIntegro CloudPrint.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place its first module. That first module decides when everything starts.

  2. 02

    Pick the starting point

    Search your shop or form app by name and choose its trigger, then click Create a connection to link that account. No app to watch? Leave the schedule of Make as the starter.

  3. 03

    Add Print

    Click the + on the right of the first module, search SellIntegro CloudPrint and choose Print. Link your CloudPrint account, then map the data coming from the previous module into the fields Make displays.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Open the bubble above each module to read the bundles it received and confirm the job reached CloudPrint.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and flip the scenario on. From now on each run counts operations, one per module per bundle, on your plan.

Modules

What the SellIntegro CloudPrint modules do

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

SellIntegro CloudPrint1

Make an API Call

ActionIn the docs only

This module gives you the rest of the CloudPrint API from inside your scenario, reusing the connection you already made, so a need that Print does not cover is still within reach.

When to use it
the moment Print lacks an option you need and the CloudPrint API offers it.
Watch out
Make documents this app only lightly, so you will need API documentation from CloudPrint itself, if it provides one, to know which endpoint to call.
SellIntegro CloudPrint2

Print

ActionIn the docs only

As its name says, Print is the action meant to send a job to CloudPrint for each bundle it receives, so a new order or a new file turns into a print request with no one clicking anything.

When to use it
as the last step of a scenario started by your shop, your forms or the schedule of Make.
Watch out
the official documentation lists no fields, so connect first and let Make show you what the module expects before mapping.
Need help

Need help automating SellIntegro CloudPrint with Make?

A person reads every message.

FAQ

Questions about the SellIntegro CloudPrint Make integration

01Is the SellIntegro CloudPrint Make integration free?
Yes, SellIntegro CloudPrint is a standard app, so it works on the Free plan of Make. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations: one for each module that runs on each bundle.
02What do you need to connect SellIntegro CloudPrint to Make?
A SellIntegro CloudPrint account and a Make account. Make's documentation lists no specific prerequisite for this app. You add one of its modules, click Create a connection, optionally name it, then either authorize Make on the CloudPrint page or paste the key the app gives you, and click Save. The connection is stored once and every CloudPrint module in your scenarios reuses it, so there is nothing to repeat when you build the next one.
03Does SellIntegro CloudPrint trigger Make scenarios in real time?
No, because the app has no trigger module at all in Make. Its 2 modules are actions, so the scenario has to start elsewhere. You can open it with the trigger of another app, for instance the one where your orders or forms arrive. Or you can rely on the schedule of Make alone: a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute between runs.
04What if a SellIntegro CloudPrint module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the CloudPrint API with the connection you already have, so you are not limited to the Print module. The catch is documentation: Make states that its guide for this app is limited because little public information exists about SellIntegro CloudPrint. You will need API documentation from CloudPrint itself, if it provides one, to know what to call and what to send in each request.
05Should you use Make or n8n for SellIntegro CloudPrint?
It depends on the tool your team already runs. On Make, SellIntegro CloudPrint comes with 2 modules, Print and Make an API Call, and works from the Free plan. The same app often has an n8n node as well, so check whether it exists before choosing. Neither answer is better in general: pick the platform where your other scenarios already live, so every automation stays in one place and is easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations