Hi , any word? Let me know if you need anything else from me.
Hey , thanks for reaching out. I’ll get back to you soon.
The issue is that when you’re running workflows for your end users, you need to configure your own OAuth client for the relevant apps that you’re using in that workflow (Eventbrite in your example).
So that means the user ID that you’re sending has a connected account that’s not using your OAuth client. How did you pass your OAuth app ID when your external user connected their account?
Hi ,
Thanks for this, appreciate the detail.
I’m not following. Please clarify.
I haven’t done this - to my knowledge:
How did you pass your OAuth app ID when your external user connected their account?
I’m new to Pipedream so please explain what you expect me to do to achieve this.
I have not yet wired my app to send the external_user_id. I am still troubleshooting/confirming being able to receive connected account data from Pipedream if I provide the relevant headers to a workflow’s trigger.
So, I’ve assumed that once I have the OAuth client configured for the ‘Select Eventbrite account’ in that code step, I can toggle the switch to “Use end user’s auth via Connect” button and then from curl send a request using the command I mentioned earlier.
Is that wrong? I’ve probably misunderstood something.
No worries — if it’s unclear to you, that means it’s probably unclear to others.
When you invoke a workflow where you’ve configured a step to “Use my end user’s auth via Pipedream Connect”, you have to pass in the external-user-id for your end user. The reason you do that is so that Pipedream knows which connected account to use when executing the Eventbrite step. So for that user, we are expecting an Eventbrite connected account to exist in your Pipedream project. And the connected account should have been connected using the OAuth client that you configured for Eventbrite.
• Check out the managed auth quickstart: Managed Auth Quickstart - Pipedream
• And also the info on OAuth clients in Connect: OAuth Clients - Pipedream
Those might provide additional info that’s helpful.
Thanks so much for this, .
I’ve gotten to the bottom of it.
Basically, when I was checking out Pipedream Connect, I decided to bootstrap creating a custom OAuth client by using an LLM and now I can see it missed out some essential information, like the connect_link query param.
At the time I didn’t fully understand how the managed auth flow was supposed to work so I assumed I could troubleshoot issues with the faulty OAuth client by fetching data directly from connected accounts via curl.
And that’s when I posted my first call for help.
I’ll fix my OAuth client to generate the connect link properly and then I should be able to fetch data into my app as I know the workflow and trigger are working properly.
Thanks again for all your help - it’s been really informative.
Your speed at responding is inspiring.
