This topic was automatically generated from Slack. You can find the original thread here.
Hey Pipedream team 
We’re seeing a hard failure connecting NinjaOne through Pipedream Connect in production.
Context:
We use Pipedream Connect with the browser SDK flow:
- Our backend creates a Connect token
- Frontend calls
connectAccount({ app: "ninjaone" }) - We expect
onSuccessto return a Pipedream connected account ID (apn_...)
What we’re seeing:
The Connect token request succeeds, but the NinjaOne OAuth/authorization flow fails beforeonSuccessfires. Our app never receives a connected account ID, so the connection remains stuck in an initiating/pending state.
Customer-facing error:
{
"resultCode": "FAILURE",
"errorMessage": "HTTP 404 Not Found",
"incidentId": "WEB_MGMT_SERVICE-a7e6b64d500345c3ba44bb0b534e10e52-1782397628-YPBUCEPL"
}
Why we think this is in the Connect → NinjaOne OAuth step
• Our /pipedream-token request returned 200
• connectAccount never reached onSuccess
• We never received an apn_... account ID
• apps.list can see NinjaOne in our prod project as app_z6hGeN, slug ninjaone, auth type oauth
• We are not passing a custom oauthAppId; we appear to be using Pipedream’s official NinjaOne OAuth client
Impact:
This is blocking a production customer from connecting NinjaOne and they’re cranky about it
Questions:
- Can you trace the incident ID above on your side?
- Is Pipedream’s official NinjaOne OAuth client currently working for Connect production?
- Does NinjaOne require region-specific OAuth / redirect URI configuration that Connect needs to account for?
- Should we be using a custom OAuth client for NinjaOne instead? If so, what exact redirect URI and setup should we register?
Happy to follow up in DMs. Thanks for the help!