Actions12
Overview
This node integrates with the EmailConnect API to manage email automation resources such as domains, aliases, and webhooks. Specifically, for the Alias - Get operation, it retrieves detailed information about a specific email alias identified by its name or ID within a selected domain.
Common scenarios where this node is beneficial include:
- Fetching configuration details of an existing email alias to verify forwarding settings.
- Retrieving alias metadata for auditing or synchronization purposes.
- Integrating alias data into automated workflows that depend on alias properties.
For example, you might use this node to get the destination email address associated with a particular alias before sending notifications or updating records in another system.
Properties
| Name | Meaning |
|---|---|
| Alias Name or ID | Select an existing alias from the list (populated based on the chosen domain) or specify an alias ID using an expression. This identifies which alias to retrieve. |
| Domain Name or ID | Select the domain under which the alias exists. The list is dynamically loaded from available domains. |
Output
The output is a JSON object representing the alias details as returned by the EmailConnect API. Typical fields may include:
id: The unique identifier of the alias.email: The full alias email address.localPart: The local part of the alias email (before the @).destinationEmail: The email address to which messages are forwarded.- Other metadata related to the alias configuration.
The node does not output binary data for this operation.
Example output JSON structure:
{
"id": "alias-id-123",
"email": "support@example.com",
"localPart": "support",
"destinationEmail": "user@example.com"
}
Dependencies
- Requires an API key credential for authenticating with the EmailConnect API.
- The node depends on the EmailConnect service being accessible via its REST API endpoints.
- Dynamic loading of domains and aliases requires network access to fetch current lists.
Troubleshooting
Common issues:
- Selecting an alias without first selecting a domain will result in no aliases being listed.
- Using an invalid or expired API key will cause authentication errors.
- Network connectivity problems can prevent fetching domains or aliases.
Error messages:
"Unauthorized"or similar indicates invalid API credentials; verify and update the API key."Not Found"when specifying an alias ID means the alias does not exist or does not belong to the selected domain."Failed to load options"suggests issues retrieving dynamic dropdown data; check network and API status.
Resolutions:
- Ensure the domain is correctly selected before choosing an alias.
- Confirm API credentials are valid and have necessary permissions.
- Check network connectivity and EmailConnect API availability.
Links and References
- EmailConnect API Documentation (replace with actual URL if available)
- n8n Expressions Documentation
- n8n Node Development Guide