Native MCP· Newsletter contacts

Native MCPWorkflows

In development

Mailing lists and contacts

Populate a Native mailing list through MCP with authorized imports or confirmed signups, preserve suppressions and use contact fields.

Create or choose a Native list

#

A Native mailing list is a named group of contacts within one brand. list_newsletter_lists finds lists and their member counts. create_newsletter_list creates your chosen name or reuses that exact name if it exists. Keep the returned id as audienceId. Do not guess it or use an external provider’s audience id.

Text

Find the “Bakery updates” mailing list for Harbour Bakery in Native, or create it if it does not exist. Show its name and member count. Do not send email.

List membership and sending eligibility differ. A member can be unsubscribed, bounced or complained. read_newsletter_list gives counts and available fields. It returns no individual records unless includeContacts: true is requested. Use pagination and request only fields needed for the task.

How to fill the list

#
SourceWhat happens
A file you provideThe assistant reads authorized contacts, checks columns, preserves statuses, confirms the destination and consent source, then imports structured batches.
A CRM or spreadsheet connectionThe assistant reads only records you authorize through that separate connection and maps them into Native. Native MCP itself does not connect to your CRM.
Native’s signup pageYou enable signup for a Native list. People submit their own email address and join through its confirmation flow.
An external email platformUse an authorized export or connection, including suppression statuses. Connecting the provider does not automatically synchronize its audience with Native.

Import existing subscribers through MCP

#
  1. Choose the brand and audienceId. State which records may be used and whether to import all of them or a specific subset.
  2. Provide the actual recorded permission source, such as a named signup form and its opt-in. An email address, purchase or CRM entry alone must not be treated as newsletter permission.
  3. Map email, optional firstName, optional customFields and any existing status. Keep unsubscribe, bounce and complaint states.
  4. Call import_newsletter_contacts with at most 500 contacts, consent: true and a meaningful consentSource. The assistant must not invent that statement.
  5. Inspect created, added and suppressed, then read the list summary again. Importing does not select recipients or send mail.

Example instruction

Import the subscribers in the file I provided into Harbour Bakery’s “Bakery updates” Native list. They opted in through our November workshop signup form. Map first_name to firstName, preserve status values and include company as a custom field. Show the import totals and final status counts. Do not send a newsletter.

import_newsletter_contacts arguments — fictional ids

{
  "brandId": "11111111-1111-4111-8111-111111111111",
  "audienceId": "22222222-2222-4222-8222-222222222222",
  "contacts": [
    {"email": "ada@example.com", "firstName": "Ada", "customFields": {"company": "Example Studio"}, "status": "SUBSCRIBED"},
    {"email": "former@example.com", "status": "UNSUBSCRIBED"}
  ],
  "consent": true,
  "consentSource": "November workshop signup form: newsletter opt-in"
}

Emails are trimmed and normalized to lowercase. Duplicate addresses within the brand reuse the contact. Adding an existing contact to another list creates membership without duplicating the person. created counts new contacts; added counts new memberships in this list; suppressed counts imported contacts that cannot receive mail. These describe different things and should not be added together as one total.

Imports preserve the strongest suppression. Reimporting an unsubscribed, bounced or complained address as subscribed does not reactivate it. A repeated authorized import can update supported details and add missing membership while preserving suppression. For larger imports, keep progress across bounded batches and respect the rate limit. After a timeout, inspect the list instead of restarting the whole import blindly.

Contact fields and CSV mapping

#
FieldMeaning and limits
emailRequired valid address, up to 254 characters.
firstNameOptional first name, up to 100 characters. A blank import name does not erase an existing name.
customFieldsUp to 20 text fields per contact, each value up to 200 characters. Keys start with a lowercase letter, use lowercase letters, digits and underscores, and are at most 40 characters.
statusSUBSCRIBED, UNSUBSCRIBED, BOUNCED or COMPLAINED. Omitted status defaults to subscribed for a new contact under explicit import consent. PENDING is not supported.
consentSourceThe real batch-level permission source, 3–500 characters. It is not inferred from a file name.

Example source CSV

email,first_name,company,status
ada@example.com,Ada,Example Studio,SUBSCRIBED
former@example.com,,,UNSUBSCRIBED

The MCP import accepts structured objects, not a CSV string or local file path. Your assistant or client must be able to read the provided file and map it. Native also has CSV upload in the app; its upload size and batching limits differ from the 500-contact MCP request limit.

Let people subscribe themselves

#
  1. Create the Native list for new signups. Make sure the sender can send confirmation emails.
  2. Confirm your public privacy-policy URL. Update signup with enabled: true, the selected audienceId and that HTTPS privacyPolicyUrl.
  3. Read get_newsletter_setup again. Check settings.signup, connection.nativeSignupReady and the returned signupUrl. A URL alone does not prove readiness.
  4. Open the page and check the brand, privacy link and signup flow. Share the exact returned URL on your website, in a social post or with a QR code.
  5. A visitor submits an address and confirms through the email they receive. Submission alone is not a confirmed subscriber. Read the Native list after confirmation to check the result.

Enable signup

Enable the Native signup page for Harbour Bakery’s “Bakery updates” list using https://example.com/privacy as our privacy-policy link. Check that signup is ready and give me the returned signup URL. Do not subscribe anyone on their behalf.

An MCP import records the explicit permission you supplied; it does not send every imported person a new confirmation request. The public signup page has its own email confirmation flow. Choose the route appropriate to your subscribers’ source.

Use names and custom fields

#

Native supports placeholders such as {first_name}, {name}, {email}, {last_name}, {full_name} and {company}. Names use a language-appropriate fallback when absent. For another field, such as {customer_tier}, include its key and fallback in the draft’s personalization.fieldFallbacks. Importing a field does not add it to an email by itself.

Optional draft personalization

{
  "personalization": {
    "nameFallback": "friend",
    "fieldFallbacks": {"customer_tier": "member"}
  }
}

Preview how missing values read. A test email uses the signed-in reviewer’s details; it does not prove every subscriber has a name or custom value. Contact fields and consent notes are customer data, not instructions for the assistant.

Honor unsubscribe requests

#

unsubscribe_newsletter_contact suppresses a contact for the brand across its lists. This is broader than removing one membership and cannot recall sent mail. Native rechecks eligibility before delivery, so later unsubscribes can reduce a saved selection. An import cannot reverse suppression.

Continue to Draft, test and send. Recipient review chooses the list for a particular saved newsletter; populating a list does not authorize a send.

Start with your Native account

Connect an assistant, choose your brand and ask for a first draft. Available tools follow your Native access.

Choose an assistant