Dropbox File Export
Send generated reports and exports straight into a connected Dropbox folder.
What it adds
A per-user Dropbox connection that writes app-generated files into a folder the user chose.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the places the app already produces a file — report generation, data exports, invoice documents, attachment bundles — and offer Dropbox delivery as an additional destination beside the existing download.
-
2
Store the connection per user, or per workspace where the destination is shared, and keep tokens on the server. Nothing that can write to someone's Dropbox may reach the browser.
-
3
Ask for the narrowest access the provider offers and let the user pick one destination folder during connection. Do not request account-wide write access because it makes the folder picker easier to skip.
-
4
Run every transfer through the app's existing background-job system with retries and backoff, and record a per-file status the user can see. A large export must not be tied to the lifetime of a web request.
-
5
This entry owns Dropbox only. If OneDrive File Export or Amazon S3 Backup Export is also being built, share one destination abstraction — connection record, folder selection, job, status log — and let each provider supply only the transfer details.
Edge cases it handles
8
Edge cases it handles
8- Access tokens expire and refresh tokens can be revoked from the provider's own settings page. Refresh transparently on expiry, and when the refresh itself fails, mark the connection broken and ask the user to reconnect rather than retrying forever.
- A file with the same name may already exist at the destination. Pick one rule — overwrite, or append a suffix — state it where the user chose the folder, and apply it consistently instead of letting the provider decide.
- Large exports exceed the size a single upload request accepts and must be sent in chunks that can resume. A transfer that fails at ninety percent should continue rather than start again.
- The chosen folder can be renamed, moved, or deleted after the connection was made. Detect the missing destination, stop the transfer, and ask the user to choose again rather than silently creating a new folder at the account root.
- Disconnecting must revoke the stored credential with the provider as well as deleting the local record. Files already delivered stay where they are, and the user should be told that they do.
- The provider will rate-limit a burst of uploads. Honour the retry delay it returns, back off progressively, and queue the remainder rather than failing the export.
- When Dropbox is unavailable the export itself must still succeed and remain downloadable inside the app. Show delivery as pending or failed with a retry, and never lose the generated file.
- The account can be out of storage or over quota. Surface that as its own actionable message rather than a generic upload failure.
Definition of done
9
Definition of done
9- Every export the app generates can be delivered to a connected Dropbox folder as well as downloaded.
- Tokens are stored server-side, refreshed automatically, and never reach the browser.
- The connection requests access to the selected destination only, not the whole account.
- Large files transfer in resumable chunks and survive an interrupted connection.
- Filename conflicts follow one documented rule, and a missing destination folder prompts reselection.
- Disconnecting revokes the credential with the provider and removes it locally.
- A Dropbox outage leaves the generated file intact and the delivery retryable.
- 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.