// AUTOMATION FIXES
Zapier connection expired? Reconnect it, then stop it expiring again
A Zapier connection expired means the login behind it stopped working: a password changed, access was revoked, or the app’s token ran out. Every Zap using that connection stops until someone reconnects it. Make and n8n connections expire the same way. Web Blend builds and runs Zapier, Make.com and n8n automations, and is a ServiceM8 Bronze Partner. We reconnect it on an account your staff can’t break, then watch for the next quiet spell.
Updated October 2026. Google token rules checked against Google’s OAuth documentation on 30 October 2026.
// CHECK IT NOW
Five checks for connections
- Which connections ask to reconnect? Zapier: app connections. Make: Connections. n8n: Credentials. Note every one.
- Whose login made it? If it was a staff member’s email, a password change or their leaving can end it.
- Is it a Google connection that dies every 7 days? See the next section.
- Is it Outlook or Microsoft 365? Microsoft’s default refresh-token lifetime is 90 days, and owners report reauthorising Outlook connections on about that cycle. Diarise a check.
- Which automations use it? Reconnect once, then check each one ran.
Google connections that die every 7 days
If you set up your own Google Cloud app for Make or n8n and left it in “Testing” with external users, Google issues a refresh token that expires in 7 days (unless the app only asks for name, email and profile). Builders on the n8n community forum report reconnecting Google every week for exactly this reason.
Google also ends a refresh token when:
- the user changes their password and the token has Gmail access,
- it hasn’t been used for six months, or
- the account passes 100 tokens for one app, in which case the oldest goes without warning.
The fix is to move the app out of Testing (depending on what it asks for, Google may want to verify it) or to use the platform’s built-in Google connection where it offers one.
// MAKE
Make: “please reauthorize the connection”
Make users report “Invalid refresh token. Please reauthorize the connection” when the connected app no longer accepts the saved token. Scenarios that use it fail, and a scenario with an instant trigger is switched off on its first error. Reauthorise, then check whether the scenario was deactivated.
// GOHIGHLEVEL
GoHighLevel keeps asking to reconnect
Owners report GoHighLevel’s connection to Zapier asking to reconnect again and again, and n8n builders report GoHighLevel tokens dropping out of their workflows without an error. The pattern is the same as every connection on this page: whoever’s login made it, and whatever happens to that login, decides whether it keeps working.
We run GoHighLevel in-house, so we connect it with a dedicated user rather than an owner’s or staff member’s login.
// HOW WE STOP IT
A dedicated account, then an alert when it goes quiet
Prevention: our own account in your system
Connections run through a dedicated Web Blend user: Web Blend business name, an @webblend.au email, only the rights the automation needs. A staff password change or a deleted user can’t break it. You know it’s there and leave it alone.
Detection: an alert when a flow goes quiet
Error alerts need a run that fails. A trigger that stopped produces no run at all. So an n8n automation watches each flow for silence, for example no form leads in 3 days or no review requests sent, and alerts us.
Fail-safe: a register
Every action is logged to a Google Sheet, such as who was asked for a review. When something fails, the sheet shows exactly who missed out.
Recovery: a replay
A catch-up automation replays each missed action once, or backdates the data, such as conversions to Google Ads, so it catches up.
Google keeps an ad click’s ID for 90 days, so conversions that need replaying should be replayed quickly.
// PRICING
Automation Rescue + Watch
$490 + GST to fix what’s broken and set up monitoring, then $49/month + GST. Watch covers Make and n8n, including self-hosted n8n. Watching Zaps takes the Zapier add-on, $29/month + GST per Zapier account, or we move your Zaps to Make or n8n. See automation monitoring for small business.
// FIT
When you can fix it yourself
-
One connection, made with your own login, and you’re happy to reconnect when asked. - Only the Google 7-day problem, and you can publish the Google app yourself.
Zap still on but not running? See Zapier stopped working. n8n workflow gone quiet? See n8n workflow failed silently.
// QUESTIONS
Questions owners ask
Not sure which login your automations hang off? Tell us what you run and we’ll find out.
Ask usWhy does my Zapier connection keep expiring?
The login or token behind it stopped working. Common causes are a password change, revoked access, a staff member leaving, or a token the app expires on a timer. Reconnecting fixes it until the next time.
Why does my Google connection in Make or n8n expire every 7 days?
Google gives a 7-day refresh token to apps left in “Testing” with external users, unless the app only asks for basic profile access. Move the app to production or use the platform’s own Google connection.
What happens to my automations while the connection is expired?
Every automation using it stops or fails until it is reconnected. Anything that should have happened in between is missed unless something replays it.
Should my automations use my own login?
We’d rather they didn’t. A staff login ties your automations to one person’s password. We connect with a dedicated Web Blend account that only does this job.
Do you need my password?
No. We set up our own user in your system with only the rights it needs.
How much does it cost to fix connections that keep expiring?
Automation Rescue + Watch is $490 + GST to fix what’s broken and set up monitoring, then $49/month + GST. Watch covers Make and n8n automations, including ones we didn’t build and self-hosted n8n. Watching Zaps takes the Zapier add-on, $29/month + GST per Zapier account, or we move your Zaps to Make or n8n.
// GET HELP
Reconnect it once, on an account nobody changes
Tell us which connection keeps dropping and which tools it feeds. We’ll tell you why and give you a fixed price.
// AUTOMATION RESCUE + WATCH
Tell us what stopped
Say what went quiet and roughly when. A person at Web Blend replies within one business day with what probably broke and a fixed price to fix it and watch it.
Documentation used
- Google: Using OAuth 2.0 (refresh token expiration)
- Microsoft: refresh tokens
- Make: scenario settings
- Google Ads: offline conversion imports