EML icon

EML

Node to work with EML files
Join our community

Actions2

Overview

The EML node is designed to parse and extract information from EML files, which are email messages formatted according to the RFC822 standard. This node is useful in workflows where you need to analyze or process raw email content, such as extracting headers, reading message bodies, or handling attachments.

A common scenario for this node includes:

  • Parsing incoming emails stored as raw EML content to extract metadata like sender, recipient, subject, and specific headers.
  • Extracting attachments from emails for further processing or storage.
  • Filtering or routing emails based on header values or content.

For example, you might use this node to parse an EML file received from an email service, extract all headers and attachments, and then save attachments to cloud storage or trigger alerts based on certain header values.

Properties

Name Meaning
EML Content (RFC822) The raw EML content string representing the full email message to be parsed.
Output All Headers Boolean flag indicating whether to include all email headers in the output.
Headers to Output Comma-separated list of specific headers to include if "Output All Headers" is set to false.
Include Attachments Boolean flag indicating whether to include email attachments in the output as binary data.

Output

The node outputs a JSON object containing the parsed components of the EML content. This typically includes:

  • Parsed email headers (either all headers or only those specified).
  • Email body content.
  • If enabled, attachments included as binary data, allowing subsequent nodes to handle or store these files.

The exact structure depends on the parsing implementation but generally provides easy access to key email parts for downstream processing.

Dependencies

  • The node relies on internal utilities and resource definitions bundled within the node package.
  • No external API keys or services are required.
  • It expects valid EML content as input.

Troubleshooting

  • Invalid EML content: If the provided EML content is malformed or incomplete, the node may fail to parse it correctly. Ensure the input string is a complete and valid RFC822 email message.
  • Headers not appearing: If "Output All Headers" is false and the "Headers to Output" field is empty or misspelled, no headers will be included. Provide a correct comma-separated list of header names.
  • Attachments missing: If attachments are expected but not present in the output, verify that "Include Attachments" is enabled and that the EML content actually contains attachments.
  • Error during execution: The node wraps errors in a generic operation error. Check the input data and property settings for correctness.

Links and References

Discussion