Google Drive File Export
Let users send app files and reports straight to a folder in their own Google Drive.
What it adds
An authorized per-user Drive connection that uploads generated files to a folder the user picks, with resumable uploads and naming rules.
What your agent is told to do
5
What your agent is told to do
5-
1
Request the narrowest scope that allows writing the files this feature creates, and prefer a scope limited to files the app itself created over one granting access to the user's whole Drive.
-
2
Have the user pick the destination folder explicitly through a selection flow, store the folder reference with the connection, and write only inside it. Never fall back to the Drive root when the stored folder cannot be found.
-
3
Upload through a resumable mechanism for anything larger than a trivial file, record the upload session against the export, and resume from the last confirmed position rather than restarting from zero after an interruption.
-
4
Define the collision rule before writing: either create a new version of the existing file or write a distinct name with a deterministic suffix. Do not silently overwrite a file the user may not have realized was there.
-
5
Run every export through the app's existing background-job system and show its state on the export record, so a large upload never holds a web request open or times out under the user's cursor.
Edge cases it handles
8
Edge cases it handles
8- Asking for broad Drive access to do a narrow job is the tempting shortcut and the wrong one. Request only what writing the app's own exports requires, and if a wider scope was ever granted, drop to the narrow one on the next reconnect and say so in the connection screen.
- A stored folder can be renamed, moved, trashed, or have its sharing revoked between exports. Verify the folder is still present and writable before uploading, and when it is not, pause the export and ask the user to reselect rather than writing somewhere else.
- Repeated exports of the same report will collide by name. Apply the chosen collision rule consistently, make the resulting name predictable so the user can find it, and never destroy an existing file without an explicit instruction.
- Large uploads fail partway on flaky connections and leave a fragment behind. Use resumable uploads, resume from the last acknowledged byte, and clean up abandoned partial uploads so the user's Drive does not fill with truncated files.
- The connection must not become a general-purpose door into the user's Drive. Do not list, read, or index unrelated content, do not cache directory structure beyond what the folder picker needs, and revoke the token cleanly when the integration is disconnected.
- Tokens expire and consent can be revoked by the user or a Workspace administrator. Refresh ahead of expiry, and on permanent authorization failure mark the connection disconnected and prompt a reconnect rather than retrying indefinitely.
- Drive rejects uploads when the account is out of storage or a size limit is exceeded. Distinguish those permanent conditions from transient failures, tell the user which one occurred in plain terms, and do not queue endless retries against a full account.
- When Drive is unavailable the export itself must still succeed. Generate the file, keep it downloadable from the app, and show the Drive delivery as pending with a retry rather than losing the export.
Definition of done
9
Definition of done
9- The connection requests only the minimum scope needed to write the app's own export files.
- The destination folder is chosen explicitly, and exports are written only inside it.
- A missing or unwritable folder pauses the export and asks the user to reselect instead of writing elsewhere.
- Filename collisions follow a stated rule and never silently overwrite an existing file.
- Interrupted uploads resume from the last confirmed position, and abandoned partials are cleaned up.
- Disconnecting the integration revokes the stored access, and no unrelated Drive content is read or retained.
- A Drive outage leaves the generated file available in the app with the delivery marked pending.
- 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.