Actions22
- Tool Actions
- Other Tool Actions
- Date Operation Actions
- Text & Formatting Actions
Tool → Fix Email Address Domain
AI-generatedOverview
The node provides a variety of utility tools for data processing and text manipulation. Specifically, the "Fix Email Address Domain" operation is designed to correct common typos in the domain part of an email address. This is useful when users input email addresses with misspelled domains such as "gmial.com" instead of "gmail.com". The node automatically detects these common mistakes and replaces them with the correct domain.
Practical examples:
- Correcting user-submitted email addresses before storing or sending emails.
- Cleaning up mailing lists by fixing domain typos to improve deliverability.
- Validating and normalizing email inputs in workflows that require accurate contact information.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address string to be fixed. The node checks the domain part and corrects it if it matches known common typos. |
Output
The output JSON object contains the following fields:
originalEmail: The original email address input.correctedEmail: The email address after domain correction.domainCorrected: Boolean indicating whether the domain was corrected.originalDomain: The domain part extracted from the original email.correctedDomain: The corrected domain (same as original if no correction was needed).
This output allows downstream nodes to use either the original or corrected email address depending on the workflow logic.
Dependencies
- No external API or service dependencies are required.
- The node operates fully locally using a predefined mapping of common email domain typos to their correct forms.
- No special environment variables or credentials are needed.
Troubleshooting
Invalid email address format error:
If the input email does not contain an "@" symbol or is empty, the node throws an error stating "Invalid email address format". Ensure the input is a valid email string.No correction applied:
If the domain is not recognized as a common typo, the node returns the original email unchanged. This is expected behavior.Handling unknown domains:
The node only fixes domains included in its internal typo map. For uncommon or new domains, no correction will occur.