Google Tasks Email-to-Task Capture
When a flagged email arrives (or is forwarded to an intake address), the flow creates a Google Task with the subject as title, due date from the email or rules, a link back to the message, and posts a confirmation. Turns actionable emails into Google Tasks automatically.
Provided as-is, without warranty of any kind. Review and test each pattern in a non-production environment before deploying it to live automations. See our Terms.
Overview
This flow turns flagged Outlook emails into Google Tasks. When an email is flagged in the configured mailbox folder, the flow creates a Google Task — the email subject becomes the task title, the sender / received time / preview / a deep link to the message go into the task notes, and the due date is set to today plus a configurable offset. It then posts a confirmation card to a Microsoft Teams channel.
Why it matters: Emails that imply action get lost in the inbox. Auto-capturing flagged emails as Google Tasks with a link back to the source message ensures follow-through, and the Teams confirmation gives the team visibility.
Status: Built (ships Off). Going live requires only authorizing the three connections and setting the environment variable values.
Use Case
A user lives in Google Tasks but receives actionable work over email. Instead of re-typing emails into Google Tasks, they simply flag the email in Outlook. Within a few minutes the flow creates a matching Google Task (with a one-click link back to the original message) and announces it in a Teams channel for team awareness.
Flow Architecture
When An Email Is Flagged
Office 365 Outlook — OnFlaggedEmailV4Polling trigger (every 3 min) that fires for each newly flagged email in the configured folder.
Initialize Google Task List Id
Initialize VariableLoads the target Google Tasks list ID from env var.
Initialize Teams Group Id
Initialize VariableLoads the Teams team (group) ID from env var.
Initialize Teams Channel Id
Initialize VariableLoads the Teams channel ID from env var.
Initialize Due Offset Days
Initialize VariableConfigurable days-from-receipt used for the task due date (default 2).
Compute Due Date
ComposeaddDays(utcNow(), varDueOffsetDays) -> RFC3339 due date.
Build Task Notes
ComposeAssembles sender, received time, body preview, and a deep link to the email.
Create Google Task
Google Tasks — CraeteTaskCreates the task: subject as title, built notes, computed due date.
Post Confirmation To Teams
Microsoft Teams — PostMessageToConversationPosts a confirmation card with the task, due date, and email link.
Environment Variables
| Schema name | Type | Default | Description |
|---|---|---|---|
| flowlibs_GoogleTaskListId | String | @default | Google Tasks list the task is created in (@default = user's default list). |
| flowlibs_IntakeMailFolder | String | Inbox | Mailbox folder monitored for flagged emails. |
| flowlibs_TeamsGroupId | String | <your-team-id> | Teams team (group) for the confirmation message. |
| flowlibs_TeamsChannelId | String | <your-channel-id> | Teams channel for the confirmation message. |
Connectors & Connections
| Connector | API name | Actions used |
|---|---|---|
| Office 365 Outlook | shared_office365 | OnFlaggedEmailV4 |
| Google Tasks | shared_googletasks | CraeteTask |
| Microsoft Teams | shared_teams | PostMessageToConversation |
Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.
Customization Guide
Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.
- Change the intake folder
- Set flowlibs_IntakeMailFolder to any Outlook folder (e.g. a rule-fed Tasks subfolder) instead of Inbox.
- Route to a specific Google list
- Set flowlibs_GoogleTaskListId to a real list ID to file tasks somewhere other than the default list.
- Adjust the deadline
- Change varDueOffsetDays (Initialize Due Offset Days) to set how far out tasks are due.
- Keyword-based due dates
- Extend Compute Due Date to parse phrases like 'by Friday' from the subject/body and override the offset.
- Priority prefix
- Prepend a marker (e.g. [HIGH]) to the task title based on email importance.
- Quieter confirmations
- Swap the Teams post for an Outlook SendEmailV2, or remove it entirely.
Key Expressions
The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.
EXPR.01Due date
Sets the task due date from a configurable offset.
EXPR.02Task title
Uses the email subject as the task title.
EXPR.03Email deep link (in notes)
One-click link back to the original message.
EXPR.04Notes body
Assembles the task notes from email metadata.
Customize & download
Generate a ready-to-import copy of this solution with your environment-variable values baked in — available on Base, Pro, or Team.
Upgrade to customize
Comments
Sign in to join the conversation.
Sign inNo comments yet. Be the first to share your experience with this flow.