Oppy

Manage Boards

Unified board, list, and item management. Boards contain lists (columns), lists contain items (cards). ACTIONS — prefix indicates resource type: • board_list/get/create/update/delete — Manage kanban boards • list_list/get/create/update/delete — Manage lists (columns) within a board • item_list/get/create/update/move/delete — Manage items (cards) within lists • item_bulk_get/bulk_update/bulk_delete — Bulk item operations (max 50) COMMON PATTERNS: • Browse: board_list → list_list(board_id) → ite

Manage Contacts

Manage contacts. Actions: list, get, create, update, delete, count, bulk_update, bulk_add_tags, bulk_remove_tags, analytics, find_duplicates, search_notes, segment. SINGLE: get/update/delete require contact_id. create needs email or phone_number for dedup. BULK: Use filters object and/or contact_ids array to select contacts. Workflow: list/count → confirm → bulk action with SAME filters. FILTERS object keys: query (name/email/phone/metadata), name, email, phone_number, first_name, last_name, ta

Manage Conversations

Manage conversations. Actions: list, get, create, update, post_message, generate_reply, analyze, export_transcript. LIST filters: universal_search, channel_id, contact_id, status (comma-sep, special: all_active/any), tags, starred, is_priority, subject_contains, delivery_state, contact_method (sms/email/phone/voice/chat/unknown), has_draft_messages, has_engaged_users, has_scheduled_delivery, user_not_responded_to, min_call_duration, parent_conversation_id, latest_message_after/before (ISO8601),

Manage Channels

