Third-Party Account Import
Pull existing data straight from another service instead of asking for a file.
What it adds
An API-driven import that previews what will be created, then writes it in a resumable, deduplicated way.
What your agent is told to do
6
What your agent is told to do
6-
1
Let the user pick what to import before authorizing, and request only the scopes those selections need. Do not ask for full account access to import one list.
-
2
Fetch through the provider's pagination to completion and persist a cursor as you go, so the job resumes from where it stopped rather than restarting.
-
3
Show a preview before writing anything: how many records will be created, how many match existing ones, and what the duplicate rule will do with them.
-
4
Store the provider's record ID alongside your own, scoped to the connection. Do NOT treat a provider ID as globally unique — two connections to the same provider will collide.
-
5
Establishing the connection itself is owned by OAuth Integration Connections, file-based import by CSV Import, and the progress display by Background Job Progress. Use them rather than rebuilding them.
-
6
Make the whole import reversible or at least identifiable — tag imported records with the import run so a bad import can be found and undone.
Edge cases it handles
6
Edge cases it handles
6- Rate limits will be hit mid-import. Respect the provider's retry-after, pause the job, and resume — do not fail the whole run.
- The token can expire partway through a long import. Refresh and continue; if reauthorization is needed, pause and tell the user rather than discarding progress.
- The provider's data may change while you are paginating, producing duplicates or gaps. Deduplicate on provider ID rather than trusting page boundaries.
- Referenced records may point at objects the user did not select or does not have scope for. Import them as placeholders or skip them explicitly; do not fail silently.
- A user may run the same import twice. The second run must update matched records rather than doubling everything.
- Fields the provider allows and yours does not — longer text, unsupported characters, missing required values — need a stated per-record outcome, reported at the end.
Definition of done
8
Definition of done
8- Requested scopes correspond to the data the user selected to import.
- Pagination completes and the job resumes from a persisted cursor after interruption.
- A preview shows create, match, and skip counts before any write occurs.
- Provider IDs are stored scoped to the connection, not as global identifiers.
- Re-running an import updates matched records instead of duplicating them.
- Every skipped or failed record is reported with a reason after the run.
- 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.