NotionAI & Automation

Forward Emails to Notion: Automate Task Creation

Daniel Canosa·

Picture this: you get an email that needs action, but not right now.

You probably snooze it or manually create a task somewhere else.

Maybe you copy the subject line so you can find the email later.

But honestly, this whole process disrupts your day and creates friction between your inbox and your task manager.

I hate manual processes like this.

That's why I built this automation that forwards any email to Notion and automatically creates a task with all the context I need.

Let me show you exactly how it works.

The Email-to-Task Automation in Action

When I receive an email that needs follow-up, I simply press F to forward it to a special Make.com email address.

I can add a note like "to-do today" or just "urgent" in the forward.

The system reads the entire email thread, understands the context, and creates a properly formatted task in my Notion database.

Email forwarding to Notion: incoming payment request email automatically captured in Notion database showing sender, subject, and full email content
Email forwarding to Notion: incoming payment request email automatically captured in Notion database showing sender, subject, and full email content

The automation extracts the key information I need: what task needs to be done, who it's from, when it's due, and includes the full email content for context.

No manual copying and pasting.

No switching between apps.

No forgetting important details.

The task appears in my Notion workspace with a due date (either extracted from the email or set to two business days from now), the sender's name, and the complete email thread.

This means I can stay in my task manager instead of jumping back to email to remember what someone wanted.

Building the Make.com Workflow

The automation runs on three main components: a Mail Hook, ChatGPT processing, and Notion integration.

Make.com automation workflow showing the 'Tasks from emails' scenario with Webhooks (Mail Hook), Parse email, Create Task, and Notion modules connected in sequence
Make.com automation workflow showing the 'Tasks from emails' scenario with Webhooks (Mail Hook), Parse email, Create Task, and Notion modules connected in sequence

The Mail Hook acts like a webhook but for emails.

It gives you a unique email address where you can forward messages.

When you send an email to this address, the hook captures everything: the subject, body, HTML content, sender information, recipient details, and the entire email thread.

The ChatGPT module does the heavy lifting.

This is where the magic happens because it reads through potentially long email threads and extracts exactly what I need.

Make OpenAI ChatGPT module configuration showing Connection, Method (Create a Chat Completion), Model selection (gpt-4.1), and Messages setup with Role and Text Content fields for email task processing
Make OpenAI ChatGPT module configuration showing Connection, Method (Create a Chat Completion), Model selection (gpt-4.1), and Messages setup with Role and Text Content fields for email task processing

I use GPT-4.1 because it's cost-effective for this type of task processing.

The key is in the system prompt that teaches ChatGPT exactly how to analyze emails and what information to extract.

The system prompt includes specific instructions:

Extract the main task Daniel needs to complete based on the conversation.

Find the due date if mentioned explicitly (like "by Friday" or "before our call tomorrow").

If no due date exists, set it to two working days from now.

Return only the body of the last email received (not from me).

Output everything in a specific JSON format.

System prompt and JSON output structure requirements for OpenAI API integration, showing task schema with fields for task, due_date, last_email_body, subject, and who
System prompt and JSON output structure requirements for OpenAI API integration, showing task schema with fields for task, due_date, last_email_body, subject, and who

The JSON structure ensures I can map each piece of information to the right field in Notion: task name, due date, email body, subject line, and who sent it.

Training ChatGPT with examples makes it more reliable.

I set up a conversation flow within the module that shows ChatGPT exactly how to respond.

ChatGPT message configuration showing user role selection and text content setup in the OpenAI module
ChatGPT message configuration showing user role selection and text content setup in the OpenAI module

This conversation includes a sample email and the exact JSON response I want.

By showing ChatGPT the expected input and output format, it follows the pattern consistently.

Bear in mind, AI models sometimes ignore instructions, so providing concrete examples helps maintain consistency.

Mapping the Results to Notion

Once ChatGPT processes the email and returns structured data, the final step connects everything to Notion.

Notion database mapping configuration showing parsed JSON variables (S2F, YouTube, Backend, Working On properties) being mapped to Notion database fields for the task creation workflow
Notion database mapping configuration showing parsed JSON variables (S2F, YouTube, Backend, Working On properties) being mapped to Notion database fields for the task creation workflow

The parsed JSON gives me clean variables to work with.

Instead of raw JSON text, I get individual fields: task, due_date, last_email_body, subject, and who.

This parsing step is crucial because it allows me to map specific information to specific fields in my Notion database.

The Notion module creates the task with proper field mapping.

The task description comes from ChatGPT's analysis of what needs to be done.

The status defaults to a standard value in my workflow.

The assignee is automatically set to me.

The due date uses ChatGPT's extracted or calculated date.

Notion database item creation interface showing field mappings with Content Objects, Type selectors (Paragraph), Text fields, and content formatting options including Annotations (Bold, Italic, Strikethrough, Underline)
Notion database item creation interface showing field mappings with Content Objects, Type selectors (Paragraph), Text fields, and content formatting options including Annotations (Bold, Italic, Strikethrough, Underline)

The task body includes all the email context I might need later.

I append the original email content, subject line, and sender information to the task.

This formatting uses Notion's content blocks: headings for organization and paragraphs for the actual content.

Having this context means I can search for the original subject line if I need to reply to the email later.

The entire setup probably takes 10 minutes to build once you have the system prompt (which I've shared in the video).

This automation eliminates the friction between email and task management.

Every email that needs action becomes a properly formatted task with context.

No more losing track of important follow-ups.

No more manual copying between systems.

Your task manager becomes the single source of truth for what needs to get done, not your inbox.

Ready to see where your business stands with AI and automation? Take our AI Readiness Scorecard to find out.

Get more like this in your inbox

AI implementation insights for service business founders. No fluff.