Email to a Bot
Give a responsibility an email address of its own. Mail sent or forwarded there starts the Bot on it, with the message and its attachments, and mail that fails the sender checks is held for you instead.
3 min read
Getting an addressCopy link to this section
Open Responsibilities, find the responsibility and press Add trigger in its Triggers section. Choose Email as the Trigger. Once it is saved, the trigger shows its own address with Copy address: send or forward mail to it to start a run.
Incoming mail is set up for the whole workspace by whoever runs it. Until it is, an email trigger shows a warning in place of its address and cannot receive mail yet.
To accept mail only from certain people, fill in Allowed senders (blank: anyone) with addresses or whole domains, separated by commas. Like every trigger, an email trigger belongs to the person whose responsibility it starts.
What the Bot receivesCopy link to this section
Each message becomes one event with the sender, the recipients, the subject, the date, whether the sender was authenticated, and the text of the mail, up to its first 16,000 characters.
- Up to eight attachments are saved to the files of the conversation the responsibility works in, as if its owner had uploaded them, and go through the same checks as an upload: only kinds a Bot can read, within the administrator's size limits, damaged documents refused and a photo's location removed. The Bot is told what was saved and what was refused, and why.
- The trigger's filter works on these fields like any other: for example Only when field subject equals a fixed subject line, or a condition on the sender.
- A Prompt template shapes what the Bot reads, such as
New request from {{from}}: {{subject}}.
The work appears in the responsibility's conversation, where you follow it as usual. The Bot does not write back to the sender by itself; if you want it to, say so in the trigger's instruction, and sending mail is then an action like any other, subject to your boundaries and approvals.
Held mailCopy link to this section
The receiving mail service checks each message's SPF, DKIM and DMARC, and the trigger reads its verdicts; nothing is judged from headers the sender wrote. A message is held under Held mail instead of reaching the Bot when:
- Failed sender authentication: DMARC failed, or neither SPF nor DKIM passed and one of them failed.
- Sender not on the list: the trigger has allowed senders and this sender is not one of them.
- Listed sender, but not authenticated: the address is on the list, but neither DKIM nor DMARC passed, so anyone could have typed it.
Mail that simply carries no verdicts, as many small senders' does, is not called forged, and is delivered when the trigger accepts every sender.
Held mail is kept for 30 days and shown with its sender, subject and verdicts. Release to the Bot runs the trigger exactly as if the mail had passed, so release only mail you trust; Delete removes it. Holding, releasing and deleting are recorded on the audit trail with the sender's domain and the verdicts, never the address or the message.
Warning
Anything in a mail is untrusted text from outside. The Bot treats it as material to work on, not as instructions that override yours, and actions it leads to still go through your approvals.
Last updated