How to Get User-Identifying Names for Apps Like Spotify, Strava, and Eventbrite using Pipedream Connect without Separate Proxied API Calls?

This topic was automatically generated from Slack. You can find the original thread here.

Hey folks :wave:
We’re using Pipedream Connect and running into an inconsistency with the name field on account objects returned from GET /v1/connect/{project_id}/accounts.
What we’re seeing:
For some OAuth providers, name returns the user’s actual identity (email/handle), which is exactly what we want to display in our UI:
• Gmail →"[user@example.com](mailto:user@example.com)"
• Slack →"[user@example.com](mailto:user@example.com)"
For others, name just returns the app’s display name - not anything user-specific:
• Spotify →"Spotify"
• Strava →"Strava"
• Eventbrite →"Eventbrite"
What we expected:
We assumed name would always be a user-identifying value (email, username, handle) since that’s what the docs describe as “the custom name of the account if set.” For Spotify specifically, the account has the user-read-email and user-read-private scopes authorized, so the user identity is accessible - it just doesn’t seem to be surfaced in the account object.
Question:
Is there a way to get a user-identifying name (email, display name, etc.) for apps like Spotify, Strava, and Eventbrite without making a separate proxied API call to each provider’s /me endpoint ourselves? Is this something Pipedream could enrich automatically given the scopes are already granted?
Any guidance appreciated!

Will look into this - thanks

displaying some identifying information such as name or email , is the ideal but can’t be guaranteed and you shoulnd’t assume this.

Hey buddy , I reviewed the Shopify app, it needed a little tweak and now it should display the email when you connect the account. Same for Eventbrite. Let me get back to you later on Strava, need to check a couple of things