Connecting task lists
“I still have to deal with this” is the worst state for an email: too important to archive, too bulky for the inbox. The task integrations solve it by turning the mail into an entry in the tool where your tasks live anyway:
| Service | The email becomes |
|---|---|
| Trello | a card, at the top of the chosen list on a board |
| Asana | a task in the chosen project |
| Notion | a page in the chosen database |
Connecting
Section titled “Connecting”Each service has its page in the settings in the Integrations section. The connection follows the same pattern everywhere:
- Turn the service on, for instance with Enable Trello.
- Click Connect with Trello (or Asana, Notion) and allow access in the browser.
- Set a default target: board and list, workspace and project, or the Notion database.
For Notion, only databases appear that you shared with the integration in Notion and that have a “Title” property. Further options per service: Include email body, Attach email as PDF (Trello, Asana) and, for Trello, the Card description format.
By hand: the mail action
Section titled “By hand: the mail action”In the More actions menu of every email you find the action of the connected service, such as Send to Trello. A dialog shows the default target, the subject as title and the content as description. You can change both before sending, and the target too; for Asana, section and due date come on top.
After that, the email can go to the archive with a clear conscience: the task now exists in the right place.
Automatically: by rule
Section titled “Automatically: by rule”The same actions are available in the automation, with their own target per rule or the default from the integration settings. Recurring mail thus becomes recurring tasks without you touching it. The title is always the subject of the email.
- Every mail to
support@becomes an Asana task in the support project. - The supplier’s orders land as Trello cards on the purchasing board.
- Mail with “invoice” in the subject becomes a page in the accounting team’s Notion database.
Combined with Add tag and Move to mailbox, this builds an intake line: the mail gets filed, the work moves into the task system.
Good to know
Section titled “Good to know”- No return channel: The integration creates entries, it does not sync. Whether the Trello card is done, YouniqMail does not know, and does not need to.
- Only the one email is transferred, and only when you (or your rule) trigger it. No standing access to the mailbox.
- Disconnecting: Disconnect removes the sign-in from YouniqMail. YouniqMail also revokes access at the service. If that fails, for example without an internet connection, a notice asks you to remove YouniqMail in the service’s account settings.
- Pro feature: All task integrations belong to the Pro feature set.