I have a Webhook Request workflow that makes an authenticated POST to our Heroku pipeline. I use Pipedream’s OAuth integration with Heroku to manage the access token for authenticating this request.
I started getting 401 errors for invalid credentials, and the Heroku account on the Connected Accounts page has a status of “unhealthy”. When I try to reconnect the account, I get the OAuth popup as expected but no matter how I sign in to Heroku it doesn’t appear that it reaches Pipedream.
Example 1 - I’m already logged into Heroku in a separate tab:
The popup appears with a “Couldn’t find that registered client” error message
If I enter my credentials and log in, I get redirected to the Heroku dashboard within the popup and the window just hangs out there. No callback or redirect to Pipedream seems to happen
Example 2 - I am not already logged into Heroku in another tab:
The popup appears with a bizarre “Page Not Found” error message
This is happening both when I try to reconnect the existing account or when I try to create a new connection to Heroku. It might be a coincidence, but this started happening right around the time Heroku began requiring MFA for all accounts. I do go through the step of entering a TOTP in the OAuth popup - I wonder if that could have something to do with it?
PS - I’ll reply with more screenshots since I guess I’m limited to 1 per post
Thank you so much for raising this issue. I can reproduce your issue and created a bug ticket here for Pipedream team to triage. Kindly subscribe to the ticket to be noticed when the issue is fixed!
I can confirm that I can reconnect the account successfully now! Thank you so much for such a quick turnaround on this - it’s a HUGE benefit for my project workflow!
Hey, I’m sorry to reopen this but I’m hitting a roadblock with the scope permissions that the OAuth is asking for. Previously it gave us a token with global permissions, but now it gives us a token with identity, read, write permissions.
Is there a way for me to specify a global permission set? Our webhook appears to fail when it hits Heroku due to insufficient permissions Build failed to start: The scope of this OAuth authorization does not allow access to this resource.
Ah, sorry about that. I didn’t realize webhooks required the global scope. That does not appear to be documented on their side. Can you try reconnecting your account, then try to create the webhook trigger again?
Excellent, it’s working just like before. Yeah Heroku’s docs aren’t very clear about this, I wouldn’t have thought it would require global permissions but apparently it does.
Again, thanks a bunch for the lightning quick response!
