Integration Health: how each connected service is doing

Where does Integration Health show up?

The main surface is a dedicated page: Integration Health in the side navigation, with one card per service. It is visible only to the account owner and to admins whose permissions include managing integrations, and the page checks that permission before it loads any connection data. Members never see it. Before you connect anything, the page simply says no integrations yet.

The same signals appear in two other places. Settings, then Integrations, shows a health badge on the Planning Center card and health rows for your connected calendars. And the Analytics page has a Data and Integrations module that rolls the statuses up into counts: how many services are healthy, how many need attention, and how many need reconnecting. One naming note: Connection Health is a different feature. It describes how connected a person is to your church; Integration Health describes how a software service is doing.

• Integration Health lives in the side navigation for the account owner and admins permitted to manage integrations. Members never see it.
• Each service card shows a plain-language status, an optional message, the connected organization, granted permissions, and last checked and last failure ages.
• Statuses fall into three tones: healthy, neutral, and needs attention. Anything unexpected is treated as needing attention, never as fine.
• Reconnect and Disconnect buttons exist only for Planning Center, Google Calendar, and Microsoft Calendar. Other services are status-only.
• Planning Center connection changes are account-owner-only with MFA. Calendar connections also allow a permitted admin, with MFA.
• Collie reads integration health to draft review-only suggestions. It never reconnects, repairs, or changes a connection on its own.

What do the statuses mean?

FlockConnect tracks eighteen distinct statuses, and every one falls into one of three tones. Healthy covers a connection that is working: connected, actively syncing, or running in simulated test mode. Neutral covers the in-between states, like a service that is not connected yet or is in the middle of connecting. Everything else means the service needs attention, with a label that says why in plain words: Reconnect needed, Missing permissions, Conflicts need review, and so on. If FlockConnect ever sees a status it does not recognize, it shows it as needing attention rather than quietly passing it off as fine.

Each card shows the status badge, often a short message explaining what happened, which organization the service is connected as, the permissions that were granted, and how long ago the last check and last failure were. A service that has not been used yet reads not checked yet. Statuses update when something actually happens: when you connect or disconnect a service, or when FlockConnect uses the connection, like writing an event to your calendar. There is no background monitor polling every service around the clock, so last checked tells you when FlockConnect last had a reason to look. The page shows statuses, timestamps, the organization name, and permission names only. It never shows tokens or credentials, and there is no member data on it.

What should I do when a service needs attention?

Start with the message on the card, which describes the problem in plain language. Reconnect and Disconnect buttons exist for exactly three services: Planning Center, Google Calendar, and Microsoft Calendar, because those are the connections your church authorizes itself. Everything else on the page, like email delivery, text messages, and maps, is status-only; there is nothing for you to reconnect, and if one of those looks wrong you can contact support. Calendar write problems surface here too: if FlockConnect loses write access to a calendar destination, an owner or admin can see the problem on this page.

Reconnecting never happens inside FlockConnect alone. The Reconnect button sends you to the provider's own authorization screen, where you sign in and approve the connection again. Who can do this is deliberate: Planning Center connections can only be changed by the account owner, and only with multi-factor authentication completed. Calendar connections allow the owner or an admin permitted to manage calendar connections, also with MFA. If you can see the page but a button is missing from a card, that action belongs to the account owner.

How does the Planning Center reconnect path work?

When the Planning Center card says the connection needs attention, the account owner clicks Reconnect, signs in on Planning Center's own screen, and lands back on Settings, then Integrations, with a banner saying whether the connection succeeded, was denied, or hit an error. FlockConnect asks Planning Center for everything its import needs in a single authorization, so a church reconnects at most once rather than once per feature.

If your connection was made before a permission existed, imports do not fail. The blocked data type is marked, the import panel shows needs reconnect in place of its count, and a notice points you to the Reconnect button on the Planning Center card. Giving has one extra requirement: the Planning Center user who authorizes the connection must also have Giving access on the Planning Center side. Re-running an import after reconnecting is safe, because rows that already came over are skipped, not duplicated. Disconnecting is just as careful: the owner can disconnect at any time, FlockConnect revokes its own access at Planning Center, people you already imported stay in FlockConnect, nothing changes in Planning Center, and the connection is kept so you can reconnect with one click later.

How does Collie use these signals?

Collie, FlockConnect's AI assistant, reads integration health as one of the inputs to its home Mission Feed, alongside open follow-ups, unreviewed responses, and new visitors, and its suggestion cards can carry an integration category. Everything it produces is a draft that waits for your review; you approve or reject each one.

Collie's role here is advisory only. It never reconnects a service, never repairs a connection, and never changes anything on its own. Reading the statuses and acting on them stays with you, which is exactly how the rest of FlockConnect treats Collie: it drafts, a person decides.