I’ve had a WooCommerce REST API integration running smoothly for over a year. It broke today and I suspect a Woo update caused it.
Even if I try to add a new Account source with a fresh Woo API key, it fails to set up the new account. Could this be because Pipedream is using v2 of the API and v3 is the latest and greatest?
@philippedubs Are you seeing a specific error in that last example step? Are you able to visit your workflow’s Settings and enable the setting to share the workflow with Pipedream Support? I’d like to see the logs from that run.
Do you operate a firewall or any kind of network rules that would block connections from specific IP addresses? Or do you use a service like Cloudflare in front of your Wordpress instance that would reject network requests from Pipedream? If the request is timing out completely, that may be related.
Cool to get support from the top dog (on a holiday no less).
I just enabled support access, it’s my client-thd-order_emails workflow. I used the Pipedream auths manager up to v68 (that’s what worked for 1yr). Today I did a few new versions trying to hardcode the auth details, moving the order number to the URL, etc.
Again, I can confirm that this website is accepting requests and returning data when I test outside of Pipedream (including axios on my local).
I also tried to do basic auth to the same Woo site in one of my clients Pipedream accounts to no avail… this client has no legacy Pipedream v1 workflows so I thought that may help…