From Yaplet, the assistant inside your dashboard, or a connected AI app, an AI can draft campaigns and write their emails, design email templates, look at screenshots of any saved email or template, build email automations, set up Newsletter Autopilot and give it topic ideas, add and organize subscribers, and read email statistics, your sending domain's setup and its deliverability, including the Gmail spam status. It looks actions up with find_actions and runs each one with the run tool for its kind — see MCP Server. Everything that makes an email actually go out stays with a person: the AI prepares the draft and tells you where to send it or switch it on.
Permission required: each action needs the same permission as its dashboard screen — Newsletter for subscribers, groups, segments, email templates, email previews and email stats (previewing a campaign's email, or making a template from one, also needs Newsletter → Campaigns; previewing an automation's email also needs Email automations); Newsletter → Campaigns for campaigns; Email automations for automations; Newsletter Autopilot for autopilots; Content sources for topic ideas; Settings → Email for the sending-domain check; and Settings → Domain for the deliverability status. An app connected by browser login also needs the Newsletter area ticked on the login screen, and the person the connection runs as needs the Yaplet assistant permission.
Brand limits apply. A team member limited to some brands reaches only those brands' autopilots and topic ideas — in Yaplet, in apps connected by browser login, and through API keys whose AI access they switched on.
Email automations, not chat workflows. The automations.* actions work on Marketing → Newsletter → Automations. Where something still says workflow — the workflow choice of newsletter.email_stats, or the /workflows web address — it means an email automation, never a scripted chat under Brand → Workflows.
Level is the access level an action needs. In Yaplet, every change and delete waits for you to click Confirm first.
| Action | Level | What it does |
|---|
campaigns.create | Change | Creates a draft campaign — name, subject, preheader, sender and recipients — optionally with its email copied from a template, a previous campaign or HTML you provide. |
campaigns.update | Change | Changes a draft campaign's name, subject, preheader, sender, recipients or email; only drafts can be changed. |
campaigns.write_with_ai | Change | Writes or rewrites a draft campaign's email with AI, in your Default template or a template you name, optionally with 1–3 AI images billed per image. Leave out the campaign and give a name, and it creates the draft and writes its email in one step. Uses AI credits. |
| Action | Level | What it does |
|---|
newsletter.preview_email | Read | Shows screenshots of a saved campaign email, automation email or template at computer and phone width, plus a short quality report. |
templates.create | Change | Creates a template — header, empty Content area, footer — from HTML the AI writes itself, from a previous campaign's email (its Content area emptied), or as an exact copy of another template. |
templates.update | Change | Renames a template or replaces its design with new HTML. Emails already made from it keep their own copy. |
templates.set_default | Change | Stars a template as your Default — the one AI writing starts from — or removes the star. |
templates.delete | Delete or send | Deletes one template for good; emails made from it keep their content. Refused while a newsletter autopilot uses it. The AI must repeat its exact name. |
| Action | Level | What it does |
|---|
automations.create | Change | Builds a new automation — trigger, steps and branches — from a plain description, always switched off. Uses AI credits. |
automations.update | Change | Renames an automation, sets its trigger settings directly, or sets its sending priority — low, normal or high (new automations start at normal). High mail is never held back during a Gmail slowdown, so use it for cart, order and welcome emails. |
automations.restructure_with_ai | Change | Adds, changes, reorders or removes steps from a plain description, but never removes a step whose email is already written. Every email step it keeps stays exactly as saved — its email, subject and finished state; change an email with automations.edit_email. Uses AI credits. |
automations.edit_email | Change | Sets one email step's subject, preheader, sender, or its email copied from a template, a campaign or HTML you provide. |
automations.write_email_with_ai | Change | Writes or rewrites one email step's email with AI, optionally with 1–3 AI images billed per image. Uses AI credits. |
automations.switch_off | Change | Switches an automation off. Everyone partway through it is dropped, and the answer says how many. It can never switch one on. |
automations.delete | Delete or send | Deletes one switched-off automation for good, with the emails of its steps — refused while another automation starts it. The AI must repeat its exact name. |
| Action | Level | What it does |
|---|
audience.preview_segment | Read | Counts the contacts a set of filters (or a saved segment) matches and shows a sample of 10, without saving anything. Filters can use the email provider (one of a fixed list, such as google, apple or microsoft) and the activity fields — last active, last opened, last clicked, clicks, emails received and last emailed — as well as the usual fields. |
subscribers.add | Change | Adds up to 500 contacts at once, optionally into existing groups. |
subscribers.update | Change | Edits one subscriber: name, custom fields, engagement score or state. The engagement score updates itself afterwards: an open adds 10, a click 50, and each email sent takes 10% off. It cannot change the email address — add the new address with subscribers.add and set the old one to Removed. |
subscribers.set_state | Change | Sets one state on up to 500 contacts at once — this is how people are unsubscribed or removed. |
subscribers.add_to_group | Change | Puts up to 500 existing contacts into a group. |
subscribers.remove_from_group | Change | Takes up to 500 contacts out of a group; they stay on your list. |
audience.create_group | Change | Creates a subscriber group. |
audience.rename_group | Change | Renames a subscriber group. |
audience.create_segment | Change | Creates a segment from filters and answers with how many contacts it matches, plus a sample. |
audience.update_segment | Change | Renames a segment or replaces its filters. |
| Action | Level | What it does |
|---|
autopilot.options | Read | Lists what an autopilot can be set up with — brands, sender addresses, templates, segments, groups and models — and, for one brand, its content sources and autopilots. |
autopilot.create | Change | Creates an autopilot for one brand, always switched off and with Require my approval on. |
autopilot.update | Change | Changes an autopilot's settings for its future issues; only the settings sent change. |
autopilot.set_enabled | Change | Switches an autopilot on or off; switching on is refused for an autopilot that sends without approval. Uses AI credits. |
autopilot.generate_sample | Change | Writes one sample issue now — a draft that is never sent. Once it is ready, it replaces the autopilot's earlier samples that never went out, so there is no need to cancel the previous one first. Uses AI credits. |
autopilot.cancel_issue | Change | Cancels a planned issue or a draft waiting for approval, so it is never sent. |
autopilot.rewrite_issue | Change | Writes a fresh issue for the same date in place of a waiting draft or a failed issue; also needs Newsletter → Campaigns. Uses AI credits. |
content_ideas.create | Change | Adds a topic idea — a title and a short brief — for a brand's autopilots; needs Content sources. |
content_ideas.update | Change | Changes a topic idea's text or which autopilots may use it; needs Content sources. |
autopilot.delete | Delete or send | Deletes one autopilot for good; the AI must repeat its exact name. |
content_ideas.delete | Delete or send | Deletes one topic idea for good; the AI must repeat its exact title. Needs Content sources. |
| Action | Level | What it does |
|---|
newsletter.email_stats | Read | Shows one campaign's or one email automation's numbers: sent, opened, clicked, bounced, complained, unsubscribed, failed and queued. Opened counts only opens at least a minute after sending, the same as the dashboard. |
newsletter.domain_setup_state | Read | Shows a sending domain's live setup — the exact DNS records to add and whether each one is found yet, the setup phase and the detected DNS provider; needs the Settings → Email permission. |
newsletter.deliverability_status | Read | Shows how a sending domain's email is doing, as its Deliverability tab does: delivery per email provider (sent, complaints, and bounces split into addresses that don't exist and mailboxes that are full or temporarily failing), whether sending is slowed or paused to protect the domain, and Gmail — the slowdown level (none, watch, act or severe) with the day it started, the day the hold should lift (act and severe only; watch is a warning that pauses growth and holds nothing) and whether sending is recovering, the last 28 days of Google's data with the estimated number of spam reports (it arrives 2 to 4 days late), the worst recent day and the campaigns and automations that most likely caused it, how many emails are on hold now and how many were released back to sending or dropped when the last hold lifted, and Google's sender checklist. Without a domain it reads the most recently added one; needs the Settings → Domain permission. |
- Every campaign an AI makes is a draft. The answer carries a link to it; you review it and send or schedule it from the dashboard.
- Writing with AI is one step. For a new campaign the AI gives
campaigns.write_with_ai a name and no existing campaign: it creates the draft and writes its email together, so in Yaplet that is one Confirm instead of two. It first checks that AI writing is allowed, so an organization without AI credits is not left with an empty draft. If the writing fails, the empty draft stays, and the answer names it so the AI can try again on it. Subject, sender and recipients can be set afterwards with campaigns.update. campaigns.create is for a draft you fill from a template, a previous campaign or HTML; for an email the AI writes, it uses campaigns.write_with_ai. - Your design stays yours. In your Default template (the starred one on the Templates page) or a template you name, the AI writes only inside the Content area — the header, footer and style stay exactly as designed. A template without a Content area is refused. Without a template, a draft that already has an email gets new content in its own layout (or a rewrite of what is there, if you ask for edits), and an empty draft gets a whole email designed by the AI.
- Recipients are all active subscribers, some segments, or some groups — one of the three.
- The AI designs templates itself. It writes the template's HTML — a header, an empty Content area where each email's content goes, and a footer — and no AI credits are used. HTML without a Content area is refused with the exact piece to add, and anything inside the Content area is removed when the template is saved. An exact copy of a template keeps its content. The AI does not need to add an unsubscribe link: the sending system adds one to every email.
- Every design change comes with a preview. When an AI creates or changes an email's or a template's design (
campaigns.create, campaigns.update, campaigns.write_with_ai, automations.edit_email, automations.write_email_with_ai, templates.create, templates.update), the answer includes screenshots at computer width (700px) and phone width (390px), plus a short report, so the AI sees what it made and can fix it. Renaming, or changing only a subject or the recipients, returns no preview. A template's empty Content area shows as a gray box. - What the report checks: images that failed to load or have no description (alt text), placeholder links (empty,
# or example.com), {{placeholders}} that no subscriber field fills, phrases spam filters dislike, whether Gmail would cut the email off (above 102 KB), and how much phone mail apps shrink an email that is wider than the screen. - A preview never blocks a change. If the screenshots can't be made — for example when many previews run at once and the answer says the screenshot service is busy — the change is still saved and the answer says why the preview is missing. The AI can look again later with
newsletter.preview_email. Making screenshots uses no AI credits.
Changing a template that an autopilot uses. A newsletter autopilot picks up its template's new design on its next issue. If that autopilot is switched on and sends without approval, the change is still saved, but the answer names the autopilot and warns that its next issue goes to subscribers in the new design without anyone seeing it first. To check issues before they go out, switch on Require my approval on the autopilot's page.
- It is created switched off. You switch it on yourself after checking it — with the switch on its row on the Automations page (Marketing → Newsletter → Automations), or in the builder. It can be switched on only once every step is finished and every email step has a written email.
- Email steps start with a subject only. The AI then writes each one with
automations.write_email_with_ai, or fills it with automations.edit_email. - A restructure keeps written emails. Steps the AI keeps stay exactly as they were — a kept email step keeps its subject and content even if you ask for a change in the same request; the AI changes those with
automations.edit_email or automations.write_email_with_ai. If the new structure would remove a step whose email is already written, nothing is changed and the AI tells you which step — remove it yourself in the dashboard, or ask for a structure that keeps it. The AI credits of that attempt are still used. - The AI can list and open your automations —
list_records and get_record with email_workflows — each with its trigger, whether it is switched on and whether every step is finished, and, when opened, its steps with their node IDs and email subjects.
Editing an automation that is switched on is allowed. A changed email or trigger applies to the next emails the automation sends. In Yaplet you confirm every change first; an outside AI app that is allowed to run actions without asking you can change a live automation before anyone has looked at it.
- List hygiene on every add. Invalid addresses, no-reply and system addresses, and disposable domains are skipped and counted. Addresses already on your list are left untouched.
- The states. The tool uses the state names New, Verified, Unsubscribed, Bounced, Complaint and Removed. The dashboard shows Verified as Subscribed and Complaint as Spam complaint.
- New contacts start as New and are verified automatically before they can be emailed. An AI can never set a contact to Verified. A contact that is Unsubscribed, Bounced, Complaint or Removed can only be moved to Removed by an AI. Nobody in your account can bring back an Unsubscribed, Bounced or Complaint contact, not even in the dashboard — only the person can subscribe again, through the subscribe link in an earlier email or a new confirmation email, and never after a complaint or a bounce. A Removed contact can be verified again by a person in the dashboard, unless its address unsubscribed, bounced or complained before. Bounced, Complaint and New are set by the system only.
- Custom fields must already exist. Fields the AI names that you don't have are reported back, never silently dropped.
- Your plan's subscriber limit applies, and each call handles at most 500 contacts.
- Check the segment numbers. Every segment save and preview returns the exact match count and a sample of 10 contacts. A campaign keeps a segment as it was when the segment was chosen there — choose it again in the campaign to pick up new filters.
- A new autopilot is off, with approval on. Its answer carries the cost estimate — issues per month, contacts reached, price per image — and the AI should tell you the numbers before it switches the autopilot on.
- Switched on by an AI, it still waits for you. The AI can switch on only an autopilot whose Require my approval is on, so every issue still waits for a person's Approve & send. It can switch any autopilot off.
- Samples and rewrites take a few minutes. The AI checks back until the issue is ready for review. An issue that is still being written cannot be canceled.
- The dashboard's limits apply: at most 10 autopilots per brand, one sample at a time, only sender addresses on verified domains, only templates with a Content area. See Newsletter Autopilot.
- Topic ideas reach every autopilot of the brand — newsletter and social posting, including ones that send or publish without approval — unless the AI limits an idea to some autopilots. An idea's text can be edited only until an autopilot writes from it. Up to 200 open ideas per brand; see Content sources.
- Send, schedule, pause, resume or cancel a campaign, or change one that is no longer a draft — do it in the dashboard under Marketing → Newsletter → Campaigns.
- Switch an email automation on — do it with the switch on its row under Marketing → Newsletter → Automations, or in the builder.
- Remove an automation step whose email is already written — remove it yourself in the automation builder.
- Delete a template that a newsletter autopilot uses — pick another template in each of those autopilots first; the refusal names them.
- Approve an autopilot issue — click Approve & send on the draft in the dashboard; see Issues and approval.
- Switch an autopilot's Require my approval off, or switch on an autopilot that sends without approval — do it on the autopilot's page under Marketing → Newsletter → Autopilot.
- Rewrite an issue of an autopilot that sends without approval, or change the settings of one that is switched on and sends without approval — a rewritten issue or a changed setting would go out with no person looking. Do it on the autopilot's page; the AI can still switch such an autopilot off.
- Delete subscribers, groups, segments or campaigns — an AI can only unsubscribe or remove a contact, which keeps the contact on your list. Deleting is done under Marketing → Newsletter.
- Set a contact to Verified, change a subscriber's email address, or bring back a removed contact — a person does this on the subscriber in the dashboard, under Marketing → Newsletter (a removed contact only if its address never unsubscribed, bounced or complained).
- Bring back an unsubscribed, bounced or complained contact — nobody in your account can, not even in the dashboard. Only the person can subscribe again, through the subscribe link in an earlier email or a new confirmation email, and never after a complaint or a bounce.
- Add or verify a sending domain, or buy the dedicated IP — the AI can only read a domain's setup. Domains are added under Settings → Connections → Emailing → Custom Domains; the dedicated IP is a paid add-on only a person can buy.
- "Draft a campaign about our spring sale in my default template, with one AI image, for the VIP group. I'll send it myself."
- "Design an email template for our brand: our logo in a dark blue header, and a footer with our address and social links. Then make it my default."
- "Show me how my March campaign looks on a phone."
- "Build a welcome automation: when someone subscribes, send a welcome email, wait 3 days, then send our top tips. Write both emails."
- "Add these 20 addresses to the newsletter and put them in the Beta Testers group."
- "Switch off my old onboarding automation, then delete it."
- "Set up a weekly tips newsletter for the Acme brand, every Monday at 9:00, written from our knowledge base, for the Customers group, and write me a sample first."
- "What were the open and click rates of my March campaign?"