> ## Documentation Index
> Fetch the complete documentation index at: https://docs.armin.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Sendcloud

> See Sendcloud shipment status for a customer's orders in the ticket sidebar and with AI Agents.

The Sendcloud integration connects your Sendcloud account to Chatarmin CX. Agents see where a customer's parcels are without leaving the ticket, and AI Agents can answer "Where is my package?" with current tracking data — across every carrier you ship with through Sendcloud.

> [!NOTE]
>
> Sendcloud shows up in the **customer panel** on a ticket. It does not create tickets or send notifications. The card itself only ever reads. An AI Agent can additionally cancel a parcel or create a return, but only if you add those actions to it, and both ask you for approval before anything happens — see [Use Sendcloud in AI Agents](#use-sendcloud-in-ai-agents).

## When to use it

Use Sendcloud when you create your labels in Sendcloud and your team often handles:

* "Where is my parcel?" and "When will it arrive?"
* "The tracking says delivered, but I didn't get it"
* Parcels that were not delivered, or are waiting for pickup
* Orders shipped with different carriers, where you would otherwise check each carrier's site

## Set it up

You need the **Public Key** and **Secret Key** of a *Sendcloud API* integration in your own Sendcloud panel. Creating one takes about two minutes and needs no approval from Sendcloud.

**1. Create your API keys in Sendcloud**

In the Sendcloud panel, open **Settings → Integrations**, find **Sendcloud API** and click **Connect**. Give it a name such as `Chatarmin CX`. Sendcloud generates a **Public Key** and a **Secret Key**.

Copy both now — Sendcloud shows the Secret Key only once.

**2. Open integrations**

[Open integrations](https://armin.cx/app/_/settings/integrations) from your workspace settings and choose **Sendcloud**.

If Sendcloud is not listed, contact your Chatarmin CX account team to enable it for your workspace.

**3. Connect your Sendcloud account**

Click **Connect**, enter the **Public Key** and **Secret Key**, and save. Chatarmin CX checks them with Sendcloud before saving. If Sendcloud rejects them, you see the reason and nothing is saved.

## Use Sendcloud in the inbox

When Sendcloud is connected, a **Sendcloud** card appears in the customer panel on a ticket. Expand it to see the shipments for the contact's most recent orders, newest first — up to five orders, and every parcel in them.

For each parcel the card shows:

* The current **status** and the **carrier** that is carrying it
* The **tracking number** and a link to the carrier's own tracking page
* The **expected delivery date**, when the carrier gives one
* The **delivery history**, newest first
* The **recipient** and the **items** in the parcel

The card is keyed to the contact: it finds the orders Chatarmin CX already knows for this customer and asks Sendcloud for their shipments. Nobody has to type an order number.

> [!NOTE]
>
> The card is only as good as the order link. On a ticket where Chatarmin CX cannot tell which orders belong to the contact — a social DM, for instance — the card shows a clean empty state rather than guessing.

### Recipient details

The recipient's name, address, email address and phone number, and the items in the parcel, appear only on a parcel that belongs to this ticket's contact. For any other parcel the card still shows the status, the carrier, the tracking link and the history, but leaves the recipient and the items out.

This is deliberate. Carrier tracking numbers are largely sequential, so without that rule the card would be a way to look up a stranger's name, address and phone number.

### What you see

| Situation | What the card shows |
| - | - |
| No linked orders on this ticket | "No Sendcloud parcels found for this customer" |
| Sendcloud has no shipment for those orders | The same empty state — a label may not have been created yet |
| Sendcloud is rate limiting | "Sendcloud is limiting requests right now. Try again shortly." with a **Retry** button |
| The API keys were rejected | "Sendcloud rejected this connection’s API keys. Reconnect it in the integration settings." |
| Sendcloud can't be reached | "Could not load Sendcloud parcels." with a **Retry** button |

Statuses are shown in your app language. If Sendcloud adds a status Chatarmin CX does not know yet, the card shows Sendcloud's own wording instead of a blank.

## Use Sendcloud in AI Agents

Add Sendcloud actions to an [AI Agent](https://docs.armin.cx/ai-agents/skills-and-actions.md) and select the Sendcloud connection each may use. Four are available, and you choose which ones the agent gets:

| Action | What it does | Approval |
| - | - | - |
| **Track shipment** | Looks up one order number — or one tracking number, when the order number is unknown — and answers with status, carrier, tracking link, expected delivery date and history. | Not needed; it only reads |
| **Get Sendcloud return link** | Returns the link into your own return portal for that parcel, which the agent can send the customer so they start the return themselves. | Not needed; it creates nothing |
| **Create Sendcloud return** | Creates a return and its label for a parcel the customer already received. | **Asked every time** by default |
| **Cancel Sendcloud shipment** | Cancels a parcel the carrier has not taken yet. | **Asked every time** by default |

> [!NOTE]
>
> **Create Sendcloud return** needs a **return shipping option code** on the action, because that decides which carrier you pay. Without one the agent cannot create anything: it stops and reports which codes your account offers, so you can set the right one. The free `sendcloud:letterreturn` option is useful for testing.

> [!WARNING]
>
> Carriers refuse cancellation once a parcel is manifested, and Sendcloud warns that shipping a previously cancelled parcel voids its insurance. The agent will not cancel a parcel that is already delivered, collected or returned, and says so instead.

Three limits are built in and cannot be configured away:

* An agent only ever sees and acts on shipments belonging to the customer in the conversation it is answering. Another customer's parcel reads as no parcel at all, and no write can touch it.
* An agent never sees recipient details or item lines, even for its own customer's parcel. It gets the status, the carrier, the tracking link, the dates and the history.
* In a test run, no write reaches Sendcloud at all — it is simulated.

> [!TIP]
>
> Prefer **Get Sendcloud return link** over **Create Sendcloud return** unless you want the agent creating labels on your account: it answers the same customer question and creates nothing.

## Data and access

For each lookup, Chatarmin CX sends Sendcloud only an order number or a tracking number. Your Public Key and Secret Key are stored encrypted.

Nothing is written to Sendcloud unless you add the **Create Sendcloud return** or **Cancel Sendcloud shipment** action to an AI Agent. Those are the only two writes this integration can make; both are approval-gated by default, and every one is recorded on the run with the parcel and action involved — never the customer's details.

## Change or disconnect Sendcloud

To change a connection, click it in [integrations](https://armin.cx/app/_/settings/integrations). Leave **Secret Key** blank to keep the current one.

To disconnect, open the connection's **Connected** menu, choose **Disconnect**, and confirm **Delete**. The Sendcloud card disappears from tickets, and any AI Agent actions using this connection stop working. Your shipments and your Sendcloud account are not changed.

## Troubleshooting

### The connection won't save

* Check that the **Public Key** and **Secret Key** are copied in full, without spaces.
* Make sure both come from the same *Sendcloud API* integration in your Sendcloud panel.
* If the Secret Key was lost, create a new *Sendcloud API* integration in Sendcloud and use the new pair.

### The connection says it needs reconnecting

Deleting the *Sendcloud API* integration in the Sendcloud panel invalidates its key pair. Create a new one and enter the new keys on the connection.

### The card is empty on most tickets

The card needs to know which orders belong to the contact. It will be empty where that link does not exist — most often on social DMs, and on orders from a shop that is not connected to Chatarmin CX.

### A parcel shows no recipient or items

That parcel is not the ticket contact's, as far as Chatarmin CX can tell. This is expected — see [Recipient details](#recipient-details).

If none of this helps, contact Chatarmin CX support. Include the ticket link and the time of the lookup, but not your Secret Key.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.