When an integration shows an error
Read the error, fix the cause in the other tool, and run it again.
Find the message
Open the integration's Logs tab. Each failed run shows the other tool's own error, like 401 Unauthorized or invalid_grant.
The usual causes
- 401 or 403: the key was revoked, expired or lacks a permission. Create a new one, paste it on the Connection tab and click Test connection.
- invalid_grant (FreshBooks, other sign-in based tools): the authorization was withdrawn. Authorize again and paste the new token.
- 404: an ID you entered (a list, course, account or business) no longer exists. Check it in the other tool.
- 429: the other tool is rate limiting. The next scheduled run usually catches up.
Keys that expire on their own
- Dropbox generated tokens last about four hours. Generate a new one for each upload until the sign-in style connection ships.
- Cal.com keys default to 30 days; create them with Never expires on.
- Constant Contact access tokens expire; authorize the app again and paste the new one.
- SurveyMonkey private apps left in Draft expire 90 days after creation; deploy the app to keep the token.
- Webflow retires a token after a year unused. A daily schedule keeps it alive.
- QuickBooks, Xero, FreshBooks refresh tokens are swapped on every use. Mybers saves the new one, so never paste an old copy back in; reconnect instead.
A permission you just added in the other tool can take a minute to apply (SurveyMonkey, Zoom). Wait, then click Test connection again.
After fixing it, click Sync now on the Overview. If the error doesn't make sense, send us the message from the Logs tab and we'll take a look.