← Integration Engineering
Integration Engineering

A Connected Account Is Not “Done”. It Has a Life.

16 Oct 2026·3 min read

A connection rests on a token or a key, and those do not stay valid forever. Tokens expire. Someone removes your app’s access. The admin who clicked "Allow" leaves, and the access they granted can go with them. Nothing announces it, and often the customer notices first.

Three states to track

  • Active: the credentials work and calls go through.
  • Error: calls fail, usually because a token expired or someone removed access. Retrying will not fix it. The customer has to connect again.
  • Paused: you stopped it on purpose, for example when a customer stops paying. Keep the credentials so it can resume.

Hear about it when it breaks

Checking every account every few minutes costs many calls that almost always say "still fine". So listen first: if your platform or provider sends account events, subscribe to them, like a webhook that says "this account went into error". Keep a slow poll as a backup, and mark the account as error the first time a call fails with a 401.

Then tell the customer in plain words: "Your HR connection needs you to sign in again", with a button that opens the same connect screen.

From my own schedulerMy LinkedIn scheduler’s token lasts 60 days, with no refresh token. The code checks the expiry on every run and emails me a warning five days before, so I do not find out from a quiet morning with nothing on LinkedIn.
Do this in 60 secondsPick one integration and ask: if a customer’s token were revoked right now, who would find out first? If the answer is "the customer, when they complain", you know what to build next.
Today’s AI angleCheck the account state before an AI agent calls a tool on it. If it is in error or paused, return a clear message like "the HR connection needs to be reconnected". Otherwise the agent may retry, guess, or say the data does not exist.
A Connected Account Is Not “Done”. It Has a Life. · Ali Huzaifa