---
title: "Cancel the Sendcloud parcel when an order is refunded | FlowRunner flow"
description: "When an order is refunded, this flow finds its parcels in Sendcloud, cancels any the carrier has not collected, and tells the warehouse in Slack to pull the box."
url: https://flowrunner.ai/flows/sendcloud-cancel-parcel-on-refund
date_published: 2026-11-14
date_modified: 2026-11-16T14:50:08-08:00
---

# Cancel the Sendcloud parcel when an order is refunded

When an order is refunded, this flow finds its parcels in Sendcloud, cancels any the carrier has not collected, and tells the warehouse in Slack to pull the box.

## The prompt

When our store sends a refund for an order, find that order's parcels in Sendcloud and check each one's status. If the carrier hasn't collected it yet, cancel the parcel so the label is voided, and tell the warehouse in Slack to pull the box from the outbound stack. If it's already with the carrier or Sendcloud won't cancel it, tell support in Slack so they can arrange an intercept or a return.

FlowRunner Prompt to Flow built this flow from that request. Here it is as it opens in the editor.

## The flow

Inside the loop: For each parcel

[Import this flow](https://flowrunner.ai/downloads/prompt-to-flow/sendcloud-cancel-parcel-on-refund.json)

-   [Sendcloud](https://flowrunner.ai/integrations/sendcloud)
-   [Slack](https://flowrunner.ai/integrations/slack)

Download the file, then in FlowRunner click + beside Flows, pick it under Import a Flow Version and click Create. [How importing works](https://docs.flowrunner.ai/manage/flows#importing-a-flow)

## What each step does

1.  Refund comes in Your store or order system calls the flow when a refund is issued and sends the order number.
2.  Find the order's parcels Looks up every Sendcloud parcel created for that order number.
3.  For each parcel Runs the next steps once per parcel, so an order shipped in several boxes is handled box by box.
4.  Still in the warehouse? Reads the parcel's current status from Sendcloud. A parcel with no label yet, or with a label that has not been handed to the carrier, can still be stopped. Anything further along goes to support.
5.  Cancel the parcel Cancels the parcel in Sendcloud, which voids the label where the carrier supports it.
6.  Tell the warehouse to pull the box Posts the order number, recipient and tracking number to Slack so the box comes off the outbound stack.
7.  Tell support the parcel can't be stopped When the parcel has already gone, or Sendcloud or the carrier refuses the cancellation, posts the order, the parcel status and the tracking number to Slack, so support can arrange an intercept or a return with the customer.

## Need a custom refund cancellations automation? Our team can build it for you.

Tell us the process. Our implementation team at Midnight Flow builds it around how you work, tests it on your real data, and keeps it running, in your own FlowRunner workspace.

[Have us build it](https://midnightflow.ai/packages/custom?utm_source=flowrunner.ai&utm_medium=referral&utm_campaign=general&utm_content=flows.aside&utm_term=sendcloud-cancel-parcel-on-refund)

## Before you turn it on

-   Enter your Sendcloud public key and secret key, and connect your Slack account.
-   Copy the URL of the block Refund comes in into your store or order system as its refund webhook. It should send the order number as orderNumber, the same order number your Sendcloud parcels carry.
-   Pick your Slack channels in the two Slack steps: one the warehouse watches and one for support.

[Everything FlowRunner does with Sendcloud](https://flowrunner.ai/integrations/sendcloud)

---
Markdown version of https://flowrunner.ai/flows/sendcloud-cancel-parcel-on-refund. Site index: https://flowrunner.ai/llms.txt
