OneDrive File Export
Deliver app-generated files into a OneDrive folder or a SharePoint document library.
What it adds
A Microsoft account connection that writes exports to a drive and folder the user selected, respecting tenant policy.
What your agent is told to do
5
What your agent is told to do
5-
1
Offer OneDrive delivery on the same exports that already produce a file, and make the drive choice explicit: a personal drive, a work drive, and a SharePoint document library are different destinations with different rules.
-
2
Resolve the drive and folder during connection and store the resolved identifiers rather than the display path, so a renamed team folder does not force everyone to reconnect.
-
3
Keep tokens and the app's own registration secret on the server, refresh them ahead of expiry, and never place anything capable of writing to a tenant's files into client-side code.
-
4
Run transfers as background jobs with resumable chunked upload, backoff on throttling, and a visible per-file status. Return the destination to the user as a link that resolves through their existing permissions.
-
5
Dropbox File Export and Amazon S3 Backup Export cover the other destinations. Share the destination abstraction and the job pipeline with them; this entry owns only the Microsoft-specific drive resolution, tenant policy, and permission handling.
Edge cases it handles
8
Edge cases it handles
8- A personal account and a work account behave differently in quota, sharing defaults, administrator policy, and which drives exist at all. Detect which kind of account connected and adjust rather than assuming one shape.
- An organization user may have several drives plus multiple SharePoint libraries. Make them pick one deliberately, and re-verify the drive still exists before each scheduled delivery.
- Uploads above the single-request threshold need a resumable session, and a name collision at the destination must resolve by a rule the app states — replace or rename — rather than being left to chance.
- Tenant policy or conditional access can block the app entirely, or block it from an unmanaged device or an unexpected location. Present that refusal as an administrator decision to escalate, not as a bug in the export.
- A link handed back to the user must rely on that user's existing permissions. Do not create an anonymous sharing link to make the link work for everyone, because it puts the file outside the organization.
- Administrator consent can be granted and later withdrawn for a whole tenant, invalidating every connection at once. Detect that class of failure and tell affected users to reconnect instead of silently retrying.
- The service throttles aggressively during business hours. Respect the retry interval it returns and spread bulk deliveries rather than pushing them all at once.
- When the service is unavailable the generated file stays downloadable in the app and delivery shows as pending with a retry.
Definition of done
9
Definition of done
9- Exports can be delivered to a personal OneDrive, a work drive, or a SharePoint library, chosen explicitly by the user.
- The destination is stored as a resolved identifier and survives a folder rename.
- Credentials stay server-side, refresh automatically, and no secret appears in client code.
- Large files upload resumably and interrupted transfers continue rather than restart.
- Blocked tenant policy, withdrawn consent, and throttling each produce a distinct, actionable message.
- Links given to users resolve through their own permissions, with no anonymous sharing links created.
- A provider outage never loses the generated export.
- 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.