PERSONAL PRODUCTIVITY

Turn Outlook email promises into assigned Asana tasks with due dates

When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew email sent from OutlookOutlook
  • ActionExtract deliverables and dates with LLMOpenAI
  • LogicDeliverable present and date usable?
  • ActionCreate assigned Asana tasksAsanaAsana
  • OutputReturn created-task confirmation

What it does

This workflow watches your Outlook sent mail, detects explicit deliverables you promised, and converts each into an Asana task with a clear title, a due date parsed from the email, and a description that quotes the original promise. Promises become tasks where you already work, not a separate list.

When to use it

Ideal for operators who live in Asana and want email commitments to flow straight into their existing project or personal task board, with deadlines, rather than living in a tracker they have to check.

How it works

  1. 1Sending an email from Outlook triggers the run.
  2. 2The body is analyzed by an LLM that returns each deliverable plus an inferred or explicit due date.
  3. 3A logic step confirms at least one deliverable exists and that a usable due date was extracted; promises without dates default to a 3-day deadline.
  4. 4For each deliverable, an Asana task is created and assigned to you, with the due date and a quote of the original sentence in the notes.
  5. 5A confirmation is returned listing the tasks created.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AsanaTasks, projects, milestones — everywhere.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.