Resources · Make integration

Sendcloud Make integrationAutomate Sendcloud with Make.

Parcels, labels and refund requests can move on their own once Sendcloud talks to Make. The Sendcloud Make integration gives you 24 modules: 5 instant triggers, 12 actions and 7 searches. This guide shows shipping teams how to link the account and build a first working scenario.

Try the Sendcloud integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Sendcloud Make integration automate?

The Sendcloud Make integration links your Sendcloud account to Make, a no-code tool where you chain apps together. You build a scenario, which is the automation itself, out of modules, the small bricks that each watch, create, read or change one thing in Sendcloud, such as a parcel, an invoice or a sender address.

Parcels created from somewhere else. An order lands in a form, a spreadsheet or another shop tool. Create a Parcel opens the shipment in Sendcloud, then Download Parcel Document pulls its document into the scenario so the next module can store or send it.

Status changes that reach the right people. Watch Parcel Status fires the moment a parcel changes status. Pair it with Get a Parcel to read the full record, then pass the details to your support inbox or chat tool.

Refunds handled without copy and paste. Watch Refund Requests starts a scenario as soon as a refund is requested, so finance sees it in its own tool instead of checking Sendcloud by hand.

When the module you need is not in the list, Make an API Call reaches the rest of the Sendcloud API with the same connection. Sendcloud may also have an n8n node; the n8n vs Make comparison helps you weigh the two, and the Make review gives a wider view of the tool. Budget questions go to Make pricing.

Connect

How do you connect Sendcloud to Make?

  1. 01

    Generate your API key and token

    In Sendcloud, open Settings, then Integrations. Find Sendcloud API in the list and click Connect. Give this API integration a name, click Save, then copy the API key and the API token that appear on screen.

  2. 02

    Add a Sendcloud module in Make

    Log in to Make, open your scenario and add any Sendcloud module. Click Create a connection. The Connection name field is optional, but a clear name helps when you later run a second Sendcloud account.

  3. 03

    Paste the credentials and save

    Enter the key and token you copied, or follow the instructions Make shows on screen. Save. This connection is your Sendcloud account linked to Make once, and every other Sendcloud module of the scenario reuses it.

First scenario

Your first scenario: turn an incoming order into a Sendcloud parcel

GoalWhen a new order shows up in another app, Make creates the parcel in Sendcloud and fetches its document.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. Search for the app where your orders arrive and pick its module that watches new entries.

  2. 02

    Add Create a Parcel

    Click the + on the right of that first module, search Sendcloud and choose Create a Parcel. Click Create a connection and use the key and token from your Sendcloud settings.

  3. 03

    Map the order data

    Fill the fields of Create a Parcel by mapping values from the first module, such as the customer details it received. Once the connection exists, Make lists what it can read from Sendcloud.

  4. 04

    Fetch the parcel document

    Add Download Parcel Document after the parcel module and map the parcel it just created. The file then travels as a bundle, one item passed to whatever module you add next.

  5. 05

    Test with Run once

    Create a test order in the first app, then click Run once. Open the bubble above each module to read the bundles it received and check that a parcel really appeared in Sendcloud.

  6. 06

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Choose your interval, then switch the scenario on.

Triggers

Sendcloud triggers in Make

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

Sendcloud1Watch Connected Integrations

Watch Connected Integrations

Instant trigger

In Make“Triggers when an integration is connected.”

This trigger starts your scenario each time an integration gets connected in your Sendcloud account, so a new sales channel or a new API link never goes unnoticed by the rest of the team.

How it fires
instant, Sendcloud calls Make through a webhook as soon as the connection happens.
When to use it
post an alert in your team chat whenever someone plugs a new integration into the shared Sendcloud account.
Watch out
click Create a webhook before Create a connection, otherwise nothing reaches Make.
Sendcloud2Watch Deleted Integrations

Watch Deleted Integrations

Instant trigger

In Make“Triggers when an integration is deleted.”

You find out right away when a connection disappears from Sendcloud. This module turns that deletion into an event your scenario can react to, carrying the deleted integration.

How it fires
instant, Sendcloud calls Make through a webhook as soon as the integration is deleted.
When to use it
warn the operations lead the moment a connected channel is removed, so the removal can be checked with whoever made it.
Watch out
the scenario must be switched on to receive the webhook, so activate it once your test with Run once looks right.
Sendcloud3Watch Parcel Status

Watch Parcel Status

Instant trigger

In Make“Triggers when a parcel status is changed.”

Customers ask where their order is; this trigger lets Make answer before they do. It fires whenever a parcel changes status in Sendcloud and hands the parcel to the next module.

How it fires
instant, Sendcloud calls Make through a webhook as soon as the status changes.
When to use it
send the new status to your helpdesk, a customer message tool or a spreadsheet that tracks deliveries.
Watch out
every status change creates a bundle, so add a filter after the trigger if only some statuses matter, or each one costs an operation, the unit Make counts on your plan.
Sendcloud4Watch Refund Requests

