Troubleshooting
Below are some common errors when connecting your users’ accounts via Pipedream Connect.
and check the response for error messages.
Error creating a Connect token
Error creating token: Error: Failed to obtain OAuth token: Response Error: 401 UnauthorizedAuthorization to the Pipedream API failed when creating the Connect token. Double-check the client ID or secret for your Pipedream OAuth client.
Error connecting an account
Most errors when connecting an account are related to the Connect token, which Pipedream validates from the Connect iFrame.Common errors
This link has expired. Please request a new one from the app developer.
This session has expired. Please refresh the page to try again.
Troubleshooting steps
Pipedream typically returns an explicit error message in the HTTP response of the token validation network call directly from the iFrame in the client. To check for errors, start the account connection flow in a browser and open the developer console to view the network requests. Filter for requests toToken validation errors
The Pipedream Connect token is invalid. Please generate a new one and try again.Connect tokens expire, and are only able to be used once. Try generating a new token and try again.
App not found. Please check your app id.Double-check the app slug you’re passing when connecting your user’s account.
Connection failed. Please retry or contact support.
The user may have closed the OAuth popup window without completing authorization.Connect popup doesn’t open
If the Connect popup window doesn’t open, try settingCross-Origin-Opener-Policy (COOP) header to same-origin-allow-popups on the page that embeds the Connect iFrame.
The default COOP is unsafe-none; only make this change if you explicitly enforce same-origin. This relaxes isolation just enough to allow trusted popups (e.g., OAuth) to open from iFrames.
If you’re still have trouble or hitting an error that isn’t listed here, get in touch with us. We’d love to help.