# Unsure of best way to set up Click Up \>\>Shipstation to create an order then Shipstation \>\> Click Up to return update **URL:** \ **Category:** Questions\ **Created:** [June 13, 2023, 1:11pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094 "2023-06-13T13:11:36Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![BlackSparrow](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/blacksparrow/32/14759_2.png) [@BlackSparrow](https://community.make.com/u/BlackSparrow)\ **Post date:** [June 13, 2023, 1:11pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/1 "2023-06-13T13:11:36Z")
I dont have screenshots… I have a scenario currently set up and working well that does the following: Listens for new tasks in click up \> Gets task info when created \> Creates an order in Shipstation What I am not sure of is how to then update my task in Click Up once an order is shipped in Shipstation. What I need is: Shipping Label Created in Shipstation, and status changed to Shipped \> Update task in Click Up Im not sure the best way to map it back to the correct task. Any help would be appreciated. TIA ---
**Author:** ![Runcorn](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/runcorn/32/9169_2.png) [@Runcorn](https://community.make.com/u/Runcorn)\ **Post date:** [June 13, 2023, 1:45pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/2 "2023-06-13T13:45:43Z")
Hi @BlackSparrow, It would have helped if you have the scenario mapping as part of the screenshot. What you can do is, 1. Setup a new scenario 2. Add [Listen for Shipment Events (With Item Info) ](https://www.make.com/en/help/app/shipstation#listen-for-shipment-events--with-item-info-_body) as the First Module, that will basically listen for new updates in the Shipstation 3. Search Clickup based on data received from Shipstation 4. Update Clickup Item Not sure what events are received from the Shipstation, so it might be a good idea to add a filter after first module to only track the relevant status that you are looking for. ---
**Author:** ![Runcorn](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/runcorn/32/9169_2.png) [@Runcorn](https://community.make.com/u/Runcorn)\ **Post date:** [June 13, 2023, 1:48pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/3 "2023-06-13T13:48:00Z")
> [@BlackSparrow](#): > > status changed to Shipped My bad, the current integration doesn’t support that for Listen for Shipment Events (With Item Info). Instead what you can do is, use Webhooks as the first module in make, Grab the generated URL and then setup the Shipstation Webhook as described [here](https://help.shipstation.com/hc/en-us/articles/360025856252-ShipStation-Webhooks). Rest of the step will be the same, I hope they do support Shipped Webhooks. ---
**Author:** ![BlackSparrow](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/blacksparrow/32/14759_2.png) [@BlackSparrow](https://community.make.com/u/BlackSparrow)\ **Post date:** [June 13, 2023, 2:05pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/4 "2023-06-13T14:05:25Z")
@Runcorn Thank you for the quick reply. I’ll give it a shot. ---
**Author:** ![BlackSparrow](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/blacksparrow/32/14759_2.png) [@BlackSparrow](https://community.make.com/u/BlackSparrow)\ **Post date:** [June 13, 2023, 2:14pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/5 "2023-06-13T14:14:15Z")
What do mean by #3? How would I set that “based on” up? ---
**Author:** ![Runcorn](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/runcorn/32/9169_2.png) [@Runcorn](https://community.make.com/u/Runcorn)\ **Post date:** [June 13, 2023, 2:17pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/6 "2023-06-13T14:17:06Z")
For that, either you need to modify your original scenario, so the task is updated once the Label is generated on ShipStation, you can add a shipStationID or the label, which then you can use in this step to search ClickUp ---
**Author:** ![BlackSparrow](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/blacksparrow/32/14759_2.png) [@BlackSparrow](https://community.make.com/u/BlackSparrow)\ **Post date:** [June 13, 2023, 2:39pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/7 "2023-06-13T14:39:30Z")
@Runcorn - I really appreciate the help. I guess it is the “search” step I’m a bit confused about. Still new to MAKE. Right now Click Up generates an ID that is passed to ShipStation as the Order # when the order is created. is the “search” looking to match the order # back to the Click Up ID in order to update the correct one? I understand that concept, I am not sure how to “search ClickUp”…this is my existing scenario ![Screen Shot 2023-06-13 at 10.36.01 AM](https://europe1.discourse-cdn.com/flex013/uploads/make/original/2X/1/1bff4ca7a542265d242b77e71f47d7df406499ca.png) ---
**Author:** ![Make\_Bot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/make_bot/32/14661_2.png) [@Make\_Bot](https://community.make.com/u/Make_Bot)\ **Post date:** [December 7, 2023, 5:49pm UTC](https://community.make.com/t/unsure-of-best-way-to-set-up-click-up-shipstation-to-create-an-order-then-shipstation-click-up-to-return-update/12094/8 "2023-12-07T17:49:43Z")
This topic was automatically closed because it's resolved or inactive. Please, start a new topic.