Data Converter
Actions49
- Base64 Actions
- Binary Actions
- Encoding Actions
- Format Actions
- HTML Actions
- String Actions
Overview
This node provides a versatile "Data Converter" tool that supports many data format transformations, including Base64 encoding/decoding, binary conversions, JSON/XML/YAML/CSV formatting, HTML generation, text encoding/decoding, and string manipulations. Specifically, the Parse Email Address operation under the String resource extracts structured information from email address strings, such as the name, email, and domain parts.
Use cases for the Parse Email Address operation include:
- Extracting user names and domains from raw email strings in workflows.
- Validating or normalizing email inputs by breaking them into components.
- Preparing email data for further processing or routing based on domain or user.
Example: Given an input like "John Doe <john.doe@example.com>", the node will parse and output the name "John Doe", the email "john.doe@example.com", and the domain "example.com".
Properties
| Name | Meaning |
|---|---|
| Input Data | The email string to parse. Can be a plain email, or formatted with a display name. |
| Binary Property Name | (Optional) Name for the output binary property if binary output is enabled (not used here). |
Note: For this specific operation, only the Input Data property is relevant and required.
Output
The node outputs a JSON object with the parsed email address details. The structure typically includes:
name: The display name part of the email if present (e.g., "John Doe").email: The full email address extracted (e.g., "john.doe@example.com").domain: The domain part of the email address (e.g., "example.com").
Example output JSON:
{
"result": {
"name": "John Doe",
"email": "john.doe@example.com",
"domain": "example.com"
}
}
No binary output is produced by this operation.
Dependencies
- No external services or API keys are required.
- The node relies on internal utility functions for parsing email addresses.
- No special environment variables or credentials are needed.
Troubleshooting
- Invalid email format: If the input string does not contain a valid email address, the output may be incomplete or empty fields. Ensure the input follows standard email formats.
- Empty input: Providing an empty string will result in no meaningful output.
- Error handling: If an error occurs during parsing, the node will throw an error unless configured to continue on failure, in which case it outputs an error message in the JSON.
Links and References
- RFC 5322 - Internet Message Format
- Email Address Parsing in JavaScript (for regex reference)
- n8n Documentation: Creating Custom Nodes