Menu
Mattering Automations connector

A Sendcloud MCP that buys the label, and knows which steps cost money

Connect one Sendcloud key pair and 42 nodes land on the canvas: rate a route before you commit, ship an order and get the label back, track parcels, find service points, announce and cancel returns, book a carrier pickup, and read transit times and invoices. Eight of those nodes spend money or send a driver, and every one of them is flagged so you can put an approval in front of it.

42 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Sendcloud MCP connector does

The Sendcloud connector for Mattering Automations is 42 nodes on Sendcloud API v3: 30 read nodes and 12 action nodes covering the account spine, rating and checkout options, orders, shipments, parcel tracking, service points, returns, pickups, transit time analytics, invoices and the account event feed. Sendcloud is the shipping layer between a store and the carriers, so the automation value sits where the two meet: an order that needs a label, a parcel whose status changed, a return that needs announcing, a month of carrier performance that nobody has time to read.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant answering a where is my parcel question can read Sendcloud: Track Parcel and Sendcloud: Get Shipment and give a real answer, and it can do that safely, because reading is 30 of the 42 nodes and none of them commits anything.

The thing to design around first is cost. Buying a label, announcing a shipment and booking a pickup are real commercial acts: Sendcloud: Ship Order and Buy Label, Sendcloud: Create and Announce Shipment, Sendcloud: Create Shipment Using Shipping Rules, Sendcloud: Create Return and Sendcloud: Book Carrier Pickup all reach a carrier, and none of them is freely undone. Cancellation exists but it is bounded and conditional rather than a general undo: Sendcloud documents a window after announcement, refuses shipments that are already cancelled or already delivered, and answers a cancellation with a queued status as often as a completed one. Sendcloud also states that re-sending a cancelled shipment voids its insurance. A booked pickup sends a real driver to a real address. All eight of these nodes carry the destructive flag for that reason, and the honest advice is the same one you would give for a payment connector: put an approval or a condition between the trigger and the node, and rehearse the shape with the read nodes first.

Rating before committing is what makes that workable, and it is a genuinely useful pattern rather than a consolation. Sendcloud: List Shipping Options prices a real route and parcel and returns only the options your account can actually buy, Sendcloud: Get Checkout Delivery Options answers the same question in checkout shape, Sendcloud: Calculate Duties and Taxes gives the landed cost for a cross border parcel, Sendcloud: Validate Address checks a destination before a carrier rejects it, and Sendcloud: Validate Return checks whether a return could be announced without creating or announcing anything. Five nodes that answer the expensive questions for free, and they are all reads.

One connection, three surfaces

  • Visual automations. Drag Sendcloud nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Sendcloud node, ready to drop on the canvas

42 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 30

Sendcloud: Calculate Duties and Taxes

Estimate import duty and tax for a cross-border shipment before it is sold or shipped: per-item duty and tax rates and amounts, an HS-code description, the de minimis thresholds that applied, and a landed-cost total. Creates nothing. Use it to show a delivered-duty-paid price at checkout, or to decide whether a route is worth shipping at all.

Sendcloud: Check Service Point Availability

Check whether a service point is currently accepting parcels before a label is bought for it. A POST that creates nothing, which is why it is classed Safe Read. Returns a single boolean, so it slots straight into a condition node ahead of a service-point shipment.

Sendcloud: Get API User Metadata

Return the user id and integration id the current API credential is bound to. The cheapest authenticated call on the whole API (no parameters, no pagination, two integers back), so it doubles as the credential health check. The integration_id it returns is the one the order endpoints expect.

Sendcloud: Get Carrier Contract

Retrieve one carrier contract by id: its carrier, client id, country, state and whether it is the default for that carrier.

Sendcloud: Get Carrier Transit Times

How long each carrier actually took, per origin and destination country pair: parcel volume and mean transit time in hours and in whole days over the requested period. Answers which carrier is fastest on a lane using this account's own shipments rather than a marketing claim. Response is BARE (no data wrapper): read data.transit_times[].

