/minutes-x1-send-meeting

Send one of the user's own meetings to their X1 household for review. Minutes supplies the meeting's outcomes. X1 decides who the sender is, which household it goes to, and what gets matched, and the user approves the send in X1. The meeting lands in the user's own review queue. Nothing reaches the household record until they confirm each item, and no professional sees it.

Required connections

This workflow needs both the local Minutes MCP and the official X1 MCP. Call X1 get_user_capabilities first. If submit_my_meeting or request_human_confirmation isn't mounted, stop: X1 hasn't turned meeting sends on for this account yet. Don't substitute another X1 write tool, invent an endpoint, or save the meeting somewhere else in X1.

Before using dueStatement or detail, inspect the mounted submit_my_meeting input schema from MCP tools/list and check its meeting.actionItems item properties. A mounted tool name alone does not prove support for a field. If that schema is unavailable, an available X1 get_user_capabilities action proposal contract for submit_my_meeting may supply the argument schema; capability discovery never grants approval. If a needed field is absent or neither discovery path supplies its schema, stop before requesting a send and ask: “Can you update or reconnect X1 so it accepts this meeting's original timing or detail?” Do not silently drop conditional timing or rewrite a task to work around an older backend.

Workflow