Email-to-task

Each tenant registers one or more aliases (for example, atlas-abc123@in.your-domain.com). When the MX gateway posts an inbound email signed with ATLAS_INBOUND_EMAIL_SECRET, Atlas mints a task in the alias's default project.

• HMAC-signed webhook (not raw SMTP), which keeps the API surface small
• Per-alias default project and default assignee
• Every inbound email is persisted in InboundEmail regardless of success

• ATLAS_INBOUND_EMAIL_SECRET must be set on the api service. See docs/operations/operations-prerequisites.md.
• Attachments are not yet ingested; the body goes into the task description.

1. 1Go to Settings > Email-to-task > New alias (this picks the default project).
2. 2Configure your MX gateway to POST to /inbound-email/hook.
3. 3Forward emails to the alias, and tasks appear.

Why does nothing arrive when I email the alias?

Check that the inbound email secret is set on the api service. Without it the gateway cannot sign its post and Atlas will not accept the message. The operations prerequisites document names the variable.

Where do the attachments on an inbound email go?

Nowhere yet. Attachments are not ingested at present, and the body of the message becomes the task description. Send anything that must be attached through the task itself once it exists.

Can I tell which project and assignee an emailed task will land on?

Yes. Each alias carries a default project and a default assignee, so the destination is a property of the address the sender used. Register more than one alias when different inboxes should land in different projects.