Contentful Entry Sync
Create and update Contentful entries against the connected space, environment, and locale.
What it adds
A sync that writes app records into Contentful entries using the connected space's content model and locale configuration.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Resolve and confirm every referenced entry and asset before writing the entry that points at them, and hold the write if a target does not exist rather than creating an entry with dangling references.
-
5
Do not blindly overwrite a published entry that has been changed by an editor since the app last wrote it. Compare against the version the app last saw and, on divergence, stop and report the conflict rather than discarding a person's work.
Edge cases it handles
8
Edge cases it handles
8- Fields must be addressed by their stable identifiers, and the value type must be checked against the model first. A string sent into a field the model now defines as a reference fails after the request has already partially applied.
- Localized fields fall back between locales in ways that hide missing content. Writing only the default locale can leave other locales displaying stale text that looks current.
- References and assets must exist and be processed before the entry referencing them is written, and asset processing is asynchronous, so a link created immediately after upload can point at something not yet usable.
- An entry can be draft, published with no changes, published with unpublished changes, or archived. The app must decide which of these it may transition and must not resurrect an archived entry as a side effect of a routine sync.
- Editorial changes must not be silently clobbered. Detect that the entry moved on since the app last wrote it, and surface the conflict to a human rather than resolving it by overwriting.
- Rate limits apply per space and are easy to hit during an initial backfill. Batch, back off with jitter, and make a long backfill resumable so a limit part way through does not require starting over.
- The management credential expires or is revoked. Detect authentication failure distinctly from other errors, mark the connection as needing reconnection, and surface it in the app instead of failing quietly in a background job.
- When the destination is unavailable, the app's own content must remain saved and usable, with the sync marked as pending rather than the user's save being rejected.
Definition of done
9
Definition of done
9- Space, environment, and locale are chosen explicitly at connection and stored.
- Field mappings use stable identifiers and are type-checked against the fetched content model before writing.
- Localized fields are written under an explicit locale, with the app's ownership of each locale stated.
- References and assets are confirmed to exist and be processed before the referencing entry is written.
- An entry changed by an editor since the last sync raises a conflict instead of being overwritten.
- Entry states including archived are handled explicitly, with no unintended state transitions.
- Rate limits and expired credentials surface as recoverable, operator-visible conditions.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
Google Places Address Lookup
Google Places Address Lookup
Turn a half-typed address into a structured location the app can rely on.
What it does
An address autocomplete that fills structured location fields from real places and stays editable by hand.
How it works
- 1 Replace free-text address entry on the forms that need a real location with a lookup returning structured components, and keep every component field editable after the lookup returns.
- 2 Group the keystrokes of one lookup into a single billable session and close it when a place is chosen or the field is abandoned. Debounce input and set a minimum query length, because every keystroke that reaches the provider costs money.
- 3 Store the provider's place identifier in its own field, separate from the human-readable address the user sees. The two serve different purposes, and the display text must never be parsed back into structure.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/google-places-address-lookup
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.