Zoom Meeting Creation
Create Zoom meetings from the app with the right host, passcode, and recording rules.
What it adds
Meeting creation and updates on a connected Zoom account, with host selection, access-controlled join details, and reconciliation.
What your agent is told to do
5
What your agent is told to do
5-
1
Let the user choose which licensed host a meeting is created under, and validate that the host still holds a license at creation time. A meeting created under an unlicensed or deactivated host will be silently limited or rejected.
-
2
Treat the join URL and passcode as access credentials. Show them only to the meeting's participants and the record's authorized viewers, keep them out of activity feeds, exported reports, and shared links, and redact them from logs and error reports.
-
3
Read the account's recording, waiting-room, and authentication policies before sending settings, and never send a value the account forbids. Present what the policy will actually apply rather than what the user selected locally.
-
4
Store the returned meeting reference and, for a series, the occurrence reference against the app record, so a later update targets exactly the meeting or occurrence intended.
-
5
Do all creation and update work through the app's existing background-job system, and if Google Calendar Event Creation or Microsoft Outlook Calendar Events is present, let the calendar brief own the calendar entry and this one own only the meeting and its join details.
Edge cases it handles
8
Edge cases it handles
8- Creating under the wrong host produces a meeting nobody can start. Verify the selected host's license and status at creation, and when it has lapsed fail with a clear message naming the host rather than falling back to an arbitrary account.
- Join URLs and passcodes leak easily through notifications, exports, and shared record views. Gate them behind the same permission that governs the record, and never include them in an email sent to an address that has not been confirmed as a participant.
- A recurring meeting is a series with occurrences, and editing one is not editing all. Make the scope explicit whenever a user changes a recurring meeting, and store enough reference to target a single occurrence without disturbing the rest.
- Account-level policies on recording, waiting rooms, and authenticated join override anything the app requests. Read the effective policy, disable the controls it forbids, and explain why rather than letting a user set an option that is silently discarded.
- A meeting deleted or rescheduled directly in Zoom leaves the app showing a dead link. Reconcile on the next sync, mark the record as diverged, and offer to recreate or unlink instead of quietly recreating it.
- Tokens expire and an administrator can revoke the app for the whole account. Refresh ahead of expiry, and on revocation disconnect the integration and stop issuing calls rather than retrying rejected requests.
- Zoom enforces per-account rate limits and different limits per endpoint class. Back off with jitter, pace bulk creation, and never retry a validation rejection as though it were a transient failure.
- When Zoom is unavailable the underlying appointment must still be bookable. Save the record, queue the meeting creation, show a pending state on the record, and notify the organizer once the link exists.
Definition of done
8
Definition of done
8- The host is selected explicitly and validated as licensed and active at creation time.
- Join URLs and passcodes are visible only to authorized viewers and are absent from logs and exports.
- Recurring meetings store both series and occurrence references, and edit scope is explicit.
- Requested settings are reconciled against account policy before sending, with forbidden options disabled and explained.
- Meetings changed or deleted in Zoom are detected and flagged on the linked record.
- A Zoom outage leaves the record saved with the meeting creation queued and visibly pending.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Direct Messages
Direct Messages
Let two users hold a private conversation inside the app instead of leaving to email.
What it does
One-to-one private threads with message history, per-conversation unread counts, and blocking.
How it works
- 1 Build the conversation list, the thread view, and the unread badge. Keep the first version to one-to-one threads only and defer group conversations, reactions, threading, and file attachments rather than shipping all of them half-finished.
- 2 Reuse the app's existing Read and Unread State and Notification Center rather than inventing a second unread mechanism and a second alert path. A message notification should sit alongside every other notification the user gets.
- 3 Reuse the composer, mention handling, and rendering rules from Comments and Mentions instead of writing a second message editor with subtly different escaping.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/direct-messages
Voice Notes
Voice Notes
Say it instead of typing it, and attach the recording where the conversation is.
What it does
In-app recording of short audio notes attached to a record, comment, or message.
How it works
- 1 Add recording to the places where people already leave text, most likely alongside Comments and Mentions, so a voice note is another kind of comment rather than a separate feed nobody checks.
- 2 Store the recording through the app's existing file upload path so a voice note inherits the same retention and access rules as any other attachment on the record, and disappears with the record when it is deleted.
- 3 Show a live duration and a simple level meter while recording, and let the user review and discard before it is sent. Nobody should be committed to a recording the instant they stop.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/voice-notes
Assign Ownership
Assign Ownership
Make it obvious who is responsible for each record.
What it does
An assignee on records, with a picker, notifications on change, and a history of who owned what.
How it works
- 1 Add a nullable assignee to the relevant records. Unassigned is a real, valid state — do not force a default owner just to avoid the null.
- 2 Restrict the picker to users who can actually access the item, and validate that server-side as well as filtering the list.
- 3 Notify the new assignee when they are assigned by someone else, and record every change with the actor and timestamp.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/assign-ownership
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.