RReshape.
← All articles

Claude Gmail Connector Disconnected: How a Loan Team Lost a Month of Pipeline Activity

By Alex Regueiro · November 9, 2026 · 4 min read

For roughly a month, a loan officer's Claude workflows looked healthy and captured nothing. Gmail had disconnected during a cloud migration, and that one break stopped the entire automation sequence.

The people involved were a loan officer and the team member who handles day-to-day follow-up. If you run a lending team on connected tools, see how we approach it on our page for mortgage loan officers.

The situation

This came out of a call with a lending operation that already had Claude workflows running to capture pipeline activity, tasks and follow-ups.

On the call it became clear that the workflows had stopped capturing activity. From the outside the system appeared to operate normally, but it was not recording what was happening in the business.

What was broken

The cause was a disconnected Gmail connection. It dropped during a cloud migration, and the break took down the entire automation sequence.

The worse problem was how quiet it was. The break went unnoticed for about a month because the system appeared to operate normally while Gmail was disconnected. About a month of pipeline data, tasks and follow-ups was missed.

What we built

We treated this as two jobs: restore the connection, then recover the missing month.

  • Live reconnect: we reconnected everything live on the call, so the fix did not wait for a follow-up session.
  • A recovery prompt: we set up what we call a "save me" prompt, a questionnaire the team member completes. The answers are the mechanism for backfilling the missed pipeline data, tasks and follow-ups, and the team member approves the generated outputs.
  • An owner for connector health: the team member was given ongoing, high-priority responsibility for connector health and for clearing approval prompts, because the original failure went undetected.
  • A dashboard session: we set a 30-minute working session for the next day to build the one-page operations dashboard we had discussed.

What changed

No recovered figures were available when the call ended, because the questionnaire had not been completed yet. What changed is the shape of the system: the connection was restored, there is a defined route for backfilling the missing month, and one person is responsible for noticing the next disconnect.

A tip from this case: a workflow that fails silently needs something that fails loudly, such as a dashboard that looks empty when the inbox stops feeding it.

Check your own connectors in ten minutes

If Claude works from your inbox, open the connector settings and confirm every connection shows as active. Then look at the last few days of captured activity and compare it against your own sent mail. A gap between the two is the early warning.

Also check whether any approval prompts are waiting. Pending prompts can stall a workflow just as a dropped connection can. Finally, write down who owns this check each week. A task with no owner is the one that goes unnoticed for a month.

Frequently asked questions

Why did the Claude workflows keep looking normal after Gmail disconnected?

In this case the system appeared to operate normally while Gmail was disconnected, so nothing signaled the problem. That is why connector health needs a named owner and a regular check.

Can a month of missed pipeline activity be recovered?

Partly, and only with help from the people who did the work. Here we built a questionnaire prompt so the team member could describe what happened, then approve what Claude generated. The recovered data is only as good as those answers.

What can break a Claude connector without warning?

In this case it was a cloud migration, which dropped the Gmail connection. Other changes to accounts or permissions can do the same. The lesson is to check connection status on a schedule instead of trusting that no news means no problem.

Who should own connector health on a small lending team?

One named person, with a recurring check. In this build the team member who handles follow-up took it on, along with clearing approval prompts. Shared responsibility tends to mean nobody looks until something is missing.

If your Claude workflows have gone quiet and you are not sure why, book a 30-minute AI follow-up and reporting audit. We check each connection, find what is not being captured, and tell you what to fix first.