Mattering Automations Sendcloud integration
Connect Sendcloud to Mattering Automations: rating and address validation, orders, shipments and labels, parcel tracking, service points, returns, pickups, transit time analytics and invoices as workflow steps, authenticated with one public and secret key pair.
The Mattering Automations Sendcloud integration puts Sendcloud API v3 on your automation canvas: rate a route and validate an address before you commit, push orders in, buy labels, track parcels, find service points, announce and cancel returns, book carrier pickups, and read transit time analytics, invoices and the account event feed.
The credential is a Sendcloud API key pair. Sendcloud issues a public key and a secret key together from the panel, and they go on the wire as HTTP Basic with the public key as the username and the secret key as the password. Mattering asks for them under Sendcloud's own names rather than a generic username and password box, because that mismatch is exactly how the two halves end up swapped. Setup takes a few minutes, and this guide walks through each step and ends with the full node reference.
One thing deserves reading before you build anything. Of the 42 nodes, eight are flagged destructive, and five of those reach a carrier: buying a label, announcing a shipment, announcing a return and booking a pickup are real commercial acts, and a booked pickup sends a real driver to a real address. Undo is bounded rather than general, which is not the same as reversible. Treat this integration the way you would treat a payment connector: build the rating and validation half first, keep the committing nodes behind an approval, and use Sendcloud: Validate Return and Sendcloud: List Shipping Options to answer the expensive questions for free.
Before you start
- A Sendcloud account you can create API credentials in. The key pair is created in the Sendcloud panel under Settings, then Integrations, then API, and both halves are shown at creation.
- At least one active carrier contract on the account if you intend to use the shipment, label, return or pickup nodes. What you can buy is decided by your contracts rather than by this integration, and Sendcloud: List Carrier Contracts is the inventory of what those nodes can actually reach.
- A sender address configured in Sendcloud, which the label nodes need as the origin. Sendcloud: List Sender Addresses reads what is configured.
- A Mattering workspace with access to the Automations app.
- Worth confirming with Sendcloud before you scope a workflow: Sendcloud's developer portal does not document whether API access itself is gated by plan, so confirm that with Sendcloud; shipment volumes per plan are published on Sendcloud's pricing page. Sendcloud also publishes a test-label guide and states that labels created with the Unstamped letter shipping option are not charged. The cancel-inside-the-deadline method carries no such statement and depends on carrier support.
Create a Sendcloud API key pair
Mattering authenticates to Sendcloud with the key pair Sendcloud issues from its panel: the public key goes on the wire as the Basic username and the secret key as the password. There is no header token scheme, no query string key and no region or account identifier anywhere in the URL, so these two values are the whole credential.
Connect Sendcloud to Mattering
Verify it works
After connecting, open any automation canvas and check the palette: a Sendcloud section should list the read and action nodes. Drop Sendcloud: Get API User Metadata onto the canvas and run a test step. It is the integration's natural probe, because it takes no parameters and returns two integers: your user id and your integration id. Keep the integration id somewhere, because the order nodes ask for it and this is the easiest place to read it rather than hunting for it in the panel.
Now confirm what this account can actually ship. Drop Sendcloud: List Carrier Contracts onto the canvas and run it: the rows are the carriers and services your account holds contracts for, grouped by carrier, and they are the same values the contract pickers on the label and pickup nodes offer. If that list is empty, the label nodes have nothing to buy with, and that is an account configuration matter in Sendcloud rather than a connector problem. Finish with a rating read: Sendcloud: List Shipping Options with a real from address, to address and parcel returns the options and prices this account can genuinely buy for that shipment. Everything in this verify path is read-only and reaches no carrier, so it is safe to re-run whenever you rotate the keys.
Node reference
42 nodes, generated from the connector itself so this reference always matches what ships.
Read and query nodes 30
Sendcloud: Calculate Duties and Taxes
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
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
sendcloud_get_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
sendcloud_get_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
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
sendcloud_get_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
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
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
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
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
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
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
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
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
sendcloud_list_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
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
sendcloud_list_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
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
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
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
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
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
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
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
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
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
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
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
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
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
sendcloud_create_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
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
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
sendcloud_create_external_parcel
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
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
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
sendcloud_create_shipment_with_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
sendcloud_create_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
sendcloud_upsert_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
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
sendcloud_ship_order
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
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.
Using the integration
On the automation canvas
Sendcloud nodes chain with every other node in the workspace. A schedule can sweep Sendcloud: List Shipments for status changes and open a task when a parcel stalls, an order feed can drive Sendcloud: Create or Update Orders, and Sendcloud: Track Parcel can feed a customer update in Comms or a row in a Mattering database. Most identifier fields are pickers sourced from the matching list node, so you choose a contract by carrier and a shipment by recipient rather than pasting an opaque id. One picker is smarter than the rest and worth understanding: the shipping option field on the shipment nodes is sourced from a rater, not a catalogue, so it reads the addresses and parcels you already filled in on the same form and offers only options that can actually be bought for that shipment. If the addresses are blank it asks for them rather than listing a fiction.
From AI assistants over MCP
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter, the assistant built into the platform, can drive the same surface. Reading is the large half here, 30 of the 42 nodes, and it is the half to hand an assistant: Sendcloud: Track Parcel and Sendcloud: Get Shipment answer a where is my parcel question, Sendcloud: List Service Points finds a nearby drop off, Sendcloud: List Shipping Options prices a route, and Sendcloud: Get Carrier Transit Times answers how a carrier has been performing. None of those commits anything. The eight flagged nodes are the ones to keep off an agent-facing surface, or to route through an approval task, because five of them reach a carrier and spend money.
Rate and validate before you commit
This is the pattern that makes an expensive integration safe to automate. Sendcloud: List Shipping Options prices a real route and parcel and returns only what your contracts can buy, Sendcloud: Get Checkout Delivery Options answers the same question in checkout shape, Sendcloud: Calculate Duties and Taxes gives the landed cost on a cross border parcel, Sendcloud: Validate Address checks a destination before a carrier refuses it, and Sendcloud: Validate Return checks whether a return could be announced without creating it or announcing it with the carrier. All five are reads. Put them and a condition in front of every node that commits, and the committing node becomes the last step of a decision rather than the first step of a hope. Two documented ceilings belong in the same design: the synchronous shipment endpoint caps at 15 parcels per request, the rating endpoint at 50 parcels, and the duties calculator at 10 line items.
Orders and the label purchase
Sendcloud: Create or Update Orders pushes orders in, and Sendcloud: Ship Order and Buy Label turns one into a real label, returned inline so the next node can print or file it. Two documented behaviours change how the workflow should be wired. Order upsert is all or nothing and asynchronous: one invalid order in a batch rejects the whole batch, and a successful response does not mean the order is queryable yet, so confirm it exists with Sendcloud: Get Order before a later node tries to ship it. And the order id is typed inconsistently between request and response, coming back as a number while an update expects it as text, so a round trip that feeds a response straight back into a request fails validation until you convert it. Pace bulk fulfilment as well: Sendcloud documents 100 write requests per minute with a burst ceiling of 15 per second, so a label loop is capped near 100 labels per minute and should be restartable rather than assumed to finish.
Date filters here are not as simple as they look
Two of the busiest list nodes carry more than one date window, and choosing the wrong one gives a plausible answer to a different question. Sendcloud: List Shipments can filter on when a shipment was last updated or on when it was announced: the updated window is what a scheduled sync needs, because it catches carrier status changes on parcels announced weeks ago, while the announced window is what a fulfilment report needs. Sendcloud: List Orders has the same split between when an order was created and when it was last updated. Both pairs are available as ordinary fields, so pick deliberately rather than by whichever appeared first. Sendcloud: List Returns is stricter again: it requires a from date and a to date, so there is no recent returns call, and Sendcloud does not document which timestamp that range filters, so treat the result as a set to inspect rather than as rows you can bucket by day. Carrier status updates also arrive late by nature, and Sendcloud publishes no bound on how late, so a sync that only ever asks for yesterday will miss revisions.
Returns, service points and pickups
Sendcloud: Get Return Portal URL hands a customer a link to start a return themselves, Sendcloud: Validate Return checks a return without creating it, and Sendcloud: Create Return announces the real one. 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, after money has started moving. On service points, the four search modes are mutually exclusive rather than combinable: free text, structured address parts, coordinates with a radius, and a bounding box, and Sendcloud documents the bounding box as needing all four values with a diagonal no longer than 50 km. Sendcloud: Book Carrier Pickup is the node to treat most carefully of all: its required fields are decided by the carrier, several carriers need an item breakdown that others do not, a carrier the account holds more than one contract for rejects a pickup that does not name the contract, and the result is a real driver arriving at a real address.
Reporting, invoices and the event feed
Sendcloud: Get Carrier Transit Times and Sendcloud: Get Shipping Option Transit Times report how long parcels actually took over a period. Each row carries a parcel count beside the average, which is what a correct monthly rollup weights by: averaging the averages of two months with different volumes gives a number that looks right and is not. Sendcloud: Create Parcels Report and Sendcloud: Get Parcels Report generate a parcel level export, and the download link expires, so fetch it inside the same run rather than storing the URL for later. Sendcloud: List Invoices covers billing, and Sendcloud: List Account Events is a read only audit feed that also serves as the polling alternative to webhooks, since this connector has no trigger nodes and does not manage Sendcloud's own event subscriptions.
Troubleshooting
Test Connection fails with a 401 error
A shipment was cancelled but it still looks active
An order upsert reported success but the next node cannot find the order
A pickup booking is rejected
A service point search returns nothing or errors
The returns list ignores the date range I expected
A scheduled shipment sync keeps missing status changes
A cross border shipment or return is refused at announce time
A rules driven shipment behaved differently than expected
A parcels report link no longer works
Related
The Sendcloud MCP
What connecting Sendcloud unlocks for AI agents and automations, with common uses and FAQs.
More guides
All Automations documentation
Every integration guide, plus how connectors, credentials, and workflows fit together.
Sendcloud is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.