The Cleo connector sends your shipping requests from the app to Cleo Integration Cloud. Cleo then forwards them to your warehouse management system (WMS), such as GoFlow, for fulfillment. Cleo accepts Pipe17’s shipping request format as is, so you don’t need to set up field mapping between the two systems.
With this connector, you can:
- Send shipping requests to your Cleo tenant automatically every 5 minutes.
- Send all shipping requests for one order to Cleo together.
- Create your Cleo warehouse locations in the app from a list in the connector settings.
- See Cleo’s validation errors on any shipping request that Cleo rejects.
Setup
Before you begin, make sure you have:
- An active Cleo Integration Cloud tenant that is set up to receive shipping requests from Pipe17.
- Your Cleo API base URL, for example
https://<org>-<env>-api.integrationplatform.io. - Your Cleo API key (
x-api-key). Your Cleo administrator can provide it. - The ID and name of each warehouse location that Cleo fulfills from.
To connect Cleo:
- Navigate to Integrations in the app.
- Click Add Integration, and then select Cleo.
- Enter your Cleo API base URL in the Cleo API base URL field.
- Enter your API key in the Cleo API key (x-api-key) field.
- Enter one location per row under Cleo locations, using the format
locationId:locationName(for example,SWIM-MAIN:SwimUSA Main Warehouse). - Toggle on Create locations from configuration and Push shipping requests to Cleo.
- Click Connect.
Settings
| Setting | Description | Options/Default |
|---|---|---|
| Create locations from configuration | Creates a location in the app for each entry under Cleo locations. If you remove an entry later, the app keeps that location. | On/Off. Default: On |
| Cleo locations | Your Cleo warehouse locations, one per row, in the format locationId:locationName. |
Free text, one entry per row |
| Default location ID | The location used when the app can’t determine a location for a shipping request. If you leave it empty, the app uses the first entry under Cleo locations. | Optional |
| Push shipping requests to Cleo | Sends shipping requests that are ready for fulfillment to Cleo. | On/Off. Default: On |
| Filter: order IDs | Sends only the shipping requests for the order IDs you list. Use this while testing. | Optional. Empty sends all |
Flows
| Flow | Direction | Notes |
|---|---|---|
| Locations | Settings → Pipe17 | Cleo has no locations API, so the app creates locations from your Cleo locations list. Runs every 5 minutes. |
| Shipping requests | Pipe17 → Cleo | Runs every 5 minutes. The app waits about 10 minutes after the last change to an order’s shipping requests, then sends them all to Cleo together. Accepted shipping requests move to Sent to Fulfillment. Rejected ones stay where they are and get an exception that lists Cleo’s errors. |
| Cancellations | Not supported | Cleo can’t receive cancellations. If you cancel a shipping request that Cleo already has, ask your warehouse or Cleo administrator to cancel it there. |
| Fulfillments and tracking | Cleo → Pipe17 | Your Cleo tenant sends fulfillments back to the app through the Pipe17 API. The connector itself doesn’t fetch them. |
Troubleshooting
A shipping request has a sync failure exception and wasn’t sent to Cleo
Cleo rejected it, and the exception lists the reasons, one per line. Fix the data the exception points to, such as an address or SKU. The app then sends the shipping request again on its next run.No shipping requests reach Cleo
Check that Push shipping requests to Cleo is on and that Filter: order IDs is empty unless you’re testing. Also check that the shipping requests are ready for fulfillment. The app also waits about 10 minutes after an order’s last change before sending.The connection fails or every request returns an authorization error
The API base URL or API key is wrong. Ask your Cleo administrator for the correct URL and key for your environment (staging or production), and then update them in the connection settings.Shipping requests are assigned to the wrong location
The app couldn’t match the shipping request to a location, so it used the default. Make sure every warehouse is listed under Cleo locations, and set Default location ID if needed. To learn more, see Getting Started with Locations in Pipe17.A canceled order still shipped
Cleo can’t receive cancellations from the app. Ask your warehouse to cancel the order directly in Cleo or the WMS.
Need Help?
If you need additional assistance:
- Use Ask Pippen, our AI agent, located at the top of the platform page.
- Submit a support request with as much relevant detail as possible. Learn how to submit a request.
We’re here to help you succeed with your operations.
Comments
0 comments