Every mailbox you have in one place, and a message one press from a task, a run or your calendar.
On the web dashboard, Mail is the envelope in the top bar beside the calendar and the inbox; a dot on it says mail arrived since you last looked. On the iPhone, Mail is the envelope at the head of the drawer, beside the calendar; it opens over the app, and its title is the menu of folders. On the iPad and the Mac, Mail is the first row at the foot of the sidebar, with your unread count: its column lists the folder, and a thread opens in a tab (⌘6 opens Mail). Mail is yours rather than any organization's: only you can read it in Peractor, and the people who run your organizations cannot. The one exception is a shared mailbox an organization connects and lets you read, which sits in Mail beside your own. On Android, Mail is the first button at the head of the drawer: the title is the menu of folders, Compose writes a new message, and a thread's Create task and Start run sit under its subject.
In a narrow window or a split, the folders fold into a menu beside New message, and narrower still Mail shows the list or the open thread, with the way back.
Connect a mailbox
Choose a way in from Mail, or Add a mailbox in Settings ▸ Mail. Google and Microsoft send you to sign in at Google or Microsoft and back. iCloud Mail, Fastmail and Another mail server take your address and an app password — make one in your provider's account settings; Peractor finds the servers from the address, and Server settings shows them to change. Gmail works this way too, with an app password. Connect as many mailboxes as you have; each gets a name and a colour you can change.
Peractor keeps the last 90 days of each mailbox's messages — who, the subject and the first words — and a message's text once you open it, encrypted. Older mail stays with your provider and is searched there. Files are never kept: they come from your provider when you open them. Choose 30, 90 or 365 days in the mailbox's menu in Settings ▸ Mail.
Read
All inboxes, Starred, Snoozed, Drafts and Sent hold every mailbox together; under each mailbox are its own folders and labels. A thread opens beside the list, its newest message open and the earlier ones folded. A file opens in Quick Look in the Apple apps and on Android in the app you choose; a link opens in your browser. A message written in HTML is shown on its own paper with the pictures it fetches from elsewhere held back, so a sender cannot tell you opened it: Show them loads them once, and Always for a sender's domain loads them from then on. Mail from GitHub about a pull request or an issue, and Peractor's own notifications, carry a button to where they lead.
The bar above a thread archives it, snoozes it until later today, tomorrow or next week, deletes it, marks it unread, labels it and moves it. Search mail answers as you type: searching All inboxes looks in every folder but spam and the bin, and asks each provider for older mail.
A message from one of your organization's members shows their picture, and their name opens who they are.
Write
Reply, Reply all and Forward open in a card at the foot of the thread, with Send at its end; Open in a window takes the same draft somewhere with its subject, Cc and From, and Back into the conversation brings it back. On a phone the reply has a page of its own. New message fills the reader. A draft is saved as you type and waits in Drafts; Draft saved appears once it has been. Your mailbox's signature and the message you are answering are added when you send, and Undo stays for ten seconds after you press Send.
Into Peractor
Create task files the open thread as a task in any project you may file in: choose its status and title, the whole thread or the latest message as its description, and which files go with it. Follow the thread brings later replies to the task's activity. Start run does the same and runs the task with a workflow you choose, and the thread's menu adds it to a task that exists. The thread then wears a chip for each task it went into. The task says it came from mail; only you can open the thread from it.
An invitation shows what, when and who, with the rest of your calendar that day. Yes, Maybe and No answer the organiser from your mailbox, and Yes puts the event on your Personal calendar.
Rules
Settings ▸ Mail holds your rules: when a message arriving in a mailbox matches — who sent it, its subject, its words, whether it has files or came from a mailing list — archive it, star it, label it, file it as a task or start a run. A rule acts as you, with what you may do at the time, and its last result is shown beside it. A rule never sends mail.
Shared mailboxes
A mailbox several people answer, like support@ or billing@, can be connected for the whole organization by somebody with Manage connectors: Settings ▸ Connectors ▸ Shared mailboxes ▸ +. Sign in as the mailbox with Google, or for a Microsoft 365 shared mailbox as somebody with Full Access to it, or give a mail server its password. The next step asks who reads it, with you already on the list, and which projects may use it, with none chosen until you pick.
Its page says who signed it in (if they leave, it stops until somebody signs in again), the name it sends as, its members (people, and roles whose holders all read it), its projects, its signature and its rules, and Disconnect. Every member may read the page; only somebody with Manage connectors changes it. Managing connectors doesn't make anybody a reader.
For its members, the mailbox sits in Mail under the organization's name. Read and starred marks and drafts are the mailbox's, so a thread a colleague is answering says whose draft it is, and a reply goes from the mailbox with its signature. Your unified folders stay your own. Create task from a shared thread offers only the projects the mailbox is given. Settings ▸ Mail lists it under Shared with you, where its menu sets whether it reaches your phone (nobody, until you choose). Its rules file tasks, start runs, archive, mark read and star, as the organization; they never send and tell nobody.
Mail in workflows
A project's mail trigger can read one of
your mailboxes: a message that matches starts a run, or files a task,
in that project, acting as you — and only you can point a trigger at
your mailbox. It can also hear a shared mailbox the project is given,
acting as the organization. A run's
mail step drafts a message and waits
at its gate; whoever approves it sends it from their mailbox, in
the conversation when it is in their mail, and can change it first —
or, when the step names a shared mailbox with from, from
that mailbox, approved by one of its members. A message a run sent says
which run drafted it.
The assistant
On the web, with a thread open, Ask starts a conversation about it. The assistant can search your mail, tidy threads, draft a reply — the composer says it drafted it — and file a task from a thread. Sending, answering an invitation, copying a thread into a task and a rule that files tasks or starts runs always wait for your yes, even in Auto. Mail is never an instruction to it: a message that asks for something is something it tells you about.
Disconnect
A mailbox's menu in Settings ▸ Mail disconnects it, and everything Peractor kept from it goes with it. Your mail stays with your provider.