Watch Refund Requests

Instant trigger

In Make“Triggers when a refund is requested.”

Refunds get handled faster when finance sees them without opening Sendcloud. As soon as a refund is requested, this trigger passes the request to your scenario so you can route it wherever the decision gets made.

How it fires
instant, Sendcloud calls Make through a webhook as soon as the request is made.
When to use it
open a task for the accounting team or add a row to a refund log each time a request comes in.
Watch out
test it with a real request and Run once so you can see which data the bundle actually carries before mapping it.
Sendcloud5Watch Updated Integrations

Watch Updated Integrations

Instant trigger

In Make“Triggers when an integration is updated.”

A changed setting is easy to miss when you check by hand. This module listens for any update made to an integration in your Sendcloud account and starts the scenario with the changed integration.

How it fires
instant, Sendcloud calls Make through a webhook as soon as the integration is updated.
When to use it
keep an audit trail of who changed a shop connection, or notify the person responsible for shipping rules.
Watch out
if your own scenario runs Update an Integration's Settings, that change can wake this trigger too, so keep the two in separate scenarios and filter out your own edits.
Modules

Sendcloud actions and searches in Make

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

Sendcloud1

Cancel a Parcel

Action

In Make“Cancels or deletes a parcel depending on its status and other parameters.”

Stops a shipment you no longer want to send. Depending on the parcel's status and other parameters, Sendcloud either cancels it or deletes it outright.

When to use it
an order gets cancelled in your shop or CRM and the parcel should not leave the warehouse.
Watch out
the outcome depends on the status, so run it once on a test parcel and read the result before relying on it.
Sendcloud2

Create a Parcel

Action

In Make“Creates a new parcel.”

Opens a brand new parcel in Sendcloud from data you map out of another module, which removes the typing step between an order and its shipment.

When to use it
orders arrive through a form, a spreadsheet or a tool that Sendcloud does not read directly.
Watch out
each run creates one parcel per bundle, so a test with several rows produces several parcels.
Sendcloud3

Delete Integration's Order

Action

In Make“Deletes an order from an integration.”

Removes an order that came in through one of your Sendcloud integrations, keeping the order list free of entries that should never ship.

When to use it
a duplicate or test order reached Sendcloud and you want it gone as soon as it is flagged elsewhere.
Watch out
a delete module cannot be undone from Make, so put a filter in front of it and test on a harmless order.
Sendcloud4

Download Parcel Document

Action

In Make“Downloads a parcel document.”

Pulls a document attached to a parcel into your scenario as a file, ready to be stored, emailed or printed by the next module.

When to use it
right after Create a Parcel or Update a Parcel, when the warehouse needs the paper without logging in to Sendcloud.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of your documents during the test.
Sendcloud5

Get a Brand

Action

In Make“Returns a specified brand.”

Returns one brand from your Sendcloud account, which is handy when you ship under several brand names and a scenario needs the right one.

When to use it
you already know the brand's identifier, for instance from a previous module, and want its full details.
Watch out
if you do not know the identifier yet, start with List Brands and pick from its results.
Sendcloud6

Get an Invoice

Action

In Make“Returns a specified invoice.”

Fetches one Sendcloud invoice so its details can land in your accounting tool or a finance spreadsheet without a manual export.

When to use it
a scenario already has the invoice reference and bookkeeping needs the matching record.
Watch out
this module reads one invoice only; to go through all of them, use List Invoices instead.
Sendcloud7

Get a Parcel

Action

In Make“Returns a specified parcel.”

Reads the complete record of a single parcel, which gives the rest of the scenario everything Sendcloud knows about that shipment.

When to use it
after Watch Parcel Status, when your message or report needs the full parcel record and not only what the trigger passed along.
Watch out
map the parcel identifier from the previous module rather than typing it, or the scenario will always read the same parcel.
Sendcloud8

Get a Sender Address

Action

In Make“Get a specified sender address.”

Brings back one of the sender addresses saved in Sendcloud, useful when parcels leave from more than one warehouse or shop.

When to use it
a scenario must pick the right departure address before creating or updating a parcel.
Watch out
the module needs the address identifier; List Sender Addresses shows you which ones exist.
Sendcloud9

Get a Shipping Method

Action

In Make“Returns a specified shipping method.”

Looks up a single shipping method in Sendcloud and returns its details, so a scenario can check the option before attaching it to a parcel.

When to use it
you store a preferred method per customer or product and want to confirm it before shipping.
Watch out
to compare several options at once, List Shipping Methods is the better starting point.
Sendcloud10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Sendcloud API from your scenario, using the connection you already set up, which covers what the listed modules leave out.

When to use it
you need a Sendcloud feature that has no dedicated module in Make.
Watch out
you have to know the endpoint and the data it expects, so keep the Sendcloud API documentation open while you build it.
Sendcloud11

Update an Integration's Settings

Action

