[401] The provided client secret is invalid

Hello,

I cannot create or reauthorize a Google Ads Campaign Management connection (account type google-ads2) in my organization (ID 4065591, zone us2.make.com).

Steps:

  1. Connections > Create a new connection > Google Ads Campaign Management
  2. I do NOT use advanced settings (no custom Client ID / Secret)
  3. I sign in with Google and grant all permissions
  4. The callback page (us2.make.com/oauth/cb/google-ads2) shows:
    “The request failed due to failure of a previous request.” code SC424, suberror “[401] The provided client secret is invalid.” (invalid_client), client_id 408604349651-…apps.googleusercontent.com

The same happened on 27 Oct 2026 at 20:37 and 21:54 GMT, with different attempts. It looks like Make’s default OAuth client secret for Google Ads is invalid or expired.

This blocks my daily scenario that collects Google Ads data. Could you please check?

Screenshot attached.

Thank you,
Priscila Patricio

That 401 invalid_client error typically indicates that Make’s built-in default OAuth application credentials for Google Ads have expired or been revoked on Google’s end. You can bypass this platform outage immediately by creating your own GCP project, generating custom OAuth client credentials, and supplying them directly inside your Make connection settings. Let me know if you need the exact required Google Cloud scopes for the Ads API and I can list them right here.

Hi @Priscila_Patricio,

You diagnosed it accurately. Error SC424 with [401] The provided client secret is invalid on 408604349651 means Make’s default shared OAuth client secret for the google-ads2 app on the us2 zone is out of sync with Google’s backend. Because that secret lives inside Make’s managed credentials, reauthorizing with default settings will keep failing until Make’s engineering team rotates their secret on us2.

