Send & Retain Emails

Create a sender identity (from name + address) on a VERIFIED sending domain. Refused while the domain is unverified. The first sender becomes the project default.

email_create_sender

Create a template (react.email TSX, imports limited to react + @react-email/components, one default export) with a draft v1. Category decides who an unsubscribe blocks: 'transactional' (receipts, resets — still delivered to unsubscribed contacts) vs 'lifecycle' (marketing email — blocked once a contact unsubscribes). Every send carries one-click unsubscribe headers either way. Use the COMPANY's brand from the project brief. For the 8 standard emails, pass `starter` to begin from a brand-filled baseline instead of authoring from scratch — then rewrite the copy in the company's voice. Then renderTemplate to iterate.

email_create_template

Register an HTTPS endpoint to receive email events (delivered, bounced, opened, …) so the customer's system does not have to poll. Returns the endpoint WITHOUT its signing secret — the operator copies that from the dashboard.

email_create_webhook_endpoint

Archive an automation (paused only; running contacts' runs are canceled). An explicit human decision.

email_delete_automation

Permanently delete one contact (a data-deletion request). Removes the profile, attributes and tags; the message log keeps its rows. Does NOT suppress the address — a later event or send recreates the contact, so use addSuppression as well when the person asked not to be emailed.

email_delete_contact

Delete a sending domain: removes it from the project (its senders go with it) AND from the provider account unless another project still uses it. Sends from it fail afterwards. Refused while the project default sender is on it and other senders exist elsewhere.

email_delete_domain

Delete a segment. Automations already triggered by segment-entry keep their enrolled runs; new enrollments stop. An explicit human decision.

email_delete_segment

Delete a sender identity. Refused for the default sender while other senders exist (promote another first). Templates pinning it fall back to the project default.

email_delete_sender

Archive a template (soft delete; message history keeps pointing at it). Refused if an enabled automation references it. An explicit human decision.

email_delete_template

Delete a webhook endpoint permanently, along with its delivery log. To pause delivery instead, set enabled: false.

email_delete_webhook_endpoint

Clone an automation and all its steps into a new PAUSED automation (delays, prop overrides, A/B variants, send windows preserved). Useful to fork a proven automation for a variant or a new segment.

email_duplicate_automation

Manually emit a contact event — the way to TEST-DRIVE automation triggers end to end (enrollment happens exactly as with API events). Production events come from the company's app via POST /api/v1/events.

email_emit_contact_event

Full automation detail: config + ordered steps + run counts per status. Each step carries `waiting` — how many runs are parked on it right now, when the next one is due, and how many are overdue.

email_get_automation

Per-step and per-variant funnel for an automation: sent, delivered, opened, clicked, bounced (from message + event data). Keyed by step, with an A/B winner readout that calls a leader only once each arm has enough volume and the gap is material.

email_get_automation_metrics

Read the company's brand kit (logo, colors, fonts, voice, sign-off, footer address, links) and website. Call before authoring or reviewing any email so it uses the COMPANY's identity, not the app's. What the company DOES lives in its Canon — read that with the knowledge tools.

email_get_brand

Sending-setup status for the scoped company: provider connection (masked key), domains with per-record DNS state, senders, webhook registration, kill switch, and `settingsUrl` — the sending settings page where the operator connects a provider or the platform they are migrating off, adds domains and senders, and mints API keys. Call before any setup step.

email_get_connection_status

One contact: profile + suppression state + recent events + recent messages.

email_get_contact

Aggregate delivery/engagement metrics for a period (default 7 days): totals + rates, grouped by template and by day. complaintRatePct is complaints ÷ fbl_delivered (mail to Yahoo/Outlook and the other inboxes that report spam — Gmail and iCloud never do); at 0.08% or above, stop and investigate.

email_get_email_metrics

Revenue attributed to email from the company's connected PostHog project, plus the per-utm_campaign breakdown and total revenue for the same window. Attribution is LAST touch: a purchase is credited to the session an email link opened, so revenue landing in a later session is not counted — say so when quoting the number. Returns configured:false when PostHog or the revenue event isn't set up.

email_get_email_revenue

One message + its full event timeline (sent → delivered → opened/clicked, bounces).

email_get_message

Day-by-day metric trends from the pre-aggregated daily rollup (email_daily_stats), with the most recent days recomputed live so today and late-arriving bounces are included — cheaper than scanning the message log for long ranges. Each day is a send-day cohort: an event counts on the day its message was SENT, not the day it arrived. Returns a per-day series (sent/delivered/fbl_delivered/opened/clicked/bounced/complained/unsubscribed) plus totals. Complaint rate = complained ÷ fbl_delivered (mail to Yahoo/Outlook and the other inboxes that report spam; Gmail and iCloud never do), never ÷ sent. Default 30 days.

email_get_metrics_trends

The guided setup's ten steps for the scoped company, each with its address (1.1–3.5), title, phase and whether it is done — the same list the operator sees in the dashboard. Call it before describing progress or picking what to do next.

email_get_onboarding_steps

Ranked, evidence-backed action feed for a company's email — deliverability risks (complaints/bounces), setup gaps (unverified domain, kill switch on), conversion opportunities (A/B winners ready to promote, zero-open templates), and hygiene (stale drafts). Ground optimization answers in this. Each action carries evidence; the promote-winner action carries the exact promoteAbWinner call to apply it.

email_get_optimization_plan

Read the sending guardrails: kill switch (sendsPaused), daily send cap, UTM tagging, default locale, and how many emails went out today — read this before changing any of them.

email_get_project_settings

Background-job queue health for the whole workspace: pending jobs due now, age of the oldest pending job, in-flight count, and dead-letter count. A high or growing pendingDueNow / oldest age means the worker is wedged (e.g. it can't reach the DB) and scheduled/automation sends are backing up. Org-scoped.

email_get_queue_health

Read one pulled flow's steps in order — waits, emails and their subject lines, branches. Use it to restate what a flow does today before proposing our version, and to lift subject lines and cadence rather than reinventing them. Honour `partial`: a partial flow's steps are incomplete and you must say so instead of presenting them as the whole flow.

email_get_source_flow

Full TSX source + subject + variables of a template version (default: latest).

email_get_template

Bulk-import contacts when migrating a company in (CSV rows parsed to entries). Max 500 per call; repeat for more. Attributes merge on existing contacts.

email_import_contacts

Bulk-import suppressions when migrating a company in (from the old provider's suppression export or a CSV). Run BEFORE the first real send — re-mailing known bounces/complaints damages a new domain's reputation. Each imported address stops receiving mail from this project at once, an existing `unsubscribe` row is raised to `manual`, and any automation run in progress for the address ends; removing the suppression later does not restart those runs. Import a source's bounces/complaints as `manual` with the source's own label in `note` (`manual` blocks the same sends, and unlike a complaint it can be removed). Max 1000 per call; repeat for more.

email_import_suppressions

Per-contact runs of an automation: state, current step, next send time.

email_list_automation_runs

List the company's automations with status, trigger, and step count.

email_list_automations

List contacts (newest first). Filter by attribute equality or by tag when needed.

email_list_contacts

Event catalog: the contact-event names this project has received, with volume and last-seen — the vocabulary automations can trigger on. Use before designing a trigger to confirm the exact event name (and catch typos).

email_list_events

List the operator's projects (one project = one company) with status and website. Use first when the operator asks something open-ended, and before any company-scoped work — it returns the projectId every company-scoped tool needs.

email_list_projects

List the company's contact segments (saved filters) with their persisted member counts.

email_list_segments

List the company's sender identities.

email_list_senders

Catalog of business archetypes (saas / ecommerce / newsletter-media / marketplace) and the packs each installs (a pack is a starter set of paused automations). Call this first to confirm the archetype and pack selection with the human before bootstrapCompany.

email_list_sequence_packs

List the flows we pulled from the platform the company is leaving. Call this BEFORE proposing an email automation programme for any company that has connected a source — designing from scratch over the top of eleven existing flows is the failure this exists to prevent. Returns names, status, trigger and step counts; use getSourceFlow for the steps of one.

email_list_source_flows

List suppressed addresses with reason (bounce/complaint/manual/unsubscribe/invalid). `invalid` = verified undeliverable by MillionVerifier before we ever sent.

email_list_suppressions

Version history of a template (status, variant, author, created).

email_list_template_versions