Email-to-task

Email-to-task gives your workspace one or more inbound addresses. Each message that reaches an address becomes a task in the default project you set for that address, with the subject as the title and the text of the message as the description. Atlas does not receive mail by itself: a mail gateway connected by whoever operates your Atlas must deliver each message with a signature, so ask your administrator whether it is connected.

• Each address has its own default project and default assignee, and can be turned off or deleted at any time
• The subject becomes the task title and the text of the message becomes the task description
• Every message delivered with a valid signature to a known address is listed under Recent inbound messages, with the task it created or the reason it did not

• Atlas accepts a message only when it is signed with the inbound email secret and sent to an address that exists and is enabled. The secret is set by whoever operates your Atlas, not in the workspace.
• Only the subject and the text of the message are used. Attachments are not imported. The same message delivered twice, with the same message identifier, creates only one task.

1. 1Open Settings, then Inbound email, and choose New address. Atlas generates the alias.
2. 2Enter the ID of the default project and, if you wish, the ID of the default assignee. Without a default project, a message creates no task and is listed with an error.
3. 3Have the mail gateway deliver each message, signed, to the inbound email hook of Atlas, then send email to the address. Each message appears under Recent inbound messages.

Why does nothing arrive when I email the alias?

Atlas accepts a message only from the mail gateway, signed with the inbound email secret. If the secret is missing or different, or the gateway is not connected, nothing arrives. Ask your administrator to check both, and check that the address is enabled. The operations prerequisites document names the variable.

Where do the attachments on an inbound email go?

Nowhere. Attachments are not imported. The subject becomes the title and the text of the message becomes the description. Add any file to the task itself once it exists.

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

Yes. Each address carries a default project and a default assignee, so the destination is a property of the address the sender used. Register more than one address when different inboxes should land in different projects. An address with no default project makes no task: the message is listed with an error instead.