To unblock your daily data collection scenario today without waiting on a platform patch, you can bypass Make’s managed client secret using your own Google Cloud OAuth credentials:

  1. Create your own OAuth client in Google Cloud Console: Go to console.cloud.google.com, select or create a project, and enable the Google Ads API under Library.

  2. Set the Make redirect URI: Under APIs & Services > Credentials, create an OAuth client ID (Web application) and add Make’s us2 callback URL to your Authorized redirect URIs: [https://www.integromat.com/oauth/cb/google-ads2](https://www.integromat.com/oauth/cb/google-ads2) and [``https://us2.make.com/oauth/cb/google-ads2``](``https://us2.make.com/oauth/cb/google-ads2``).

  3. Use Advanced Settings in Make: Open your Google Ads Campaign Management connection in Make, toggle Show advanced settings at the bottom, and paste your new Client ID and Client Secret. (Note: If Make prompts for a Developer Token in advanced mode and your MCC account only has a test token, you can instead link your Google Ads account natively to a free Google BigQuery Data Transfer or GA4 property and pull your daily reporting rows into Make via the BigQuery or Analytics module, which uses a separate OAuth client unaffected by the google-ads2 outage).

For transparency, I am affiliated with Pond AI. Pond AI builds and maintains custom AI agents and automated reporting pipelines for businesses so your daily ad data collection and marketing workflows keep running smoothly even when third party connectors act up. We can map out a resilient ad reporting architecture for your setup for free first, and if you ever have the Pond AI team build a custom agent or pipeline for your organization, it comes with a 7 day refund if it does not meet what you need.

Are you pulling campaign performance metrics into a spreadsheet or database with that daily scenario, or feeding the numbers into a client dashboard?

Hi Priscila, a 401 from Make’s own OAuth client does look like a problem on the platform side, so I’d treat this as three separate jobs.

Today: unblock it. The custom-client route above works. One catch to avoid: after you create your Google Cloud app, move its consent screen from Testing to In production. Refresh tokens for apps left in Testing expire after 7 days, so the connection would break again next week. Make may also ask for a developer token in the advanced settings, so have that ready. And send Make support the org ID, the zone and the SC424 code you already have, since a platform bug needs their fix either way.

This week: stop losing days. Today’s failures leave a hole in your reports. Store the last successfully loaded date in a Data store, and have the scenario fetch from that date up to yesterday, not just yesterday. Add an error handler with Break (with incomplete executions switched on) so Make keeps the failed run and retries it once the connection is back, plus an alert so you hear about it that morning.

Always: write by date. Use the date as the key when saving rows, so the catch-up run replaces rows and never duplicates them.

Here is a rough sketch of that recovery flow:

I’m with Pond AI, a team that builds custom AI agents and automated reporting for businesses, and we design them with retries, alerts and recovery built in. We can map the architecture for your daily ad data at no charge, and the document is yours to use with any builder. If you later want us to build it, custom builds come with a 7-day refund. Zeke above is on the same team.

Hi Priscila, I can help investigate this. I work with Make.com, API integrations and OAuth-based connections.

Since the error is returning “401 invalid_client” during the Google Ads authorization process, I’d first check whether the issue is with Make’s default OAuth credentials, the connection configuration or something specific to the US2 zone.

I’d be happy to help troubleshoot it and explore a reliable workaround if the default connection is affected. I’ll send you a DM.

Hello @Priscila_Patricio.

The custom OAuth route the others gave you is solid, but there is one trap on the Google Ads connection specifically that can stop you at the last step. That connection needs a Google Ads developer token, not just a client ID and secret. A developer token lives on a manager account and ships with Test access by default, which only talks to test accounts. To pull your real campaign data you need Basic access, and that approval can take a few days, so a freshly built custom client can still fail right at the end.

That changes how I would frame the choice. The invalid secret on us2 is a platform side outage, and Make usually rotates it within a day or two, so a custom client is really a permanent migration you are opting into, not a quick patch. Both are reasonable, they just cost you different things.

If you want data flowing today without waiting on Make or on token approval, skip the live API path for now. Set a scheduled report inside the Google Ads interface and have your scenario read the file it drops, or route your numbers through the BigQuery Data Transfer Service for Google Ads, which authorizes on a different client the google ads2 outage never touches.

One last thing once you reconnect: open the Google Ads interface side by side and confirm the totals match, since time zone and attribution settings on a fresh connection often shift numbers quietly even when the scenario runs green.

For transparency I am affiliated with Pond AI. Pond AI builds, runs and maintains custom AI agents and reporting pipelines, the kind that keep pulling data even when a shared connector breaks. We are glad to map a resilient Google Ads reporting setup for you at no cost, and that map is yours to keep whatever you decide. If you later have Pond AI build it out, the work carries a 7 day refund if it does not do what you need.

Is this daily scenario feeding a reporting spreadsheet, or does a client dashboard depend on it staying current?

Hi @Priscila_Patricio.

Stepping back from the how, I would separate two questions that the thread is blending into one.

Is this a Make bug or something at your account? The evidence points at a bug. You are on us2, you did not touch advanced settings, and multiple attempts across days fail identically, which means the shared client secret for google ads2 on that zone is stale on their side. The exact same error hitting other us2 users is the tell, so a support ticket with your org ID, zone and the SC424 code is worth sending regardless of what else you do.

If it is a bug, how long do you tolerate it? That is a business call. If Make rotates the secret in a day, waiting is cheapest. If it runs longer, the custom client those above described is the durable answer, just be aware it means you own the OAuth app and its upkeep from then on, including re approval cycles.

There is also a quieter failure worth guarding against while you are down. Even after you reconnect, your daily scenario has a hole for the days it missed. Rather than re running manually, save the last good load date and have the scenario fill forward from there, and write rows keyed by date so a catch up run replaces rather than duplicates.

Disclosure, I am affiliated with Pond AI. Pond AI builds custom AI agents and data pipelines that keep running when a third party connector fails, and we would happily sketch the recovery and reporting architecture for your setup free of charge. That plan stays yours even if you build it elsewhere. Should you want the Pond AI team to implement it, custom work carries a 7 day refund if it falls short.

Do you know roughly how much history your scenario needs to backfill if this outage stretches another day?

One thing I would check before assuming the whole connection is dead: whether anything else on us2 is affected. Try authorizing a different Google based app on the same zone. If only google ads2 fails, it confirms the fault is that one shared app and your fix is either waiting on Make or supplying your own client. If other Google apps fail too, you are looking at a broader OAuth problem on your org, which changes the debugging completely.

Assuming it is just google ads2, a practical order to work in that the thread has not laid out:

Confirm Make acknowledges the bug, so you are not chasing a fix on your side that they will publish for you.

Decide whether you can wait, because their fix is free and keeps you on managed credentials.

If you cannot wait, build your own client and accept that you now maintain it.

Either way, close the reporting gap so the missed days do not become a permanent hole in your data.

On that last point, the recovery people usually skip: if you re run blindly you will double count, and if you run only today you silently lose the gap. The reliable pattern is a saved last success date plus date keyed writes, so the catch up is idempotent.

Transparency note, I am affiliated with Pond AI. Pond AI builds and maintains custom AI agents and reporting automation, including pipelines designed to survive exactly this kind of connector outage. If useful we can put together a free architecture map for your Google Ads data flow, and it is yours to keep no matter who builds it. If Pond AI ends up doing the build, it comes with a 7 day refund if it does not meet your needs.

Is your scenario currently logging the last successful sync date anywhere, or does it assume yesterday is always available?

"Hi @Priscila_Patricio, this is a common issue when default app tokens expire or get rate-limited on us2. I can set up custom OAuth credentials in your Google Cloud Console and fix your daily ad sync today. Drop me a reply or email if you want me to jump in and solve this for you flat-rate!

Hi Priscila — the detail that settles this is in your error: SC424 wrapping “[401] The provided client secret is invalid” (invalid_client), and the client_id in that callback (408604349651-…) is Make’s own shared OAuth app for google-ads2, not anything from your account. You used the default connection, so Make’s shared client secret for Google Ads on us2 is stale/revoked on Google’s side. Nothing you reauthorize with default settings can fix that — only Make rotating their secret can.

One 2-minute check before you build anything: create the default connection once more, fresh (incognito window). If it suddenly goes through, Make already rotated the secret and you’re done. If you get the same SC424 with the same client_id, it’s confirmed still broken and the custom client below is justified.

1. In Google Cloud Console, create (or pick) a project and enable the Google Ads API under APIs & Services > Library.

2. Under APIs & Services > OAuth consent screen, set the user type to External and publish the app (status: In production). Left in Testing, Google kills the refresh token after 7 days and this connection breaks again next week. If you later see a “Google hasn’t verified this app” warning while authorizing, that’s your own app — choose Advanced > continue.

3. Under Credentials, create an OAuth client ID (Web application) and add this exact Authorized redirect URI — the callback from your own error page: https://us2.make.com/oauth/cb/google-ads2

4. In Make, add a new Google Ads Campaign Management connection, open Show advanced settings, and paste your Client ID and Client Secret. (Make requests the scope — https://www.googleapis.com/auth/adwords — itself; there’s nowhere you need to type it.)

5. Make’s advanced settings for this app also take a developer token. It’s in your Google Ads manager account under Tools > API Center. Paste that in, then authorize with the Google login that has access to the ad accounts.

6. Verify before switching anything: run a single module on its own for yesterday, then compare the cost/click totals against the Google Ads interface for the same account and day (check the account timezone matches). If they match, point the daily scenario at the new connection and re-run the missing days from 27 Oct — first check that your storage step keys rows by date, so the backfill overwrites instead of duplicating.

The one alternative cause to be ready for: if your developer token is still at Test access, the new connection will authorize fine but the data calls will then fail with a developer-token error. That is a different failure from this 401 — it means the OAuth fix worked and the remaining wait is Google’s Basic access approval, which takes days, so it’s worth applying for now rather than after.

Quick question that decides your timeline: in your manager account’s API Center, does your developer token show Basic access already, or Test?

This topic was automatically closed after 10 days. New replies are no longer allowed.