Manage channels (oppies/AI assistants). Full CRUD + version control. Actions: list, get, update, create, archive, history, restore, join_meeting, reflect Create/archive require confirmed_by_user: true. join_meeting: Send an Attendee bot to join a meeting. Requires channel_id + meeting_url (Google Meet, Zoom, Teams URL). reflect: READ-ONLY tool-health + blocker report (loop credit-cap hits, function call/error/denial rates, unused-function inventory, run outcomes, OpenAiTracking anomalies, reco

Manage Indexes

Manage knowledge base indexes (a "knowledge base" = an Index that owns crawled WebPages + retrievable Chunks). A channel can have MULTIPLE indexes attached (many-to-many via channel_indexes); attaching is additive and never detaches other indexes. Actions: list, get, create, update, delete, attach_channel, detach_channel. CREATE: requires `name`. Optional: `description`, `channel_id` (associate with a channel), `privacy_status` (private/public), `max_depth` (crawler), `max_web_pages` (crawler).

Generate Content

Generate AI-powered content including text, images, and video. Actions: generate (images/text), generate_video (video from images or text), capabilities (endpoint info), templates (image templates), video_models (available Veo models). Note: person_generation enums differ — image: ALLOW_ALL/ALLOW_ADULT/DONT_ALLOW, video: allow_adult/disallow.

Extract Data

Extract structured data from URLs or HTML. Actions: extract (AI-powered), quick (heuristics-only). EXTRACT: Fetches URL, parses with AI. Optional schema (JSON Schema format) for structured output. hints: natural language guidance. QUICK: Fast — returns JSON-LD, meta tags, tables without AI. output: json|tables|meta|all.

Manage Notes

Manage notes (Contact/Account/Conversation owners; admin create defaults to Account). Actions: list, get, create, update, duplicate, delete, patch_body, list_sections, list_for_resource, create_for_resource, generate_pdf, help. Reusing an existing note as a template -> duplicate (server-side clone of note_id, aliases copy/clone) instead of get + create; the body never crosses the wire. Full-screen deck/landing page -> layout:"full_bleed". Share -> visibility:"public_unlisted", then send public_u

Manage Feedbacks

Manage thumbs feedback records on messages, conversations, notes, and OpenAI tracking records. ACTIONS: • list — filter by feedbackable_type/id, score, voter_uuid, page/per_page. Start broad — call with no filters first; add feedbackable_type or score only if results are too noisy. • get — fetch one feedback record by feedback_id • create — create feedback for Message, Conversation, Note, or OpenAiTracking; requires feedbackable_type, feedbackable_id, score • update — change score/reason/commen

Manage Notes Bulk

Bulk operations on notes — atomic multi-note updates and deletions for the /notes management UI. WHEN TO USE: Apply the same change to many notes at once: tag add/remove, set/clear embedded oppy, change visibility/status, archive or delete in batch. For single-note edits use manage_notes. ENDPOINTS: POST /api/notes_bulk/update and POST /api/notes_bulk/delete. Max 100 note_ids per call. Operations run inside a transaction; partial failures are reported per-id rather than aborting the batch. UP

Manage Events

Manage events (audit trail/activity log). Events link to Contacts, Conversations, Messages, Notes. The log holds millions of rows per account — for any "how many / breakdown / trend" question use action: aggregate, never list. list is for inspecting individual recent rows only. AGGREGATE: group_by one or more of event_type, source, day, week, month, channel_id, author_role, delivery_method. Filters below apply BEFORE aggregation. compare_prior:true adds prior-period counts + % change. Returns b

Manage Browser

Control a headless browser for web automation. Reach decisions by reading the DOM, not by staring at screenshots. SCHEMA: Playwright batch actions use Playwright Page/Locator API names as operation (goto, click, fill, snapshot, …). Same vocabulary as Microsoft Playwright MCP browser_* tools. action=help returns full reference (topic: playwright|locators|examples|errors). Validation errors include guidance + example — fix and retry. RECOMMENDED FLOW: 1. create_command_session (no args). 2. acti

Manage Twilio

Manage Twilio phone numbers, compliance, and SIP infrastructure (read-only). channel_id: Scopes to channel's subaccount. Required for all actions except get_phone_number. get_phone_number: Requires phone_number_sid (PN...). Actions: list_phone_numbers, get_phone_number, get_compliance_status, list_trust_products, get_a2p_status, list_trunks.

Manage Calendar

Manage Google Calendar events — search, view, create, update, delete, analytics. ACTIONS: - status: Check if Google Calendar is connected + email - list_calendars: List all accessible Google Calendars - list_events: Search/list events. Requires start_time + end_time. Use query for free-text search across title, description, location, attendees (e.g. query: "Shawn" finds all events mentioning Shawn). Use broad time ranges with query to find past events. Set show_deleted: true to include cancelle

Manage Automation Rules

Manage automation rules (event-driven triggers). Rules match events and execute actions. CREATE: name + trigger_event (e.g. "account.invite_sent") + action_type + action_config. action_type options: sync_card → {board_id, list_id, title_template}. send_notification → {webhook_url, message_template}. send_webhook → {webhook_url, method (POST/PUT/PATCH), headers, body_template, secret} (generic webhook with full event payload). create_list_item → {board_id, list_id, title_template, subtitle_templ

Manage Loops

Manage Loops — standing instructions that run on a schedule (account-scoped, admin-only). A Loop = a prompt + a schedule + a target Oppy (channel). Each fire posts the prompt into a fresh conversation on that Oppy, which executes it with full admin tools. ACTIONS: - list: List loops (filters: channel_id, status, last_outcome, q search; paginated) - get: Full loop + next 3 run times + last 5 runs (requires loop_id) - create: New loop. Requires name, prompt (20-4000 chars — say where the result s

Manage Calendars

Manage managed calendar connections and channel-to-calendar assignments. DISTINCT from manage_calendar (which handles event-level CRUD + analytics). ACTIONS: - list: List all managed calendars for the account (with channel assignments). Start broad — call with no filters; the list is account-scoped and usually small. - get: Get a single managed calendar by ID - add: Add calendars to the account (requires refresh_token, email, calendars array) - create: Create a BRAND-NEW secondary calendar insi

Manage Files

Oppy Files (HabitatFS): upload, organize, analyze, and search account files. Actions: help, upload, list, get, update, move, share, delete, analyze, content, search, status. CALL help (topic:overview|visibility|sharing|search|analysis) before assuming a limit — this tool ships mid-rollout and some actions are honest placeholders, not bugs: • share -> grants/updates access (grantee_type + grantee_id + access, optional expires_at); pass revoke:true to remove a grant instead • analyze -> enqueues

Note Audio

Generate or fetch cached TTS audio for a note. Audio is stored in note.metadata.audio with body_hash + voice_id keys, so re-running with the same body returns the cached URL. Voice precedence: explicit voice_id > Channel.voice_settings.voice_id (when note.metadata.embedded_channel_id is set) > service default. Action 'get' returns cached audio (or status: "generating" if it kicked off async generation). Action 'generate' synchronously generates and waits for the URL.

Ask Oppy

Ask a teammate oppy (another oppy caller_channel_id is allowed to reach — call list_teammates to see who) a question, agent-to-agent — or fan out the same question to up to 5 at once with 'teammates'. Modeled on the Account Concierge conversation contract. Resolve teammate(s) by channel id, team_id, embed_key, or assistant_name (a bare first name works even when the channel is named "First (Role)"); the target must be in caller_channel_id's reachable roster (an account_concierge can reach every

List Teammates

List the teammate oppies caller_channel_id can reach with ask_oppy. Returns each teammate's name and the addresses (team_id, embed_key, channel_id) you can pass to ask_oppy.

Ask Oppy Help

Get help/docs on agent-to-agent asking (ask_oppy, list_teammates): addressing a teammate, polling for an answer, and examples.

Manage Tools

Inspect and safely evolve the Oppy TOOL REGISTRY (the comms_tool_definitions rows that describe every tool the platform can expose to an LLM or over MCP). SUPER-ADMIN ONLY. Every action here reads or writes GLOBAL, cross-account platform data and requires an admin-scope API key or a platform-superadmin session. An account_admin key gets 403 — there is no account-scoped version of this tool. ACTIONS: • list — every tool definition: id, name, status, registry_state, revision, updated_at. Filter

Manage Prompts

Inspect the Oppy PROMPT REGISTRY — the prompt_template notes in the platform registry account that supply system-prompt fragment TEXT at render time. SUPER-ADMIN ONLY. One registry account serves every account's prompts, so this is GLOBAL cross-account data: it needs an admin-scope API key or a platform-superadmin session. An account_admin key gets 403. ACTIONS: • list — every seeded prompt fragment: name, note_id, frontmatter version, description, byte size, updated_at, plus the registry acco