External Sync Status
Tell users how current their synced data is instead of making them guess.
What it adds
Per-connection sync run state showing what was last attempted, what last succeeded, and what failed.
What your agent is told to do
6
What your agent is told to do
6-
1
Track last attempted and last successful sync as separate values. Collapsing them into one timestamp hides exactly the failure you need to see.
-
2
Record per-run counts: records created, updated, skipped, and failed. A run that half-worked is the common case, not the exception.
-
3
Give the sync run explicit states — queued, running, completed, completed with errors, failed — and show the current one.
-
4
Provide a manual re-sync that is disabled while a run is in progress, so repeated clicks cannot start overlapping runs against the same connection.
-
5
Describe freshness honestly. If you poll every fifteen minutes, say 'updated 12 minutes ago', not 'live'. Do NOT imply real-time when the data is polled.
-
6
Credential validity, missing scopes, and the reconnect flow are owned by Integration Connection Health. When a sync fails for auth reasons, hand off to that state rather than restating it.
Edge cases it handles
6
Edge cases it handles
6- A run that dies without reporting leaves the state stuck on 'running'. Give runs a heartbeat or a maximum duration and mark stalled ones as failed.
- Partial failures need the failing records named or downloadable. 'Completed with 43 errors' is not actionable on its own.
- Timestamps must render in the viewer's time zone, and relative times must keep updating on a page that stays open.
- The first sync has no previous run. Show a first-run state, not 'never synced' in red.
- A long-running initial import will make freshness look terrible for hours. Distinguish an initial backfill from routine incremental syncs.
- Manual re-sync must be rate-limited per connection. Users will click it repeatedly during an outage and exhaust the provider quota.
Definition of done
8
Definition of done
8- Last attempted and last successful sync are stored and displayed separately.
- Each run reports created, updated, skipped, and failed record counts.
- Failed records are inspectable, not just counted.
- Manual re-sync cannot start while a run is active and is rate-limited.
- Freshness wording matches the actual polling interval and never claims real-time.
- A stalled run transitions to a failed state within a bounded time.
- 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.