Microsoft Outlook Calendar Events
Create and update Microsoft 365 calendar events on the right mailbox and time zone.
What it adds
A per-user Microsoft 365 calendar connection that writes and updates events on the correct tenant, mailbox, and calendar.
What your agent is told to do
5
What your agent is told to do
5-
1
Authorize per user and record which tenant and mailbox the connection belongs to. A user with both a personal and a work account will otherwise have events land in whichever one was authorized most recently.
-
2
Let the user pick the target calendar within the chosen mailbox at setup, including shared and delegated calendars they hold write access to, and store that choice with the connection.
-
3
Use the provider's concurrency control on every update: read the current version marker, send it with the change, and treat a mismatch as someone else having edited the event. Re-read and present the conflict rather than overwriting.
-
4
Attach online meeting details only when the account is licensed for it and the connection was granted the permission. Detect the absence and fall back to a plain event with the app's own link rather than failing the whole create.
-
5
This brief owns the Microsoft side only. If Google Calendar Event Creation is also present, both must write through one shared calendar-sync abstraction on the record — the record holds one provider reference and one sync state, not two competing ones.
Edge cases it handles
8
Edge cases it handles
8- Multi-account users and multi-tenant organizations make the destination ambiguous. Record the tenant, mailbox, and calendar with the connection, show them on the record, and force a re-selection if any of them stops being valid.
- Delegated access and shared mailboxes can be granted and revoked by an administrator at any time. Check write access before each batch, and when it disappears mark the connection as needing attention instead of retrying a permanently rejected call.
- Online meeting creation depends on licensing and consent that the app cannot assume. Create the meeting link only when both are present, and otherwise produce the event without it and tell the user why.
- Two updates racing — one from the app, one from the user in Outlook — will otherwise silently clobber each other. Send the provider's change key or equivalent with every update and treat a rejection as a conflict to resolve, not an error to retry blindly.
- An event deleted or moved directly in Outlook leaves the app's copy stale. Reconcile on the next sync, mark the record as diverged, and offer to recreate or unlink rather than rewriting the user's calendar without asking.
- Times must carry an explicit named time zone, not a fixed offset, or recurring events shift by an hour across a daylight saving boundary and appear correct in the app while being wrong in the calendar.
- Tokens expire and administrators revoke consent for the whole tenant at once. Refresh ahead of expiry, and on tenant-wide revocation disconnect every affected connection with a single clear explanation rather than a flood of individual failures.
- Microsoft throttles aggressively per mailbox. Honour the retry delay it returns, back off with jitter, and bound how many events one bulk action may create before it is spread across a longer window.
Definition of done
9
Definition of done
9- The connection records tenant, mailbox, and calendar, and the user selects the calendar explicitly.
- Delegated and shared-mailbox permissions are checked, and their loss marks the connection as needing attention.
- Online meeting details are added only when licensing and consent allow, with a stated fallback otherwise.
- Every update sends the provider's concurrency marker, and a mismatch is surfaced as a conflict rather than overwritten.
- Event times carry an explicit named time zone.
- Events changed or deleted in Outlook are reconciled and flagged on the linked record.
- Throttling responses are honoured and bulk creates are paced rather than burst.
- 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.