Sendcloud: Get Checkout Delivery Options

Generate the customer-facing delivery choices for a checkout: titles and descriptions, delivery-method type (same day, next day, service point, standard), cut-off time, shipping rate charged to the shopper, carrier and logo, candidate delivery dates, lead-time percentiles and a sustainability rating. This is the shopper-facing view of the rating engine, shaped for a checkout widget rather than for label buying, and it creates nothing. Response is BARE (no data wrapper): read data.delivery_options[].

Sendcloud: Get Order

Retrieve one order by its Sendcloud id, with the full detail the list view abbreviates: every line item with weights and prices, payment breakdown (discounts, insurance, freight), customs details with sender, receiver and importer tax numbers, and the billing and shipping addresses.

Sendcloud: Get Organization

Return the Sendcloud organization behind the credential: its id, display name, and the date the account was registered. Useful for stamping which account a workflow ran against.

Sendcloud: Get Parcels Report

Check a queued parcels report and collect its CSV. Poll until status is ready, then read url for the signed download link and expires_at for how long it stays valid. Response is BARE (no data wrapper).

Sendcloud: Get Return

Retrieve one return by its Sendcloud id: current status, tracking number and URL, both addresses, weight, shipping product, and the label as both an A4 sheet and a label-printer file. Poll this after requesting a cancellation to learn whether the carrier actually accepted it. Response is BARE (no data wrapper).

Sendcloud: Get Return Portal URL

Get the branded return-portal URL for a shipment, so a workflow can drop a working returns link into an order confirmation or a support reply instead of sending the customer to hunt for one. Returns HTTP 404 when no return portal is configured for that shipment's brand.

Sendcloud: Get Service Point

Retrieve one service point by its Sendcloud id: name, carrier, shop type, address, coordinates and whether the record has expired. Use it to re-read the point a customer chose at checkout before printing a service-point label.

Sendcloud: Get Shipment

Retrieve one shipment by id, with every parcel, its current status, tracking numbers and URL, document links, addresses, shipping option, carrier and any errors recorded against it.

Sendcloud: Get Shipping Option Transit Times

The same transit-time report, one level finer: per SHIPPING OPTION rather than per carrier, so a standard service and an express service on the same carrier are compared separately. Parcel volume and mean transit time in hours and whole days per origin and destination pair. Response is BARE (no data wrapper): read data.transit_times[].

Sendcloud: List Account Events

Read the account's audit event feed: who did what to which resource and when, as create, update and delete operations with the acting user and organization ids. Use it to drive a workflow off changes made in the panel rather than only off webhook deliveries, or to reconstruct what changed a shipment.

Sendcloud: List Brands

List the brands configured on the account: name, domain, colour, logos and tracking-email reply-to settings. A brand controls how the tracking page and tracking emails look, so this is the picker source for brand_id on the shipment and return nodes.

Sendcloud: List Carrier Contracts

