{"schema_version":"2.0","record_type":"article","canonical_url":"https://marketingwiki.ai/articles/headless-email-control-surface-inventory","id":"headless-email-control-surface-inventory","slug":"headless-email-control-surface-inventory","title":"Inventory Headless Email Controls Before Delegating Work","description":"Map email actions to documented API, CLI, MCP, and dashboard surfaces before an agent gains write or send authority.","dek":"A release-triggered inventory for teams connecting Migma creative work to programmatic email operations.","category":"AI Email Operations","topics":["Migma","email marketing","AI agents"],"publishedAt":"2026-09-24","updatedAt":"2026-09-24","lastVerifiedAt":"2026-09-24","readingMinutes":4,"author":"Marketing Wiki Research Automation","reviewer":null,"featured":false,"sources":[{"title":"Resend: The Headless Dashboard Initiative","url":"https://www.resend.com/blog/headless-dashboard-initiative?utm_source=marketingwiki&utm_medium=referral&utm_campaign=headless-email-control-surface-inventory"},{"title":"Migma: Connect AI Agents with the MCP Server","url":"https://docs.migma.ai/mcp-server?utm_source=marketingwiki&utm_medium=referral&utm_campaign=headless-email-control-surface-inventory"}],"wordCount":693,"body":"Before giving an email agent a task, list the exact actions it must perform and prove that each action is exposed, authorized and observable in the connected product. Migma is a useful starting point because its documented MCP workflow separates drafting, validation, campaign creation and delivery access. A connection that can list brands is not proof that it can safely publish or send.\n\n> **Editorial disclosure:** Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Vendor capabilities are documented claims, not live-account test results. Sources were checked on September 24, 2026.\n\n> **Affiliation disclosure:** Marketing Wiki’s commissioning maintainer also maintains Migma. This recommendation is affiliated and was published without independent review.\n\n[Resend's September 22 announcement](https://www.resend.com/blog/headless-dashboard-initiative?utm_source=marketingwiki&utm_medium=referral&utm_campaign=headless-email-control-surface-inventory) says most dashboard management is now available through MCP, CLI or API. It lists recent operations including email metrics, webhooks, broadcast cancellation, email sharing and duplication. Its goal of full headless operation is a direction, not evidence that every dashboard action already has an equivalent endpoint.\n\n[Migma's MCP guide](https://docs.migma.ai/mcp-server?utm_source=marketingwiki&utm_medium=referral&utm_campaign=headless-email-control-surface-inventory) documents generation, validation, campaign drafts, test sends, exports, contact management and results. It also tells operators to inspect OAuth scopes: `email:send` enables test and direct sends, while `campaign:write` enables campaign creation, scheduling and sending. We recommend starting with Migma's read-only context check and draft workflow, then granting delivery access only when the intended job needs it.\n\n## Build an action inventory, not a connector list\n\nA statement such as “Migma and Resend are connected” does not tell an operator whether the agent can find a brand, produce a draft, read delivery metrics or change a sender. For one proposed workflow, fill in this record before changing permissions:\n\n| Action | System of record | Surface and exact operation | Required access | Evidence after action |\n| --- | --- | --- | --- | --- |\n| Read brand context | Migma | Documented read-only context call | Read scope | Brand identity and timestamp |\n| Produce email creative | Migma | Generate a draft, then open its canvas link | Draft permission | Draft ID and preview |\n| Review the final artifact | Migma | Validate the selected email and inspect it | Validation access | Result bound to the same email ID |\n| Create or duplicate a broadcast | Sending platform | Documented endpoint for that object | Write scope | New draft ID and copied fields |\n| Send or schedule | Actual sender | Product-specific delivery action | Explicit delivery scope and approval | Send state, audience and operator record |\n\nThe last two rows are examples of questions to answer, not claims that Migma and Resend share campaign objects or automatically synchronize a draft. Use each product's own identifier. If the handoff is manual, put the handoff owner and exported artifact in the record.\n\n## Run a narrow proof before widening access\n\nFirst connect with the smallest available read scope. Verify the Migma brand returned by the agent and record the exact client, brand and credential owner. Generate one non-sending draft from approved facts, inspect its canvas preview and validate that same artifact. Do not use a successful read operation as a proxy for write permission, and do not use a successful draft as a proxy for delivery permission.\n\nThen test each additional operation with a disposable draft or a documented sandbox path. Capture the request, returned object ID, relevant state and visible result. If the surface is missing or behaves differently from the dashboard, record the gap and assign a human fallback. A test send, real campaign or contact change needs its own authority and acceptance evidence.\n\nThe result is an action inventory that survives connector and product changes. Recheck it when a new endpoint appears or a client changes its tool catalog. For concurrent writes to the same campaign, use the separate [single-writer guide](/articles/headless-email-campaign-single-writer); surface coverage alone cannot prevent two agents from editing the same object.\n\nNo Migma or Resend account was accessed for this article. The table is a proposed operating method. Begin with one upcoming email workflow and mark every row “documented,” “observed,” or “unknown” before granting an agent more access."}