Amazon S3 Backup Export
Let customers send their exports and archives to a bucket they control themselves.
What it adds
A customer-configured S3 destination with scoped credentials, multipart transfer, and verified object integrity.
What your agent is told to do
5
What your agent is told to do
5-
1
Let a customer configure their own bucket as an export destination — bucket, region, key prefix, and expected encryption — and validate all of it with a test write at the moment they save the settings.
-
2
Prefer credentials the customer can scope and rotate, such as a role the app assumes with an external identifier, and store whatever is held encrypted at rest. Do not make a long-lived account-wide key the only supported option.
-
3
Write large archives as a multipart upload driven by the app's existing background-job system, so a failed part is retried rather than the whole archive resent.
-
4
Give every export an immutable key built from the prefix, a timestamp, and the export's own identifier, so a new run can never land on top of an old one.
-
5
Dropbox File Export and OneDrive File Export cover consumer destinations and their interactive folder pickers. This entry owns the customer-operated bucket case: credential scoping, multipart transfer, and integrity verification.
Edge cases it handles
8
Edge cases it handles
8- Permanent broad keys become a liability the moment the app is breached. Assume a scoped role where the provider supports it, require an external identifier so the app cannot be used as a confused deputy, and allow rotation without breaking scheduled exports.
- A wrong region, a missing bucket, a prefix the credential cannot write, or a bucket policy demanding a particular encryption setting all fail at upload time. Validate each on save and name the specific setting that is wrong.
- An abandoned multipart upload leaves incomplete parts the customer keeps paying to store. Abort explicitly on failure, and resume or clean up on the next run.
- Two exports must never collide on one key and silently destroy the earlier backup. Keys are unique per run, and an unexpected existing object fails the run loudly instead of overwriting it.
- Confirm the stored object's checksum matches what was sent before marking the export complete. An export reported as successful but truncated is worse than one that plainly failed.
- Bucket policy can change after connection so that working exports start being refused. Treat access denial as a connection-level problem, notify the account owner, and stop the retry schedule.
- The provider throttles per key prefix under sustained load. Back off on throttling responses rather than treating them as fatal.
- Never echo a stored credential back to the browser, even masked in a settings form. Show only enough to identify which credential is in use.
Definition of done
9
Definition of done
9- A customer can point exports at their own bucket with region, prefix, and encryption settings validated on save.
- Credentials are scoped, encrypted at rest, rotatable, and never returned to the client.
- Large archives upload in parts and resume rather than restarting after a failure.
- Each export writes a unique key and cannot overwrite a previous backup.
- An export is marked complete only after its checksum is verified against the stored object.
- Access denied, wrong region, and throttling are reported as distinct causes.
- Failed multipart uploads are aborted rather than left accruing storage cost.
- 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.