App slugs will always use underscores
got it I checked the url slug of that page, without realizing there is that section at the bottom, veyr helpful to know for future integrations!! Thank you 
Yea, it’d be nice if they were more discoverable, but most Connect devs also just end up getting the relevant slug from the API
haha yeah that makes sense!
now is it true, that if a user connects with the pipedream modal successfully, that essentially on the front end I dont need to capture anything else? All I need from that point is the external_cutomer_id? if so that is super awesome.
It depends what you’re doing w/ the auth. In the components API and the Connect Proxy, you do need to pass their account ID, which you can get in a callback upon successful connection, but you can also always get that from the accounts API.
got it! I love how smooth the DX here is. Airbyte needs to take a page out of you guys book.
Thanks! 
Definitely let me know if you have asks or feedback!
question if a customer authenticates their google ads, is there any way for me to retrieve just their google ads customer id?
Because some endpoints require that in the body payload
How are you sending the request? Are you using the Connect proxy? Or just directly from your app to Google?
Im using the Connect Proxy.
So I:
- generate connect token on the frontend
- user authenticates
- it returns the accountId (which I store and use later)
But now I need to make proxied requests, which some pipedream handles fine, but in some cases I need to pass the customer_id from google ads in the body.
Nevermind I think Im thinking of this wrong. When a user signs in, and authenticated we get access to allthe different google ads accounts for that user. So I just need to make a request to a list CustomerId’s endpoint or something similar.
I think you typically need to send the customer ID for Google Ads via header, right?
Hmmm, its saying I need to pass in a developer access token; but my understanding is that Pipedream takes care of that right?
(I show it here in 1 minute 50 second loom Arc - 17 March 2025 | Loom)
Yea Google Ads specifically is an interesting one, since in our integration even outside of the Connect proxy, we proxy all the requests, so that we can include the developer token from our server. So actually the target URL for you should be our proxy endpoint, which is currently
https://eolid4dq1k0t9hi.m.pipedream.net
Here’s some more info — Google Ads is a pretty unique integration in that regard, it’s non-standard in Pipedream:
ohhh I seee
that makes sense. The only thing that I’m not seeing there is, where do I pass in the external_id, and the account_id of pipedream, or are they no longer needed here?
Let me show you a basic request structure that I think should work
Are you using the SDK or REST API?
Oh right, REST
yeah rest