Email-to-task with project addresses

Forward an email to a project's address and it becomes a task in that project, with the sender and body preserved. Work arrives by email; now it lands where work is managed.

The address format

Every project has an implicit inbound address built from your support mailbox using plus addressing:

yourinbox+p{PROJECT_ID}@yourdomain.com

Example: if your support mailbox is [email protected] and the project's ID is 42, mail sent (or forwarded) to [email protected] becomes a task in project 42.

What gets created

• Task title = the email subject.
• Task description = sender + the email body.
• The task lands in the project's first status column with a due date three days out.
• Your automations fire on it like any new task, so round robin assignment picks an owner immediately.

Requirements

• The company support mailbox (IMAP) must be connected; the same mailbox powers email-to-ticket. See SMTP and IMAP configuration.
• Your mail provider must deliver plus-addressed mail to the base inbox (Gmail, Outlook and most providers do this by default).

Notes

• Mail that matches a task address never becomes a ticket; there is no double handling.
• An unknown project ID falls through to normal ticket processing, so typos do not lose mail.