List the carrier contracts on the account: which carriers can be shipped with, on whose account (direct contract or Sendcloud's own rates), in which country, and which is the default per carrier. This is the authoritative list of the account's carriers, so it is the picker source for both contract_id and carrier_code across this connector.

Sendcloud: List Integrations

List the shop integrations connected to the account: shop name and URL, type, when each last fetched orders, whether it has been failing and since when, and its webhook settings. Picker source for integration_id, and the fastest way to spot an integration that has silently stopped importing orders.

Sendcloud: List Invoices

List the invoices Sendcloud has issued to the account: reference, issue and due dates, taxable and non-taxable amounts, tax, description, category (transactional or subscription) and the issuing entity's details. The read a finance workflow needs to reconcile shipping spend.

Sendcloud: List Orders

List orders imported from the connected shops, with their items, payment status, customs details and shipping address. Filter by integration, order number, status, or a creation or update date range. This is the queue a fulfilment workflow reads before shipping anything, and the picker source for order ids elsewhere in this connector.

Sendcloud: List Parcel Statuses

List every parcel status code Sendcloud can report, with its human message (READY_TO_SEND, ANNOUNCED, DELIVERED, CANCELLED and the rest). Takes no parameters. This is the picker source for the parcel_status filter on the shipment lister, so a workflow filters on a code the API actually recognises instead of a guessed string.

Sendcloud: List Pickups

List the carrier pickups booked on the account, with their time slots, country, carrier, the carrier's pickup reference, status (ANNOUNCING, ANNOUNCED, CANCELLED), and when each was created or cancelled. Read this before booking another to avoid double-booking a driver.

Sendcloud: List Returns

List returns in a date range, with the label cost, tracking number, label URL, both addresses, the shipping product used, the returned items, whether the return is still cancellable, and the full carrier status history. The date range is REQUIRED. Response is BARE (no data wrapper) and also mirrors next and previous page URLs into the body alongside data[].

Sendcloud: List Sender Addresses

List the sender (ship-from) addresses configured on the account, with their tax numbers and label signature. This is the picker source for sender_address_id, and the place to read a from_address before announcing a shipment.

Sendcloud: List Service Points

Find parcel shops, lockers, post offices and carrier depots near an address or a coordinate: name, carrier with logo, address and position, opening times for every weekday, whether it is open tomorrow, when it next opens, and the distance from the search point. Search by free-text address, by structured address parts, by latitude and longitude with a radius, or by a bounding box (all four corners required, maximum 50 km diagonal). Those three modes are mutually exclusive.

Sendcloud: List Shipments

List shipments with their parcels: status, tracking number and tracking URL, label and document links, dimensions and weight, the from and to addresses, the shipping option used, the carrier, and any parcel items. Filter by parcel status, tracking number, order number, integration, or an updated or announced date range. This is the workhorse read for monitoring what is in flight.

Sendcloud: List Shipping Options

Rate a shipment: given a from and to address and the parcels, return every shipping option available for that route, with carrier, product, functionalities (tracked, signature, multicollo, last mile), weight and dimension limits, the contract each option would be billed to and, with calculate_quotes on, the price breakdown and lead time. A POST that CREATES NOTHING, which is why it is classed Safe Read. It is also the picker source for shipping_option_code everywhere else in this connector, so those pickers offer only options that can actually be bought for the shipment being configured.

Sendcloud: Track Parcel

Look up a parcel by its carrier tracking number and get the full event history: every carrier and Sendcloud event with its timestamp, status code, human description and success or failure type, plus the expected delivery date, both addresses and every tracking number on the parcel. This is the node a where-is-my-order workflow reads. Response is BARE (no data wrapper): read data.events[] and data.details.

Sendcloud: Validate Address

Check a delivery address against a carrier's own rules before buying a label, and get back a corrected version where one exists. Each result carries whether it is valid, which attributes were changed, which are invalid, and whether that result is the recommended one. Cheaper than a failed announcement and far cheaper than a returned parcel. Response is BARE (no data wrapper): read data.input_address_is_valid and data.results[].

Sendcloud: Validate Return

Dry-run a return: check whether it could be announced, WITHOUT creating the return or announcing anything to the carrier, in Sendcloud's own words. Same body as creating a return, so the safe way to build a return flow is to wire this node first, confirm it passes, then swap in the create node. Response is BARE (no data wrapper) and mirrors the validated return back.

Action nodes 12

Sendcloud: Book Carrier Pickup

DESTRUCTIVE: SENDS A REAL DRIVER TO A REAL ADDRESS. Book a carrier pickup for parcels waiting to be collected. Carriers commonly charge for a pickup and for a wasted call-out, and this connector ships no cancel-pickup node, so a booking made here is undone in the Sendcloud panel or with the carrier. The required fields differ PER CARRIER (carrier_code is the discriminator): DHL, UPS and Correos among others also require the items breakdown. Supply contract_id whenever more than one active contract exists for the carrier, or the request is rejected.

Sendcloud: Cancel Return

DESTRUCTIVE AND ONE-WAY. Ask the carrier to cancel a return label. Not every carrier supports cancellation over the API, and there is no un-cancel. HTTP 202 only means the REQUEST was accepted and the carrier supports cancelling, not that the return is cancelled: re-read the return with Sendcloud: Get Return and check its status to confirm. HTTP 409 means the return is not cancellable. Response is BARE (no data wrapper).

Sendcloud: Cancel Shipment

DESTRUCTIVE AND ONE-WAY. Ask the carrier to cancel an announced shipment. There is no un-cancel: Sendcloud documents that if a cancelled shipment is sent anyway, ITS INSURANCE COVER IS VOID. Cancellation is only possible within 42 days of announcement, is carrier dependent, and is refused for shipments already cancelled or delivered. HTTP 200 means cancelled; HTTP 202 means the cancellation was QUEUED, so re-read the shipment to learn the outcome rather than assuming success.

Sendcloud: Create External Parcel for Tracking

Register a parcel that was shipped OUTSIDE Sendcloud so it still appears in Sendcloud tracking, the branded tracking page and analytics. Buys nothing and announces nothing to a carrier: it records an existing tracking number. IDEMPOTENT by source_id plus carrier code, so a retried run returns the existing parcel with created set to false instead of duplicating it, which is what makes it safe behind a submission trigger. Response is BARE (no data wrapper).

Sendcloud: Create Parcels Report

Queue a CSV export of parcels announced in a date range, choosing exactly which columns it contains. Returns a report job with status queued; poll Sendcloud: Get Parcels Report until status is ready, then read the signed CSV URL from its url field. Classed Reversible Write because it creates a temporary report job and nothing else: it moves no parcel and spends nothing. The URL EXPIRES, so download it in the same run rather than storing the link. Response is BARE (no data wrapper).

Sendcloud: Create Return

DESTRUCTIVE: BUYS A REAL RETURN LABEL and, unless tracking emails are turned off, EMAILS THE CUSTOMER. Creates a return shipment and announces it, returning the return id, the parcel id and any multi-collo parcel ids. The label is billed like any other. Validate the same payload with Sendcloud: Validate Return first, which checks everything and creates nothing. Response is BARE (no data wrapper).

Sendcloud: Create Shipment Using Shipping Rules

DESTRUCTIVE: BUYS A REAL SHIPPING LABEL. Same as creating and announcing a shipment, except the account's shipping rules and defaults fill in what is missing, so only the destination address is strictly required and the carrier, sender address, box and service can all be decided by the rules. The response adds applied_shipping_rules showing which rules fired and what they changed, which is the thing to read when a shipment came out different from expected. Note that shipping rules do not fully apply to multicollo shipments.

Sendcloud: Create and Announce Shipment

DESTRUCTIVE: BUYS A REAL SHIPPING LABEL. Create a shipment from raw addresses and parcels and announce it to the carrier synchronously, returning the parcels with their tracking numbers and label links. Use this when the shipment does not come from a Sendcloud order. Maximum 15 parcels per request. The carrier bills for the label the moment this succeeds, and cancelling afterwards is carrier dependent and time limited, so never put this behind an untested trigger.

Sendcloud: Create or Update Orders

Push up to 100 orders into Sendcloud in one call. This is an UPSERT keyed on order_id plus integration id: a matching order is updated, a new combination is created. Use it to feed orders from a shop Sendcloud has no native integration with. Two things to know before wiring it up: the batch is ALL-OR-NOTHING, so one invalid order rejects all of them, and processing is ASYNCHRONOUS, so confirm the order exists before a later node tries to ship it.

Sendcloud: Delete Order

DESTRUCTIVE AND IRREVERSIBLE. Permanently remove an order from the Sendcloud account. Sendcloud documents no recovery and no trash: once deleted the order is gone, and re-importing it depends on the source shop still holding it. Answers HTTP 204 with an empty body, which surfaces as an empty data object.

Sendcloud: Ship Order and Buy Label

DESTRUCTIVE: BUYS A REAL SHIPPING LABEL. Turn an existing Sendcloud order into an announced parcel and return the label synchronously, base64-encoded plus a document link and the tracking number. This is the flattest way to ship from the canvas because the addresses and contents come from the order already in Sendcloud; only the shipping choice is made here. The label is billed by the carrier and the parcel is announced to them, so treat every run as spending money. Cancelling afterwards is possible within 42 days but is carrier dependent.

Sendcloud: Update Order

Patch one order in place. Only the sections supplied are touched, so a workflow can move an order's status, correct a shipping address, or attach customs details without resending the whole record. Within order_details.order_items, an item is matched by its name.

Connecting Sendcloud takes one credential

Sendcloud issues API credentials as a pair from the Sendcloud panel under Settings, then Integrations, then API. Both halves are shown when the key is created: the public key is the username and the secret key is the password of an HTTP Basic header. There is no header token scheme, no query string key and no account or region identifier in the URL. Mattering asks for both halves under Sendcloud's own field names rather than a generic username and password box, because that mismatch is how the wrong value ends up in the wrong field. Two things worth checking before you scope a workflow. What you can actually buy is decided by the carrier contracts on your account rather than by this connector, so Sendcloud: List Carrier Contracts is the real inventory of what your shipment and pickup nodes can reach, and a pickup for a carrier you hold more than one contract with is rejected unless the contract is named. And Sendcloud's developer portal does not document whether API access itself is gated by plan, so confirm that with Sendcloud rather than assuming from the developer docs. Shipment volumes per plan are published on Sendcloud's pricing page.

1

Sign in to the Sendcloud panel and open Settings, then Integrations, then API. Create an API key and copy both the public key and the secret key while they are shown.

2

In Mattering Automations, open Connectors, click Add Connector, choose Sendcloud, and create a credential with the public key and the secret key in their own fields.

3

Click Test Connection. Mattering calls Sendcloud's API user metadata endpoint, which takes no parameters, touches no carrier and costs nothing: it returns your user id and integration id, so a success proves the credential and hands you the integration id the order nodes ask for.

4

All 42 Sendcloud nodes appear in the canvas palette. Run Sendcloud: List Carrier Contracts next. It tells you which carriers and services this account can actually ship with, which is what every label and pickup node depends on.

Common uses for the Sendcloud MCP

Rate a route before anything commits

Sendcloud: List Shipping Options takes a from address, a to address and the parcels, and returns the options your account can genuinely buy for that specific shipment with their prices, rather than a catalogue of everything the carriers offer. Sendcloud: Get Checkout Delivery Options answers the same question in the shape a checkout page needs, Sendcloud: Calculate Duties and Taxes gives the landed cost on a cross border parcel, and Sendcloud: Validate Address checks the destination before a carrier refuses it. All four are reads that create nothing, which makes them the right first half of any workflow whose second half spends money.

Fulfilment: order in, label out

Sendcloud: Create or Update Orders pushes orders in from wherever they live, and Sendcloud: Ship Order and Buy Label turns one into a real label, returned inline in the response so the next node can print or file it. Sendcloud: Create and Announce Shipment does the same for a shipment assembled directly, and Sendcloud: Create Shipment Using Shipping Rules lets the rules already configured in your Sendcloud account choose the carrier and service. These are the nodes that cost money, so the shape that works is a rating step and a condition in front of them, and a note that Sendcloud's shipping rules do not fully apply to shipments carrying more than one parcel, so a rules driven flow can behave differently once a multi parcel order shows up.

Tracking that reaches the customer before they ask

Sendcloud: Track Parcel reads a parcel's current status and history by tracking number, and Sendcloud: List Shipments sweeps for what changed. Because the parcel status list is available as Sendcloud: List Parcel Statuses, a workflow can watch for the specific statuses that matter to you rather than a hardcoded string: a delay opens a task, a delivery closes one, a failed delivery attempt sends the customer the service point details. Sendcloud: Create External Parcel for Tracking brings a parcel shipped outside Sendcloud into the same view, so one workflow covers everything you send.

Returns without a person in the middle

Sendcloud: Get Return Portal URL hands a customer the link to start a return themselves, and Sendcloud: Validate Return checks whether a return could be announced without creating it or announcing it with the carrier. Sendcloud: Create Return then announces the real thing, which is where cost starts, and Sendcloud: List Returns and Sendcloud: Get Return follow it to completion. One requirement is easy to miss until a carrier rejects the parcel: a return originating outside the EU needs the item breakdown, with a commodity code and country of origin per item, and omitting it fails at announce time rather than at validation time.

Service points at the moment of choosing

Sendcloud: List Service Points finds drop off and pick up locations for a destination, Sendcloud: Get Service Point reads one, and Sendcloud: Check Service Point Availability confirms it can still take a parcel before the shipment names it. This is the read half of the checkout experience, and it is worth knowing that the search modes are mutually exclusive rather than combinable: free text, structured address parts, coordinates with a radius, and a bounding box are four different searches, and Sendcloud documents the bounding box as needing all four corners with a diagonal no longer than 50 km.

Carrier performance and invoices, on a schedule

Sendcloud: Get Carrier Transit Times and Sendcloud: Get Shipping Option Transit Times report how long parcels actually took over a period, with a parcel count beside each average, which is what lets a scheduled report weight the average properly instead of averaging averages. Sendcloud: List Invoices reads the billing side, Sendcloud: Create Parcels Report and Sendcloud: Get Parcels Report generate a parcel level export, and Sendcloud: List Account Events gives an audit feed of what happened on the account. A monthly workflow can write all of it into a Mattering database and open a task when a carrier's transit time moves further than it should.

Example: A daily fulfilment run that prices the shipment before it buys it

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a morning schedule fires, and Sendcloud: List Orders returns the orders that arrived since the previous run and are still waiting to be fulfilled.

2

Sendcloud: Validate Address checks each destination, and anything the validator flags goes straight to a task for a person rather than to a carrier.

3

Sendcloud: List Shipping Options prices the real route and parcel, returning only options this account can buy, and a condition compares the cheapest acceptable option against the shipping the customer paid.

4

Anything inside the expected range continues. Anything outside it stops and opens a Mattering task with both figures attached, because the next step is the one that spends money.

5

Sendcloud: Ship Order and Buy Label buys the label for the approved orders. This is the irreversible step: the label is a real commercial purchase, cancellation is bounded rather than general, and re-sending a cancelled shipment voids its insurance. Pace the loop as well, since Sendcloud documents a far lower rate limit for writes than for reads.

6

The label and tracking number are written back to the order system, and Sendcloud: Track Parcel runs on a later schedule to move each parcel's status until it is delivered.

Sendcloud MCP questions, answered

What Sendcloud operations are supported?

42 nodes on Sendcloud API v3: 30 read nodes and 12 action nodes. The account spine (API user metadata, organization, sender addresses, brands, carrier contracts, integrations, parcel statuses), rating and validation (shipping options, checkout delivery options, duties and taxes, address validation), orders (list, get, create or update, update, delete, ship and buy a label), shipments (list, get, announce, announce using shipping rules, cancel, return portal URL), tracking (track a parcel, create an external parcel for tracking), service points (list, get, check availability), returns (list, get, validate, create, cancel), pickups (list, book), and analytics and billing (carrier transit times, shipping option transit times, create and read a parcels report, invoices, account events). Deliberately not included: parcel document downloads, which return binary files rather than JSON, though every shipment and return payload already carries its documents as URLs and the ship order node returns the label inline; support ticket and claims workflows; shipping rule configuration, since the value here is applying rules rather than editing them; and Sendcloud's own webhook subscription management.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively. Reading is the large half of this connector, 30 of the 42 nodes, and it is the half to hand an assistant: tracking, rating, service points, transit times, invoices and validation all answer questions without committing anything. Keep the eight flagged nodes, the ones that buy labels, announce returns, book pickups or delete records, behind a condition or an approval task.

Which Sendcloud nodes cost money, and can they be undone?

Eight nodes are flagged, and five of them reach a carrier: Sendcloud: Ship Order and Buy Label, Sendcloud: Create and Announce Shipment, Sendcloud: Create Shipment Using Shipping Rules, Sendcloud: Create Return and Sendcloud: Book Carrier Pickup. Buying a label and announcing a shipment are real commercial acts, and booking a pickup sends a driver to an address. Undo is bounded rather than general: Sendcloud documents a cancellation window after announcement, refuses shipments that are already cancelled or already delivered, answers a cancellation with a queued status as often as a completed one, and states that re-sending a cancelled shipment voids its insurance. The other three flagged nodes, Sendcloud: Cancel Shipment, Sendcloud: Cancel Return and Sendcloud: Delete Order, remove or terminate records. Treat all eight the way you would treat a payment node: rehearse with the rating and validation reads, and put a condition or an approval in front of the commit.

Does Sendcloud have a test mode I can build against?

Sendcloud publishes a guide for creating test labels, which is the sanctioned way to exercise the label path without buying real postage, and there is no separate test host or test credential to configure: it is the same account and the same key pair. Sendcloud documents two ways to do it on the same account and the same key pair. The first is the Unstamped letter shipping option, which Sendcloud states you will not be charged for. The second is creating a real label and cancelling it inside the deadline, which Sendcloud does not describe as free and which not all carriers support. Two things are safe to build on instead. The read half of this connector, 30 nodes, is fully exercisable with any working key and commits nothing. And the rating and validation nodes answer the expensive questions without spending anything, so most of a fulfilment workflow can be designed and proven before the label node is ever enabled.

What are Sendcloud's rate limits?

Sendcloud documents them by method class rather than as one number: 1,000 requests per minute for safe reads, and for writes 100 requests per minute with a burst ceiling of 15 requests per second. Over the limit returns a 429, and Sendcloud documents no retry after header or rate limit headers, so none are claimed here. The practical consequence is worth designing for: a loop that buys labels one at a time is capped near 100 labels per minute, so a bulk fulfilment run needs pacing and needs to be restartable. Read heavy workflows, including tracking sweeps and reporting, are effectively unconstrained at automation volumes.

Why do the shipment and pickup nodes ask for a contract?

Because what you can buy is decided by the carrier contracts on your Sendcloud account, not by this connector. Sendcloud: List Carrier Contracts is the real inventory of what the label and pickup nodes can reach, and the contract fields on those nodes are pickers sourced from it, grouped by carrier. Naming the contract stops being optional in one specific case that Sendcloud documents: if the account holds more than one active contract for a carrier, a pickup that omits the contract is rejected. Pickups have a second requirement in the same spirit: the fields a pickup needs depend on which carrier it is for, and several carriers require an item breakdown that others do not.

Can a workflow start the moment a parcel status changes?

Not from this connector, which polls rather than listens. There are no trigger nodes here because Sendcloud's event subscription management is its own surface with its own authorization handshake, and this connector does not pretend to own it. Two polling paths cover most of what people want: Sendcloud: List Shipments swept on a schedule, and Sendcloud: List Account Events, which is a read only audit feed of what happened on the account. If you need immediate reaction, point a Sendcloud webhook at a Mattering webhook trigger and use these nodes for everything after that first hop.

Which API version is this built on, and does a v2 example still work?

This connector is built on Sendcloud API v3, which is the version Sendcloud tells new integrations to use. That matters more than it usually does, because v2 and v3 run at the same time on the same host and they are not variations on a theme: the core resource was renamed, so v2 parcels became v3 shipments and a v3 shipment contains parcels, sender addresses moved, most v3 responses are wrapped in an envelope that v2 did not have, and pagination changed from page numbers to opaque cursors. So an example, wrapper library or blog post written for v2 will produce a not found or a silently wrong shape against v3. Every path in this connector was read from the v3 reference for that specific endpoint.

42 nodes waiting on the canvas

Put Sendcloud to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Sendcloud is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products