Native MCPWorkflows
In developmentDraft, test and send a newsletter
Save and edit a Native newsletter, send yourself a test, review recipients, approve a revision and verify delivery or cancellation.
Before you draft
#Choose the brand, read Newsletter setup, and prepare a Native mailing list. The assistant can save drafts before delivery is ready, but it must report that sending is blocked. Use returned identifiers throughout this workflow; ids in the examples are fictional.
Give the assistant a useful brief
#Text
For Harbour Bakery, draft a Norwegian email for our Bakery updates list about Saturday’s sourdough class at 10:00, NOK 650. Use our Native brand voice and confirmed product information. Include a short opening, what participants learn, and a booking button to https://example.com/classes. Save it in Native and show me the draft. Do not send it yet.The assistant can read get_brand_voice, relevant products, approved posts and brand-library images. It should confirm missing prices, dates and links rather than invent them. create_newsletter_draft saves content written by the connected assistant; it does not invoke Native’s own AI generator or send mail.
Save a real Native draft
#A new draft needs a UUID draftId, title, subject, preheader, language, audience description, objective and 1–12 blocks. Blocks can be text, a brand-owned library image, a button or a signature. Image blocks use returned assetId values, not remote URLs or invented images. Native validates and renders the draft with its brand appearance.
create_newsletter_draft arguments — fictional ids
{
"brandId": "11111111-1111-4111-8111-111111111111",
"draftId": "33333333-3333-4333-8333-333333333333",
"title": "Saturday sourdough class",
"subject": "Join our Saturday class, {first_name}",
"preheader": "Learn to bake with us at 10:00",
"language": "nb",
"audience": "Bakery updates subscribers",
"objective": "Fill the remaining class places",
"blocks": [
{"type": "text", "heading": "Bake with us", "text": "Our Saturday class starts at 10:00 and costs NOK 650. Learn to mix, shape and bake your own sourdough."},
{"type": "button", "label": "Book your place", "href": "https://example.com/classes"}
],
"personalization": {"nameFallback": "bakervenn"}
}Keep draftId stable after a timeout or retry. Use get_newsletter_draft to read the saved document, currentRevision and recipient selection. Its appUrl opens the draft in Native. Use list_newsletter_drafts to find an existing draft before creating another.
Review and edit the saved revision
#Check the subject, preview text, facts, images, links and footer. To edit, read the current revision and pass it as baseRevision to update_newsletter_draft. Omitted fields stay unchanged. Supplying changes.blocks replaces the complete block list, so preserve all content outside the requested edit.
A stale base revision is rejected with newsletter_changed. Read the latest draft before deciding how to apply the edit. An approved or sent draft cannot be silently rewritten. After any edit, review the saved content again and refresh recipient review when needed.
Send yourself a test
#Text
Send me a test of the latest saved newsletter revision using an available Native preview option. Show which signed-in address will receive it. Do not send to the mailing list.send_newsletter_test takes brandId, draftId, revision, a stable UUID requestId and transport. Use {"provider":"RESEND"} only when setup reports that preview route available, or {"provider":"ZERNIO","accountId":"<connected mailbox id>"} using an id from get_newsletter_setup → preview.mailboxes. Connect a missing mailbox in Native first. Live email must be enabled. The recipient comes from the signed-in account and cannot be supplied as a different address.
A test creates no campaign, subscriber, recipient selection or approval. Review the test and the Native draft before proceeding. Its personalized values come from the reviewer’s details. A successful test is not proof that your production domain is verified or every subscriber has the same contact fields.
Review and save the exact recipients
#- Read the final saved draft. Call
review_newsletter_recipientswith itsdraftId,revisionand the chosen NativeaudienceId. - Show the list name, subject, revision, total members, subscribed count and excluded counts for unsubscribed, bounced and complained contacts. The response’s
subscribedcount is the current eligible count. - When the user chooses those recipients, call
select_newsletter_recipientswith thatreviewTokenand the latestexpectedSelectionId, ornullif there is no selection. - Read the returned
selection: keep itsid,recipientToken,revision,selected,eligible,excludedSinceSelectionandstalestate. This saves preparation only.
The review token represents actual contact identities and statuses, not just a total. If the list changes before selection, review it again. Later list additions are not silently added to a saved selection. Unsubscribes or other exclusions can reduce eligibility; an approval with an out-of-date recipient token must be reviewed again. Selection above 50,000 contacts requires support.
Approve the content, recipients, sender and timing
#Before approval, show the saved subject and content, revision, list, eligible and excluded counts, resolved sender, reply address, tracking and any scheduled time. Copy connection.preparedSender and connection.nativeTracking from a fresh setup read. Obtain the user’s explicit approval of those facts.
approve_newsletter_delivery requires brandId, draftId, revision, selectionId, recipientToken, the exact sender, tracking and approved: true. It returns a delivery id. This records an immutable approval and sends nothing.
Send now or schedule once
#A send request
I approve the saved version you just showed, the displayed sender and tracking, and the reviewed Bakery updates recipient selection. Send that newsletter now and show the resulting delivery state.Within that explicit request, call send_newsletter with the approved deliveryId. For a scheduled send, include an ISO 8601 scheduledAt with an offset when creating the approval, then call send_newsletter on its returned id. The time must be at least five minutes in the future. Resolve the intended date and timezone before approving.
The send action requires Native’s existing live-delivery switch, configured transport and task queue, ready sender and valid approved state. It cannot bypass an unavailable domain or provider. The MCP settings tool does not enable recurring Autopilot campaigns. A one-time schedule does not authorize a repeating newsletter.
Verify what happened
#After sending, scheduling, cancellation or a timeout, call get_newsletter_deliveries with the draft id. Report the actual delivery state and recipient progress. Keep the delivery id so the same attempt can be inspected later.
| State | What you can conclude |
|---|---|
APPROVED | Approval is recorded. Sending has not started. |
SCHEDULED | Delivery is booked for the approved time. |
SENDING | Delivery is underway; inspect pending, submitted, skipped and uncertain recipients. |
SUBMITTED | The provider accepted submissions. This is not proof of inbox delivery. |
SENT | The delivery reports sent. Do not claim every recipient received or opened it. |
UNKNOWN | One or more outcomes need reconciliation. Read state before retrying. |
NO_RECIPIENTS | There are no remaining eligible recipients for this attempt. |
CANCELLING, CANCELLED, CANCELLED_PARTIAL | Cancellation is in progress, finished, or stopped only the remaining portion. Sent messages cannot be recalled. |
get_newsletter_results returns provider results when available. Native recipient progress is in get_newsletter_deliveries; a null results response is not a zero-performance campaign. Native-domain sending does not track opens or clicks. Social analytics are a different dataset.
Cancel or recover from uncertainty
#Use cancel_newsletter_delivery for the exact delivery the user asks to stop, then read its state again. Cancellation remains available if new newsletter creation is switched off, provided the user still has brand-admin access. It cannot recall sent mail and may leave a partial result.
After a lost response, do not create a new draft, approval or delivery to retry the same send. Read the saved draft and delivery history first. Keep the original ids and test request id. If Native reports a prerequisite failure, fix that requirement before another attempt. If it reports an uncertain submission, inspect or reconcile the existing attempt rather than guessing whether it sent.
Start with your Native account
Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.
