SteelEngine Mailer

Send emails to your workspace and let SteelEngine handle them as tasks.

SteelEngine Mailer gives your workspace a dedicated email address. Forward or send emails to it and SteelEngine will process them as tasks — reading the subject, body, and any attachments, then replying to the thread with the result.

This means you can interact with SteelEngine directly from your email client without switching apps.

SteelEngine Mailer creates a Chat task from an incoming email. It does not run a fixed email-triggered Workflow unless that Chat task explicitly invokes one.

Plan Requirements

On hosted SteelEngine, the Mailer requires an active Team or Scale plan, or an Enterprise plan. On other plans, the SteelEngine Mailer entry still appears in Settings with an upgrade badge. The page then asks you to upgrade to Team or Scale.

Self-hosted deployments with billing disabled can use the Mailer on every workspace. See Self-Hosted Setup for the configuration.

Getting Started

  1. Navigate to Settings → SteelEngine Mailer
  2. Turn on Enable email inbox
  3. Optionally enter a Custom email prefix (1–64 characters, e.g., acme). Leave it blank for an auto-generated address
  4. Select Enable
  5. Copy the address shown under SteelEngine's email and start sending emails

To change the prefix later, select the edit icon next to the address. Enter a New email prefix and select Change address.

Changing your address creates a new inbox. The old address stops working immediately.

What You Can Send

Write your email like you would to a colleague. The subject and body become the task prompt.

Attachments are fully supported. Images, PDFs, and documents (up to 10 MB each) are read by SteelEngine and displayed inline in the conversation — image attachments show as previews, just like when you upload them directly in the chat. SteelEngine skips an attachment larger than 10 MB and still processes the rest of the email.

Good emailWhy it works
"Summarize the attached PDF and list action items"Clear task with an attachment
"What's in this image?" with a photo attachedSteelEngine reads and describes the image
"Draft a reply to this forwarded thread"Uses the email body as context

Allowed Senders

Only authorized senders can create tasks. Emails from anyone else are automatically rejected.

  • Workspace members are allowed by default — no setup needed
  • External senders can be added manually with an optional label (up to 100 characters) for easy identification

Manage your allowed senders list under Allowed senders in Settings → SteelEngine Mailer.

Limits and Rejections

  • Rate limit: each workspace accepts 20 emails per hour. Rejected emails do not count toward the limit.
  • Automated senders: SteelEngine always rejects emails from addresses that start with mailer-daemon@, noreply@, no-reply@, or postmaster@. Bounces and auto-replies never become tasks.
  • Duplicates: the same email message delivered twice creates one task.

SteelEngine records a rejected email as a task with the Rejected status and shows the reason: sender not allowed, automated sender, or rate limit exceeded.

Tracking Tasks

Every email becomes a task you can track in Settings → SteelEngine Mailer:

  • Search the loaded tasks by subject, sender, or the first part of the body
  • Filter by status to find what you need
  • Click any completed or failed task to jump to the full conversation

Task Statuses

StatusMeaning
ReceivedEmail accepted, queued for processing
ProcessingSteelEngine is actively working on it
CompletedDone — the result was sent as an email reply (shown as Complete in the task list)
FailedSomething went wrong during execution
RejectedEmail blocked (sender not allowed, automated sender, or rate limit exceeded)

Conversations

Each email task creates a conversation in your workspace. You can continue the conversation from the SteelEngine chat interface, and any follow-up emails in the same thread are linked to the same conversation.

Self-Hosted Setup

The Mailer is built on AgentMail. Self-hosted operators configure it once for the whole deployment:

VariableDescription
AGENTMAIL_API_KEYAgentMail API key used to create inboxes and webhooks
AGENTMAIL_DOMAINDomain for inbox addresses. When unset, AgentMail's default domain is used
INBOX_ENABLEDSet to true to bypass the hosted plan requirement
NEXT_PUBLIC_INBOX_ENABLEDSet to true to show the SteelEngine Mailer entry in Settings

When a workspace enables its inbox, SteelEngine creates the AgentMail inbox. It also registers a webhook for message.received events at https://<your-steelengine-host>/api/webhooks/agentmail. AgentMail signs each delivery with a per-workspace secret, so this endpoint must be reachable from the internet. See Environment Variables for the rest of the self-hosted configuration.

Common Questions

Not per workspace. Every inbox address uses the domain configured for the deployment (the AGENTMAIL_DOMAIN setting on self-hosted deployments). You can customize the prefix in front of the @ but not the domain itself.
On hosted SteelEngine, the Team, Scale, and Enterprise plans. Self-hosted deployments with billing disabled can enable it on any workspace once AgentMail is configured.
The email is automatically rejected and recorded as a Rejected task. Only workspace members and manually added external senders can create tasks.
Yes, each attachment can be up to 10 MB. Larger attachments are skipped while the rest of the email is processed. Images, PDFs, and common document formats are supported.
Each workspace accepts 20 emails per hour. Emails beyond that are recorded as Rejected tasks with the reason rate limit exceeded. Rejected emails do not count toward the limit.
Yes. Replies in the same email thread are linked to the original conversation, so you can continue the interaction from your email client.
Most emails are processed within a few seconds. Emails with large attachments or complex tasks may take slightly longer.
Yes. All workspace members can send to the shared inbox address. Each email creates its own task and conversation.

On this page