In Make“Updates a specified integration's settings.”

Changes the settings of one integration in your Sendcloud account from a scenario, which saves opening the admin screens for a routine switch.

When to use it
a change decided in another tool, such as a planning sheet, has to be reflected on a shop connection.
Watch out
this edit can also wake Watch Updated Integrations, so avoid putting both in the same scenario.
Sendcloud12

Update a Parcel

Action

In Make“Updates a parcel with the option to request a label - if it hasn’t been requested before.”

Edits an existing parcel and, if no label was requested for it yet, lets you ask for one in the same step.

When to use it
an address or detail gets corrected upstream and the parcel should follow, or the label should only be requested once the order is confirmed.
Watch out
the label option only applies to a parcel whose label has not been requested yet, so plan that step for the right moment in the flow.
Sendcloud13

List Brands

Search

In Make“Returns a list of brands.”

Returns all brands set up in Sendcloud, each one as a separate bundle the next module can use.

When to use it
you run several brands and want to build or refresh a reference table elsewhere.
Watch out
a search can return zero, one or many items, and every module after it runs once per brand, which adds operations.
Sendcloud14

List Integrations

Search

In Make“Returns a list of integrations.”

Gives you every integration connected to your Sendcloud account, a quick way to see which channels feed your shipments.

When to use it
you need the identifier of an integration before reading its shipments or changing its settings.
Watch out
add a filter after it if you only care about one integration, or later modules run for all of them.
Sendcloud15

List Integration's Shipments

Search

In Make“Returns a list of shipments from an integration.”

Pulls the shipments that came through one specific integration, which isolates a single sales channel from the rest of your parcels.

When to use it
a channel manager wants a report on the orders from one shop only.
Watch out
fetch the integration first with List Integrations, and expect many bundles when the channel is busy.
Sendcloud16

List Invoices

Search

In Make“Returns a list of invoices.”

Collects your Sendcloud invoices as a series of bundles, ready to be copied into accounting software or a shared sheet.

When to use it
finance closes a period and wants every shipping invoice in one place.
Watch out
each invoice becomes its own bundle, so an aggregator helps if you need a single file or message at the end.
Sendcloud17

List Parcels

Search

In Make“Returns a list of parcels.”

Searches your parcels in Sendcloud and hands them over one by one, which is the base for reports and bulk checks.

When to use it
you want to review the parcels of a batch, spot the ones still waiting, or sync them to a spreadsheet.
Watch out
a large result means many operations downstream, so narrow the search before chaining heavy modules.
Sendcloud18

List Sender Addresses

Search

In Make“Returns a list of sender addresses.”

Shows every sender address stored in Sendcloud, so a scenario can choose the right origin for each shipment.

When to use it
you ship from several locations and the scenario must pick one based on the order.
Watch out
run it once and note the identifiers; they are what Get a Sender Address expects.
Sendcloud19

List Shipping Methods

Search

In Make“Returns a list of shipping methods.”

Returns the shipping methods available in your Sendcloud account, which helps you see the options before you hard-wire one into a scenario.

When to use it
you are setting up Create a Parcel and want to know which methods you can choose from.
Watch out
the list can return many bundles; keep it out of the main flow unless you really need every method on each run.
Need help

Need help automating Sendcloud with Make?

A person reads every message.

FAQ

Sendcloud and Make: common questions

01Is the Sendcloud Make integration free?
Yes, Sendcloud is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution. You still need your own Sendcloud account with its own subscription, described on the Sendcloud pricing page.
02What do you need to connect Sendcloud to Make?
You need an active Sendcloud account and an API key. In Sendcloud, go to Settings, then Integrations, find Sendcloud API and click Connect. Name the integration, save, and copy the API key and the API token shown on screen. In Make, add a Sendcloud module, click Create a connection and paste both values. For a trigger, click Create a webhook first. The same connection then serves all 24 Sendcloud modules.
03Do Sendcloud triggers in Make fire in real time?
Yes. All 5 Sendcloud triggers are instant: Sendcloud calls Make through a webhook as soon as the event happens, whether it is a parcel status change, a refund request or an integration being connected, updated or deleted. No polling interval applies to them. The scenario must be switched on to receive these calls, and each event still counts as operations on your Make plan. Test each trigger with Run once and a real event in Sendcloud before switching the scenario on.
04What if a Sendcloud module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Sendcloud API with the connection you already created, so a feature without a dedicated module is still within reach. You have to know the endpoint and the data it expects. Before going there, check the 12 actions and 7 searches: many needs, like reading a parcel, an invoice or a shipping method, are already covered by a ready module.
05Should you use Make or n8n for Sendcloud?
It depends on the criteria that matter to your team. On Make, Sendcloud comes with 24 ready modules, including 5 instant triggers, plus Make an API Call for the rest, and each step is set up in a visual editor with Run once to test. The same app often has an n8n node too, so check what that node covers against your use case. The n8n vs Make comparison on this site lays out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations