Complete conversations
Messages are threaded by reply references. Replies and follow-ups remain in the original conversation.
Start with a programmable inbox. Receive context, prepare replies, and connect contacts and events to follow-up messages. The workspace keeps each step visible to you.
Create a dedicated inbox for each job. Start with @mailly.site or connect your brand domain so notifications and replies return to the same address.
Create your first inboxMessages are threaded by reply references. Replies and follow-ups remain in the original conversation.
Read HTML and plain text, retrieve attachments, and strip quoted history when processing a message.
Set a workspace inbox webhook or a separate endpoint for each address.
Inspect mail from the web, API, CLI, SMTP, and campaigns in one sent-mail view.
Email is independent of your model and orchestration. Choose how your agent works and keep clear control over sending.
Define email resources with the CLI and API, then inspect and control them in the workspace. Notifications, outreach, and lifecycle mail share templates, contacts, and delivery data.
Read the automation guideYour application reports setup completion
Use a published template and contact variables
Continue according to your Workflow definition
Review the run and mail for each contact
Versioned content, variables, localized templates, previews, and test sends.
Sync attributes, manage subscription preferences, and prepare static lists or dynamic segments.
Freeze content and audience, then track progress and per-recipient results.
Define event triggers, sends, and wait steps. Inspect, pause, and resume runs.
Automation does not mean handing over every permission. Reading, drafting, approval, and delivery remain inspectable steps.
MCP exposes tools within the granted scopes. Reads and writes check workspace ownership. Keep API keys in trusted clients or on your server.
Draft approval checks the reviewed text and revision. Reply approvals use stable idempotency keys to avoid a second delivery on retries.
Inbox and delivery webhooks use HMAC-SHA256 signatures. Failed deliveries retry; your receiver should verify signatures and deduplicate event IDs.
Accepted requests, queue progress, and delivery are separate states. Inspect delivery, bounce, complaint, unsubscribe, and click events.
Hosted agents draft and do not approve their own sends. Remote MCP is available with OAuth in supported clients; see pricing for plans and usage billing.
View pricingStart with an address. Connect incoming mail, replies, and follow-ups in one workflow.