Calendly Booking Sync
Bring Calendly bookings and cancellations into the app so records stay current.
What it adds
An inbound sync of Calendly booking, cancellation, and reschedule events onto the app's leads, contacts, and tasks.
What your agent is told to do
5
What your agent is told to do
5-
1
Receive booking events on a dedicated endpoint that verifies the sender's signature before doing any work, and reject anything unsigned or stale. Do not identify the sender by source address alone.
-
2
Acknowledge receipt immediately and process the booking through the app's existing background-job system. A slow match against a large contact table will otherwise cause Calendly to time out and re-send.
-
3
Match each invitee to an existing user or lead by a defined rule — email first, then any identifier passed through the booking form — and when no confident match exists, create a clearly marked unmatched booking a human can resolve rather than guessing.
-
4
Treat booking, reschedule, and cancellation as states of one booking, not three unrelated records. Keep the original booking's identity through a reschedule and record the history against it.
-
5
Store every booking time as an instant with the named zone it occurs in, and keep the invitee's own zone separately so confirmations and reminders read correctly to them.
Edge cases it handles
8
Edge cases it handles
8- Invitees book with whatever email they feel like, so a naive match will attach a booking to the wrong person or to nobody. Define the match order explicitly, hold ambiguous cases in an unmatched queue with the raw booking details, and never merge two contacts automatically on the strength of a booking.
- Webhooks are re-sent on any doubt, and reschedules arrive as new events referencing an old one. Key on the provider's booking identifier so a repeat delivery updates rather than inserts, and process events for the same booking in order even when they arrive out of order.
- Cancellation and rescheduling are the same lifecycle as the original booking. A cancellation that creates an orphan record, or a reschedule that leaves the old slot marked active, will corrupt downstream tasks and reminders. Transition the existing booking instead.
- An account can span several organizations and many event types, and the app must not sync everything by default. Let the user select which organizations and event types are imported, and ignore the rest rather than filling the app with unrelated bookings.
- Times stored without an explicit zone display correctly to the host and wrongly to the invitee. Persist the canonical instant, the event's zone, and the invitee's zone, and render each audience in its own.
- A booking may arrive for a record that has since been deleted or that the connecting user no longer has access to. Retain it as unmatched with a clear reason instead of dropping it or attaching it to something the user cannot see.
- Tokens expire and a disconnected Calendly account will keep sending webhooks that can no longer be verified against a live connection. Mark the integration disconnected, stop processing, and tell the owner rather than accumulating silent failures.
- When Calendly is unavailable or a burst of webhooks arrives during a busy period, the endpoint must stay responsive. Bound per-account processing concurrency and let the queue absorb the burst rather than shedding events.
Definition of done
9
Definition of done
9- Incoming webhooks are signature-verified before any processing, and unverified requests are rejected.
- The endpoint acknowledges immediately and processes bookings in the background.
- Repeat deliveries key on the provider's booking identifier and update rather than duplicate.
- Booking, reschedule, and cancellation move one booking record through its lifecycle.
- Invitees with no confident match land in an unmatched queue rather than being attached to the wrong record.
- Users select which organizations and event types are imported.
- Times are stored canonically and displayed in both the host's and the invitee's zone correctly.
- 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.