Why does Ecwid app integration only process 'Paid Orders' when Zapier can choose Payment and Fulfillment Status?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Can somebody tell me why there is only ‘Paid Orders’ processing for Ecwid app integration? Zapier has the ability to choose Payment Status and Fulfillment Status…

2

If you’d like to see a trigger or action that we don’t yet have, feel free to submit a request here: New Pipedream Integration Request

3

Yes, but I will wait for that too long. I need it now. Shame, your app shows wast improvements over Zapier.

4

To confirm, are you looking for additional filters (props) to apply to the existing Ecwid trigger?

5

Yes, I need to filter Orders by payment status and fulfilment status - use case: suppose I have Cash On Delivery service, Ecwid will not automatically set the order to Paid on creation, it will be Awaiting Payment. Paid is only applicable when customer pays with card, online…

6

And you want to trigger your workflow on new orders with specific payment and fulfillment statuses? Or you want to fetch the payment and fulfillment status within a workflow that is triggered from a different event?

7

I want to trigger workflow on Payment Status. Fulfilment status is currently not that important, but it would also be nice to be able to filter orders based on it.

8

Gotcha. So if a new order comes in, you want to trigger your workflow only for certain a payment status?

9

Correct

10

For the reasons I explained earlier.

11

Thanks for the info. Here is a ticket for us to track the development: [TRIGGER] New Order Received · Issue #6251 · PipedreamHQ/pipedream · GitHub

12

Feel free to subscribe to that issue, we’ll post updates there