Why Does the <http://Wordpress.org|Wordpress.org> Component Encounter a 401 Issue on Pipedream but Not on Zapier?

Bugs
1

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

hey guys, we’re getting an issue with authentication in the Wordpress.org (self hosted) component. We’re using the exact same website_url, name, and app_password for both Pipedream and Zapier. It works for Zapier, but any POST or PUT request we make gives a 401 issue. Have you encountered this before?

2

Hey , on Pipedream, you will need to remove the protocol in your Domain field, for example, you will input [example.com](http://example.com) instead of https://example.com

3

Hey Leo! We did put in the example.com version. It’s working for GET requests, but not for any PUT or POST requests

4

Hmm, this is weird though. Could you share the specific actions you’re using on Pipedream? And I assume the same action works on Zapier right?

5

Yeah this is the one I’m trying to use:

{
  externalUserId: "demo-72ca2c60-b534-47df-918d-397fc38ab5f8",
  page: 0,
  componentId: "wordpress_org-update-post",
  propName: "post",
  configuredProps: {
    wordpress: {
      authProvisionId: "*****"
    }
  }
}

and now it’s giving this error when trying to configure the prop for the posts to update:

{
  error: {
    code: "UserError",
    message: "bad options response for prop: post",
    ts: "2025-10-08T01:40:25.431Z",
    name: "UserError"
  },
  userError: true,
  errors: [
    "{"code":"UserError","message":"bad options response for prop: post","ts":"2025-10-08T01:40:25.431Z","cellId":null,"stack":null,"$debug":null,"name":"UserError"}"
  ],
  observations: [
    {
      ts: 1759887625423,
      k: "error",
      err: {
        name: "Error",
        message: "Autodiscovery failed",
        stack: "Error: Autodiscovery failed
    at /pipedream/dist/code/0d406664d640ea4b822cb4e24ff427b0219afed4cac8c37bb7c0f161059df70c/node_modules/.pnpm/wpapi@1.2.2/node_modules/wpapi/wpapi.js:465:10
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.getClient (file:///pipedream/dist/code/0d406664d640ea4b822cb4e24ff427b0219afed4cac8c37bb7c0f161059df70c/code/wordpress_org.app.mjs:184:16)
    at async Object.listPosts (file:///pipedream/dist/code/0d406664d640ea4b822cb4e24ff427b0219afed4cac8c37bb7c0f161059df70c/code/wordpress_org.app.mjs:207:18)
    at async Object.options (file:///pipedream/dist/code/0d406664d640ea4b822cb4e24ff427b0219afed4cac8c37bb7c0f161059df70c/code/wordpress_org.app.mjs:134:23)
    at async /var/task/node_modules/@lambda-v2/component-runtime/src/configureProp.js:82:13
    at async captureObservations (/var/task/node_modules/@lambda-v2/component-runtime/src/captureObservations.js:28:5)
    at async configureProp (/var/task/node_modules/@lambda-v2/component-runtime/src/configureProp.js:81:22)
    at async file:///var/task/component_maker.mjs:191:11"
      }
    }
  ],
  timings: {
    lambda_configure_prop_called: 1759887625291,
    lambda_done: 1759887625423
  },
  t: {
    ar: 1759887625083,
    br: 1759887625221,
    bp: 1759887625221,
    bls: 1759887625221,
    ble: 1759887625431,
    lcp: 1759887625291,
    le: 1759887625423
  }
}
6

any idea what could be causing this? We have a client waiting on this automation, and the proxy doesn’t seem to be working either

7

Hey , so I see you’re using Pipedream connect.

Could you share your full code using pipedream connect sdk/api if possible?

Aside from that, here’s a document you can refer to for Pipedream Connect API Proxy: Connect API Proxy - Pipedream

8

So the error I sent was happening via the Pipedream sdk demo site

9

I was testing there to ensure it wasn’t an issue on our end. I confirmed the credentials were correct because they were working well on Zapier, and I double checked that everything was input correctly for the integration on Pipedream

10

Got it , thank you for your information.

I’ll check and get back to you.

11

Thank you!

12

hey any updates here? Is there anything we can do on our end to fix the authentication issue?

13

it appears that there is a wordpress plugin that needs to be added for this to work from Zapier, do you know if something similar needs to be done for Pipedream?

14

Hey , thank you for the information. I have trouble reproducing this on my side.

My educated guess is that the Zapier plugins overrides some of the protection on your Wordpress instance, hence, it can by-pass the security checks. While Pipedream uses the API as is, so it failed the default security checks.

What is your wordpress version?

15

Thank you for giving it a shot! I believe it is 5.6.2 let me double check

16

okay completely wrong it is 6.8.3

17

Hosted on Cloudflare, my running theory is that Cloudflare is stripping the Authentication header and thus showing unauthorized even though the auth would be valid

18

Got it, I’ll take some time to dig further.

I tested selfhost Wordpress on AWS LightSail with App Password enabled (via a plugin) and it works on my side.

So this might not be within Pipedream control.

19

Sounds good, I appreciate it. I’ll see what we can do on our end. Thanks so much!