Yea I think literally the only thing that needs to change is instead of https://googleads.googleapis.com
as the base URL, you’ll use https://eolid4dq1k0t9hi.m.pipedream.net
So you send it to https://api.pipedream.com/v1/connect...
and the base 64 encoded base URL you append will use the Pipedream endpoint instead of googleads
, then you’ll still include the relevant path for Google Ads API, and also the same query params, etc
got it!
I tried doing that:
But I got the following error
{
"error": "param `url` or `path` should be a string"
}
URL: https://api.pipedream.com/v1/connect/proj_nasVEYW/proxy/aHR0cHM6Ly9lb2xpZDRkcTFrMHQ5aGkubS5waXBlZHJlYW0ubmV0L3YxOS9jdXN0b21lcnM6bGlzdEFjY2Vzc2libGVDdXN0b21lcnM?external_user_id=7e67fd1b-5642-4362-8b46-96f3d32a2588&account_id=apn_z8hxday
USed this for the Encoding:
urlToBase64UrlSafe('https://eolid4dq1k0t9hi.m.pipedream.net/v19/customers:listAccessibleCustomers')
function urlToBase64UrlSafe(url) {
// Regular Base64 encoding
const regularBase64 = btoa(url);
const urlSafeBase64 = regularBase64
.replace(/\+/g, '-')
.replace(/\//g, '_')
.replace(/=+$/, '');
return urlSafeBase64;
}
I see your requests in our logs, checking out why it isn’t working as expected
Thank you so much! I’ll be stepping out for about an hour, but, I will check back in once I come back, really appreciate the help!!
Okay I see the issue, I’m trying to figure out how to make it work
awesome thank you!
Alright, we had to make a slight change to the Google Ads proxy on our end, but here’s an example of how it works, I just tested end to end:
Amazing it works! Thanks so much!!
and I assume if we have an endpoint that requires a post and a body, we would just add body to the googleAsReq correct?
Exactly, you modify the method that you’re passing there and add the body, like
const googleAdsReq = {
method: "post",
url: "/v19/customers:listAccessibleCustomers",
body: {
foo: "bar",
}
}
Are there other apps you’re looking to access via Connect and with the Connect proxy?
that makes sense!
Thanks for asking! At the moment just Facebook Ads, but I know that has been left in a pending stage for now due to facebook ads approval requirements
But now that I’ve gotten the hang of pipedream connect, I know there will be more soon
Nice. Do you know roughly how many users you intend to use the proxy with?
For Google Ads, very little right now maybe 10 or so. But we are going to run it every 15 minutes. At it’s peak we hope to have roughly 250-350 users running this. every 15 minutes
Got it — have you chatted w/ our sales team about shipping to production already? It’s all free in development, but requires a subscription when you’re ready to ship to prod.
I have actually@
I will definitely be upgrading to the paid plan here soon, and may eventually elect to use the business plan too