Skip to content
Hypamoon

For teams that run on awork

awork email to task: replies land as comments

A lot of project talk with clients and partners runs by email, and not everyone will work in awork. Getting that email onto the task, so the whole team sees it, is copy and paste.

How it goes today

  1. Copy each sent and received email into the task as a comment.
  2. Forward emails to the colleagues who need to know.
  3. Merge tasks that were created from the same email thread.

How it can go

Emails about a task end up on that task.

Each project gets an address you can copy in or forward to. When the subject carries the task number, the email lands as a comment on that task with sender and date, and its files are attached to the task. Without a number you get a suggestion for the task and confirm it. When you start a comment in awork with a word you choose, it goes out as an email reply from your own address, and the answer comes back on the task.

Say this in ChatGPT, Claude or Copilot

Your chat gets connected to Hypamoon first, with this request filled in. You paste your awork key in the portal, never in the chat.

Your request

With Hypamoon, give each of our awork projects an email address we can copy in or forward to. When the subject has the task number, add the email as a comment on that task with sender and date, and attach the files to the task. When there is no number, suggest the task and wait for my yes. When we start a comment with a word I choose, email it to the outside contact from our address and put their answer back on the task.

An admin creates the awork key under Settings, Integrations: add an API client, then Manage API Keys. It stays yours.