Integration Connection Health
Show at a glance whether each connected service actually still works.
What it adds
A health state per integration connection that separates expired credentials, missing permissions, and provider outages.
What your agent is told to do
6
What your agent is told to do
6-
1
Give every connection an explicit health state: healthy, needs reconnection, missing permission, provider unavailable, or never used.
-
2
Derive health from the last successful call, not from whether a token row exists. A stored token proves nothing — providers revoke without telling you.
-
3
Record the classified reason whenever a call fails, so the state has an explanation attached rather than being recomputed from guesswork.
-
4
Offer a reconnect action that repairs the existing connection in place, keeping its ID, settings, and mappings. Do NOT create a second connection on reconnect — that orphans everything attached to the first one.
-
5
Show the user a plain sentence about what to do. Never surface the provider's raw error body, which routinely contains tokens, internal URLs, and account identifiers.
-
6
Per-run sync freshness, record counts, and the manual sync button are owned by External Sync Status; link to it rather than duplicating it. Refresh-token mechanics are owned by OAuth Token Refresh Recovery.
Edge cases it handles
6
Edge cases it handles
6- A provider outage is not a broken connection. Do not tell the user to reconnect when the fix is to wait.
- A scope added to the app after a user connected leaves old connections technically valid but functionally incomplete. Detect the missing scope and ask for incremental consent, not a full teardown.
- A connection that has never been used has no last-success timestamp. Show 'not yet used' rather than an alarming red state.
- Rate limiting looks like failure. Treat it as a distinct, temporary state and do not degrade health for it.
- Health checks must not hammer the provider. Judge from real traffic, and probe on a schedule slow enough not to consume the user's quota.
- The person who sees the broken connection may not be the one who can fix it. Say who owns the connection and notify them.
Definition of done
8
Definition of done
8- Every connection displays one of the defined health states.
- Expired credentials, missing scopes, and provider outages are distinguishable in the UI.
- Health is computed from the last successful call, not token presence.
- Reconnecting preserves the connection's ID and configuration.
- No provider error body, token, or internal URL is shown to the user.
- Health checking does not measurably consume the user's provider rate limit.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Contentful Entry Sync
Contentful Entry Sync
Create and update Contentful entries against the connected space, environment, and locale.
What it does
A sync that writes app records into Contentful entries using the connected space's content model and locale configuration.
How it works
- 1 Have the operator select the space, the environment, and the default locale during connection, and store all three, because writing production content into a sandbox environment is an easy and expensive mistake.
- 2 Fetch the content model at connection time and again before each sync run, map app fields to entry fields by their stable identifiers, and validate the value type against the model before attempting the write.
- 3 Write every localized field under an explicit locale rather than relying on whatever the space treats as default, and state clearly which locales the app owns and which it leaves to editors.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/contentful-entry-sync
Typesense Index Sync
Typesense Index Sync
Keep a search index in step with your records so results stay current and correctly scoped.
What it does
A one-way sync from the app's records into a Typesense collection, with server-enforced tenant filtering and a rebuild path.
How it works
- 1 Identify every model users search today and declare the indexed shape explicitly: the fields people type into, the fields they filter and sort on, and nothing more. Treat a missing or newly added field as absent rather than letting the document fail validation.
- 2 Reuse the app's existing background-job system to push creates, updates, and deletes. Do not index inside the request cycle; a slow or unreachable search service must never make a save fail or hang.
- 3 Build the tenant, workspace, and permission filter on the server at query time and attach it to every search. Do not accept a filter, collection name, or scope value from a client-supplied parameter, because anything the browser can set the browser can change.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/typesense-index-sync
Mapbox Geocoding
Mapbox Geocoding
Convert typed locations into coordinates and structured addresses the app can use.
What it does
Forward and reverse geocoding with confirmed matches, controlled result bias, and coordinate precision rules.
How it works
- 1 Separate the two directions explicitly: text to coordinates for entry and search, coordinates to address for a dropped pin or a device location. They take different inputs, carry different confidence, and fail differently.
- 2 Present ambiguous matches as a list the user confirms. Silently taking the first result is how a record ends up in the wrong country with nobody noticing for months.
- 3 Bias results toward a location only when the app genuinely knows one, such as a workspace address or the map viewport the user is already looking at.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/mapbox-geocoding
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.