Google Calendar Event Creation
Turn app records into Google Calendar events with attendees, reminders, and links.
What it adds
An authorized per-user connection to Google Calendar that creates and updates events from app records and keeps the two linked.
What your agent is told to do
5
What your agent is told to do
5-
1
Authorize each user individually and store the resulting tokens encrypted and server-side only. Request the narrowest calendar scope that supports writing events, and never place any credential where client-side code can read it.
-
2
Ask the user which calendar to write to during setup and store that choice per connection. Do not assume the primary calendar, because many people keep work bookings on a secondary or shared one.
-
3
Store every event time as an instant plus the named time zone it was entered in, and send both. A time expressed only as an offset breaks the moment daylight saving shifts or the event is moved.
-
4
Send an idempotency-style stable identifier derived from the app record with every create, and record the returned event reference against the record. On retry, look up that reference and update rather than creating a second event.
-
5
Perform all calendar calls through the app's existing background-job system so a slow or failing Google response never blocks the user's save. Show the sync state on the record instead.
Edge cases it handles
8
Edge cases it handles
8- A user with several calendars will otherwise get bookings on the wrong one. Let them choose the target calendar per connection, show which calendar is in use on the record, and re-prompt if that calendar is later deleted or no longer writable.
- Times sent without an explicit named zone drift after a daylight saving change and land an hour off for recurring bookings. Persist the zone the event was authored in alongside the instant, and render it to viewers in their own zone.
- A retry after a timeout can create a duplicate event because the first attempt may have succeeded unseen. Store the provider's event reference against the record on first success, and on any retry reconcile against that reference before creating anything.
- Attendees, recurrence rules, and calendar sharing permissions change independently of the app. Handle an attendee who declines, a recurring series edited at the provider, and a token whose granted access has been narrowed, by surfacing the mismatch on the record rather than overwriting the user's calendar.
- An event moved or deleted directly in Google leaves the app's copy wrong. Detect the missing or changed event on the next sync, mark the local record as diverged, and ask the user whether to recreate or unlink rather than silently rewriting their calendar.
- Access tokens expire and refresh tokens get revoked when a password changes or an admin removes the app. Refresh proactively, and on a permanent authorization failure mark the connection as disconnected and prompt the user to reconnect instead of retrying forever.
- Google rate limits per user and per project. Back off with jitter on throttling responses, queue rather than burst when a bulk action would create many events, and never retry a validation rejection.
- When Google Calendar is unavailable, the app must still accept the booking. Save the record, queue the calendar write, and show a pending sync state with a clear retry, rather than failing the user's action.
Definition of done
9
Definition of done
9- Each user authorizes their own connection, and tokens are stored encrypted server-side only.
- The target calendar is chosen explicitly and recorded per connection.
- Event times are stored and sent with an explicit named time zone.
- A retried create reconciles against the stored event reference and never produces a duplicate.
- Events changed or deleted in Google are detected and flagged on the linked record.
- Expired or revoked authorization marks the connection disconnected and prompts a reconnect.
- A Google outage leaves the app usable, with the calendar write queued and visibly 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.