Nitrosend - AI Native Email

Compose and send an email or SMS to an audience. This is the default tool when users want to draft, write, or send an email. Creates a draft — use nitro_control_delivery to approve and send. Modes: create (new campaign), patch (update provided fields on an existing draft campaign), replace (replace draft campaign content/audience/schedule — requires confirm: true + campaign_id). Replace clears omitted audience and schedule instead of preserving stale targeting. Patch/replace cannot change the campaign channel; create a new campaign to switch between email and SMS. For manual sections without a composition_contract, read nitro://brand and nitro://schema; use nitro://email-marketing and nitro://email-design when deeper strategy or design context is needed. Email modes (channel auto-detected as "email" when sections or template_id provided): - **Host-composed contract** — composition_mode: "intent" returns a compact composition_contract. Fill next_call with subject/preheader/sections, optionally dry-run with composition_mode: "validate", then persist with composition_mode: "draft". - **Inline** — sections + subject (required) — compose email design directly - **Clone** — template_id — clone design from existing template, optionally override subject - **Plain text** — body + subject — simple text email without design SMS mode: channel: "sms" + body (required) Goal-driven email requests use the host-composed contract path by default; Nitrosend compiles the brief and validates/persists, while the agent host writes the draft. Contract-loop states return as normal tool results with composition_status and isError=false. Preserve explicit user constraints: exact copy requests, URLs, offers, product details, sender fields, audience, schedule, tone, and legal copy. Use $contract_ref for high-risk literals, e.g. {"$contract_ref":"hard_constraints.urls.primary_cta"}. SMS and nitro_send_message simple sends are exempt. Retry safety: pass the same idempotency_key on retry to avoid duplicate campaigns.

Create or replace an automation flow from trigger + steps array. Creates a draft — use nitro_control_delivery to approve and activate. For goal or intent-driven email flows, use composition_mode="intent" first. Nitrosend returns a compact composition_contract; the agent host writes the steps, can validate without persistence, then calls this same tool with composition_mode="draft". Contract-loop states return as normal tool results with composition_status and isError=false. Modes: create (new flow), replace (rebuild existing — requires confirm: true + flow_id), patch (rename only — requires flow_id). Step types: email (subject + design or body), sms (body), wait (duration in seconds), split (filters + yes/no branches, no nesting), emit_event (fire event for contact to trigger other flows), webhook (url + optional method/headers/body), subscribe (opt-in contact to channel), unsubscribe (opt-out contact from channel). Retry safety: pass the same idempotency_key on retry to avoid duplicate flows.

Configure account sender defaults (from_name, from_email, reply_to) and test email recipients. Call with no fields to read current config. from_email must be authorized by a verified sending domain.

Configure BYO email provider credentials or check provider status.

Manage delivery lifecycle for flows and campaigns. State: draft -> approve -> live/schedule <> pause, cancel -> archive. Use archive for cleanup history, or delete confirmed never-sent drafts.

Define a contact segment with explicit filters and preview. Defaults to preview_only: true (dry preview without saving). Set preview_only: false and provide a name to persist.

Get email analytics with trends, benchmarks, and recommendations.

Get current account health, onboarding status, and recommendations.

Import contacts from inline records (< 100) or reference a pre-uploaded CSV import. Email contacts are auto-subscribed by default. For SMS-only contacts, set opt_in: true explicitly (TCPA compliance).

Ingest a local or chat-attached image into Nitrosend and return a Nitro CDN URL you can place directly into email design fields like image.src, product.image_url, hero.background_url, or theme.logo_url. Use this only for local/chat images. If the user already has a public remote URL, use that URL directly in compose tools instead.