When a token can’t be refreshed or an endpoint is retired, the integration stops moving data until someone reconnects or updates it. Access tokens expire constantly (30 minutes at HubSpot, 60 at QuickBooks Online) and renew automatically. Outages come from refresh tokens that get revoked or expire, as QuickBooks Online’s do after 100 days unused.
What happens to an integration when an OAuth token expires or an API version changes?
What actually breaks, in Zapier and in code
OAuth gives an integration two credentials. The access token is short-lived and goes with every API call. The refresh token is long-lived and is used to get a new access token. Normal expiry of the access token is invisible. An outage starts when the refresh step fails.
In Zapier or Make
The app connection gets marked as needing reconnection, steps that use it start to error, and the account owner gets an email. That email often goes to someone who has left, or who doesn’t know what the connection does. Polling triggers may pick up missed records after you reconnect. Webhook events sent while the connection was broken are often not redelivered.
In a custom integration
It depends on how it was written. A careless build throws a 401 Unauthorized, logs it somewhere nobody reads and drops the record. A careful one stops calling that system, queues the work, alerts a named person and picks up from its last sync point once someone reauthorizes. Neither approach can reauthorize itself. Only a person with the right login can grant consent again.
How long tokens last at the systems you probably use
Each vendor sets its own lifetimes. The column that matters is the last one, because it lists what kills a refresh token.
| System | Access token | Refresh token | What usually kills it |
|---|---|---|---|
| HubSpot | 30 minutes | No fixed expiry | App uninstalled, installing user removed, new scopes requiring reinstall |
| Salesforce | Tied to the org’s session timeout | Set per connected app: until revoked, fixed period, or expire if unused | Admin changes the policy, user deactivated, too many authorizations for one user and app revoking the oldest |
| QuickBooks Online | 60 minutes | 100 days, rolling; the value can change on each refresh | New refresh token not saved, 100 days with no refresh, user disconnects the app |
| Google (Gmail, Sheets) | About 1 hour | Long-lived, but 7 days if the app is still in Testing status | Password change on Gmail scopes, user revokes access, app left in Testing |
| Microsoft 365 | About 1 hour | Expires after a period of inactivity | Conditional access policies, password resets, admin revocation |
QuickBooks Online catches a lot of builds out. Intuit can hand back a new refresh token on each refresh, so an integration that keeps the original quietly fails months later. Seasonal syncs that run once a quarter hit the 100-day limit for the same reason.
How API version changes reach you
- Salesforce ships three releases a year, each with a new API version. Old versions are retired with notice; versions 21.0 through 30.0 were retired in the Summer ’25 release. Custom code that hardcodes an old version in its endpoint path breaks on that date.
- QuickBooks Online versions its Accounting API with a
minorversionparameter. In 2025 Intuit retired older minor versions and started serving every request at a single baseline. Code that depended on old response shapes can misread fields with no error at all. - HubSpot announces sunsets in its developer changelog and has been moving older v1 and v2 endpoints to newer APIs with dated versions. Retired endpoints start returning errors after the sunset date.
In Zapier you don’t control the version. The vendor’s Zapier app is updated for you, and that’s convenient until a field you mapped is renamed or removed. Then the step runs and sends a blank value. In custom code you control the version, and you also have to read the notices.
Worked example: one deal, three systems
Stack: HubSpot closed-won creates a QuickBooks Online customer and a draft invoice. Then a Stripe payment webhook updates the HubSpot deal. Here’s how it breaks and how a hardened build handles each failure:
- The QuickBooks refresh token rotates and the old one is kept. Fix: save the new refresh token on every refresh, in one place, inside a transaction.
- The accountant who authorized QuickBooks leaves and their login is removed. Fix: authorize with a shared service login the firm owns, and record whose consent each connection uses.
- A Stripe payment arrives while HubSpot is unreachable. Fix: store the webhook event, retry with backoff, and alert after a set number of failures instead of dropping it.
- HubSpot retires an endpoint the sync calls. Fix: put the version in configuration, keep one integration test per endpoint, and read the changelog each month.
By our estimate, adding these protections to an existing integration takes 10 to 25 hours at our $85 hourly rate, so roughly $850 to $2,125. Building them into a new two-system integration is part of our $1,500 to $6,000 range. The top of that range applies when there are many custom fields to map or the error handling is complicated.
We built this pattern into the Fundz connector framework: OAuth, incremental sync, deduplication and rate-limit handling for HubSpot, Salesforce and Gmail across many tenants. In a multi-tenant setup a dead token in one account must not stop the others.
Monitoring checklist for credentials and versions
- List every connection, the login that authorized it, and who to call when it breaks.
- Move authorizations off personal logins onto service accounts the company owns.
- Send connection-error emails from Zapier or Make to a shared inbox, not one person.
- In custom code, alert on the first failed refresh, not the tenth failed sync.
- Run a daily health call that uses each token, even when there’s nothing to sync.
- Record the last successful sync time per system and alert when it’s older than expected.
- Pin API versions in configuration and note when each one is retired.
- Subscribe to the HubSpot, Salesforce and Intuit developer changelogs and review them monthly.
- Queue work while a system is unavailable, then replay it after reauthorization.
- Write a one-page runbook: how to reauthorize, how to replay, how to check for duplicates.
Which approach fits
Stay on Zapier or Make if you have a few low-stakes workflows, the connections are owned by a shared account, and a missed record can be fixed by hand within a day. Most of the checklist is free there: shared alert inbox, service logins, and a monthly look at the connections page.
Go custom when the flow touches invoices, payments or customer records, when you sync many accounts or tenants, or when a silent gap of a week would cost more than the build. Don’t hire anyone yet if the integration has run cleanly for a year and only fails when someone leaves. Fix the login ownership first.
Frequently asked questions
Why does my Zapier connection keep asking me to reconnect?
Usually the vendor revoked the refresh token. Common causes are a password change, the authorizing user being removed, an admin changing app policy, or a token going unused past its limit. Reconnecting with a shared service login the company owns stops most repeats.
How long does a QuickBooks Online refresh token last?
Access tokens last 60 minutes. Refresh tokens last 100 days on a rolling basis, and Intuit can return a new refresh token on each refresh. An integration that doesn’t save the newest value, or doesn’t refresh for 100 days, has to be reauthorized.
Do HubSpot OAuth tokens expire?
HubSpot access tokens expire after 30 minutes and are renewed with the refresh token. The refresh token has no fixed expiry. It stops working if the app is uninstalled or the installing user loses access, and adding new scopes can require the app to be reinstalled.
How do I find out about Salesforce API version retirements in time?
Salesforce publishes retirement notices in its release notes and announces them well before the cutoff. Each of the three releases a year adds a new API version. Keep the version your code calls in configuration and check it against the retirement list at every release.
What does it cost to harden an existing integration against token and version failures?
By our estimate, it takes 10 to 25 hours at $85 an hour, roughly $850 to $2,125. That covers saving the newest token, refresh alerts, health checks, version pinning, a replay queue and a runbook. The cost goes up with the number of systems and how much error handling already exists.
Related answers
Want us to check your integrations for credential risk?
We’ll send a short written scope, free, or talk it through on a 20-minute call. Have ready the systems involved, roughly how many records move each month, and which connections broke or were reconnected recently. Start a conversation.