Tasks from email
What is in the task Plavn makes from an email, how to create one yourself, and what happens when you finish it.
When an email asks you to do something, Plavn adds a task for it next to the reply. This page covers the task, how to make one yourself and how finishing it can close the loop with the sender. For the reply, see Review and send.
When Plavn makes a task
Section titled “When Plavn makes a task”Plavn makes a task only when it is work mail and the email asks you to do something beyond answering it: fix something, change something, prepare, write, review or look into something. It does not make one for thanks, scheduling, small talk, or a question your reply answers. It also does not make one for personal mail, which only gets a reply.
What is in the task
Section titled “What is in the task”The task is a normal task in your planner. Plavn fills in:
- Title and description that say what needs doing, not what the email says. You can steer how they are written under Tasks made from email in the AI instructions.
- Priority.
- Due date, taken from the deadline in the email (“by Wednesday noon” becomes that Wednesday at 12:00). A date without a time is due at the end of that day. The date of a meeting is not a deadline unless the work is due then. With no deadline, there is no due date.
- Project, when the email clearly belongs to one of your active projects. Otherwise the task goes to your Inbox.
- Position: at the top of the project’s first list so you see it. If the project has no list yet, Plavn creates a list called From email.
- Document draft, if the email asks you to write something (talking points, a report, a memo, a letter, a proposal): a first draft in the task’s notes, with the sender and subject at the top. Turn this off with Draft documents.
The “From email” section
Section titled “The “From email” section”Open the task. Below its details, From email shows:
- The email. A link with the subject, sender and date; it opens the conversation.
- Analysis. What Plavn understood from the email, and for a reported problem what it found. Collapse it with the arrow.
- Suspect commits, if you linked GitHub and Plavn found code that may be behind a reported problem. Each shows the commit, repository, author and date, the commit message, why it is suspected and the files it changed. A badge says how sure Plavn is: High, Medium or Low confidence. Treat it as a lead, not a verdict.
- GitHub issue. Create GitHub issue opens a form with the title and text filled in from the report, the analysis and the suspects, for you to edit and send to one of your linked repositories. The sender’s name and address go in only if you tick Include the sender’s name and address, because issues are often public. Once created, the task shows the issue and whether it is open or closed.
- Reply, the prepared draft, editable and sendable here. After sending it shows Reply sent.
Make a task yourself
Section titled “Make a task yourself”Plavn did not make a task, or you want one for an email it did not mark? Open the email and choose Make a task in the toolbar.
- It creates a task in your Inbox, titled with the email’s subject (without “Re:” or “Fwd:”), and opens it. Add a due date there.
- The task links back to the email in From email.
- It is just a task. Make a task does not write a reply or an analysis. To get those, use Prepare a reply (or t) as described in Review and send.
- The button is hidden once Plavn has prepared a task for the email.
Finishing the task
Section titled “Finishing the task”When you complete a task that came from an email, Plavn checks for loose ends and asks about each in turn:
-
The GitHub issue is still open. Plavn asks Also close the GitHub issue? with Close issue and Keep open. Tick Do this every time to stop being asked. You can change that later under Settings → Developer, in When I complete a task with an open issue: Ask me, Close the issue or Leave it open. It is saved on this device only.
-
A prepared reply was never sent. Plavn asks Send the reply you prepared? and offers:
- Send now: sends it as it is (offline, it goes out when you are back online),
- Edit first: opens it,
- Keep for later: leaves the draft,
- Delete: removes it.
The prompt adds that unless a reply goes out, Plavn will also prepare one telling the sender it is done.
Telling the sender it is done
Section titled “Telling the sender it is done”Soon after you complete a task from an email, or after its GitHub issue is closed (a merged pull request that says “Fixes #123” does this), Plavn writes a short reply to the original sender saying it is done.
- It is two to four sentences, in the language of their email and in your voice, in their words about what they reported, with no commit hashes, links or ticket numbers.
- It appears on the email as Done · A reply telling them is ready, with the chip Done · tell them in the list, and the task says A reply telling the sender it is done is ready on the email. You also get a notification, “Done: tell Alex?”, under Replies ready.
- Review and send it like any prepared reply. Once sent, the task says The sender was told it is done.
Plavn does not prepare it if you already replied to that email after the task last changed, if the email was deleted or is in Spam, or if Prepare replies and tasks is off. This also applies to a task you made yourself with Make a task.
Settings and limits: turn parts off, tune your tone and manage the monthly AI allowance.