PipedreamHQ / PipedreamHQ/pipedream

NinjaOne

Open
#21,248 0 comments 0 reactions 1 assignee Claimed by @sergio-eliot-rodriguez View on GitHub
bug triaged user request
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

### App
NinjaOne

### Summary:
NinjaOne OAuth Connect flow returns WEB_MGMT_SERVICE HTTP 404 before Pipedream callback returns a connected account ID.

### Details:
We are seeing a customer-facing failure when connecting the NinjaOne integration through Pipedream Connect in our production project.

Pipedream account email: joseph@american-productivity.com
Pipedream project: proj_36sGpzP
Environment: production
App slug: ninjaone
Observed app id from apps.list: app_z6hGeN
APC externalUserId / connection id: 41ecaceb-723d-4980-bf3d-c8c98d411147
Customer-facing incident id: WEB_MGMT_SERVICE-a7e6b64d500345c3ba44bb0b534e10e52-1782397628-YPBUCEPL
Customer-facing error: {"resultCode":"FAILURE","errorMessage":"HTTP 404 Not Found","incidentId":"WEB_MGMT_SERVICE-a7e6b64d500345c3ba44bb0b534e10e52-1782397628-YPBUCEPL"}

Timeline in UTC on 2026-06-25:
- 14:26:52 /api/connections/initiate returned 200 for app ninjaone and connection id 41ecaceb-723d-4980-bf3d-c8c98d411147.
- 14:26:54 /api/connections/pipedream-token returned 200.
- No /api/connections/pipedream-callback request occurred afterward, so our app never received an apn_* connected account id.
- The Supabase connection row remains status=initiating with provider_account_id=pending_1782397614100 and unchanged updated_at.

Additional checks:
- Production shared Pipedream bearer token state is healthy for project proj_36sGpzP: status=valid, no retry_after_until, no last_error.
- apps.list can see NinjaOne in the production project as app_z6hGeN / slug ninjaone / authType oauth.
- We are not passing a custom oauthAppId; we appear to be using Pipedream's official OAuth client for NinjaOne.

Can you please trace the incident id above and confirm whether Pipedream's official NinjaOne OAuth client / redirect URI / region configuration is currently valid for Connect production? If APC needs a custom OAuth client for NinjaOne, please send the exact oauthAppId flow requirements and redirect URI that should be registered in NinjaOne.

### Screenshots:
No screenshots included

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.