Skip to main content

Parse email body message

Workflow preview

Workflow preview
100%
Parse email body message preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Who we are We are Aprende n8n , the first n8n Spanish course for all n8n lovers. If you want to learn more, you can find out more at Aprende n8n. Task goal This task allow...

Best for

  • Ticket Management automation workflows
  • beginner n8n builders looking for reusable templates

Tools used

n8n-nodes-base.manualtrigger, n8n-nodes-base.functionitem, n8n-nodes-base.set

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Miquel Colomer.

Original n8n.io source

1.1 Workflow description

Title
Parse email body message
Workflow name
Parse email body message

Who we are

We are Aprende n8n, the first n8n Spanish course for all n8n lovers. If you want to learn more, you can find out more at Aprende n8n.

Task goal

This task allows extracting data from any email body with a NoCode snippet.

An small explanation

You receive an email when a user submits a form from your website.

All those emails usually have the same structure as the next one:

Name: Miquel
Email: [email protected]
Subject: Welcome aboard
Message: Hi Miquel!

Thank you for your signup!

This task allows to parse any email body and assign all values to the defined labels, getting an output like this:

{
"Name": "Miquel",
"Email": "[email protected]",
"Subject": "Welcome aboard",
"Message" "Hi Miquel! Thank you for your signup!"
}

After importing it

When you import the import, you get the next task in your n8n:

We recommend importing this workflow into your current task and adapting it. You define a couple of variables in the "Set values" SET:

  • body: the email body you want to parse. You can add this as an expression from previous variables.
  • labels: the keywords you want to detect and parse. Labels are case insensitive.

We define the next values:

Body

Name: Miquel
Email: [email protected]
Subject: Welcome aboard
Message: Hi Miquel!

Thank you for your signup!

Labels

Name,Email,Subject,Message

A screenshot of the Set output is the next one

If we check the "Function item" Node, we get the next content after executing the task:

Capabilities

The task has the next features:

  • You can detect as many labels as you want.
  • Label detection is case insensitive.
  • You can use the snippet as an independent workflow to call it generically, adding the Function item to the workflow and passing body and labels as paremeters.

Limitations

This task has limitations:

  • The parser only accepts the multiline values at the end of the email.

Help and comments

If you have any doubt about this snippet, please, contact us at [email protected].

You can contact us at Aprende n8n or in the Spanish n8n community

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - On clicking 'execute'

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 2 - Email Parser Snippet

Type / Role
n8n-nodes-base.functionItem - functionItem
Config choices
Version 1

Block 3 - Set values

Type / Role
n8n-nodes-base.set - set
Config choices
Version 1

3. Summary Table

Workflow Parse email body message
Complexity beginner
Nodes 3
Categories Ticket Management
Author Miquel Colomer
Published 16 Feb 2022

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/1453/1453.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Parse email body message do?

Who we are We are Aprende n8n , the first n8n Spanish course for all n8n lovers. If you want to learn more, you can find out more at Aprende n8n. Task goal This task allow...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Ticket Management use case.