Actions12
Overview
This node integrates with the EmailConnect API to manage email-related resources such as domains, aliases, and webhooks. Specifically, for the Alias - Create operation, it allows users to create a new email alias within a specified domain. An alias is an email address that forwards incoming emails to another destination email address.
Common scenarios where this node is beneficial include:
- Automating the creation of forwarding email addresses for support, sales, or other departments.
- Managing email aliases programmatically as part of onboarding or user management workflows.
- Dynamically creating aliases for temporary campaigns or projects without manual intervention.
For example, you can create an alias like support@yourdomain.com that forwards all emails to user@example.com.
Properties
| Name | Meaning |
|---|---|
| Domain Name or ID | The domain under which the alias will be created. Choose from a list or specify an ID via expression. |
| Local Part | The local part of the email address (the portion before the "@" symbol). For example, "support" in "support@domain.com". |
| Destination Email | The target email address where emails sent to the alias will be forwarded. |
Output
The output is a JSON object representing the newly created alias resource returned by the EmailConnect API. It typically includes details such as the alias ID, full email address, destination email, and related metadata.
Example output structure (simplified):
{
"id": "alias-id",
"email": "support@domain.com",
"localPart": "support",
"destinationEmail": "user@example.com",
...
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the EmailConnect API.
- Requires an API authentication token configured in n8n credentials for EmailConnect.
- The node uses internal methods to load available domains dynamically for selection.
Troubleshooting
Common issues:
- Invalid domain ID or domain not found: Ensure the domain exists and the correct ID is used.
- Invalid email format for local part or destination email: Validate email formats before execution.
- API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
Error messages:
"Unknown error occurred": Generic catch-all; check API connectivity and credentials.- API response errors usually contain descriptive messages indicating missing parameters or invalid values.
To resolve errors, verify input parameters, ensure network connectivity, and confirm API credentials are valid.
Links and References
- EmailConnect API Documentation (replace with actual URL if available)
- n8n Expressions Documentation – for using expressions in property fields