EmailConnect icon

EmailConnect

Interact with EmailConnect API for email automation

Actions12

Overview

This node interacts with the EmailConnect API to manage email aliases, domains, and webhooks for email automation workflows. Specifically, the "Alias - Update" operation updates an existing email alias by changing its destination email address. This is useful when you want to redirect incoming emails from an alias to a new forwarding address without creating a new alias.

Practical examples include:

  • Updating the forwarding address of a support alias when the responsible team changes.
  • Redirecting emails from an alias to a different user or mailbox dynamically in an automated workflow.

Properties

Name Meaning
Alias Name or ID Select an existing alias by name or ID to update. The list depends on the selected domain.
Destination Email The new email address where emails sent to the alias will be forwarded.

Output

The output JSON contains the updated alias object as returned by the EmailConnect API after the update operation. It typically includes details such as the alias ID, email address, destination email, and other metadata related to the alias.

Example output structure (simplified):

{
  "id": "alias-id",
  "email": "alias@example.com",
  "destinationEmail": "newuser@example.com",
  ...
}

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the EmailConnect API.
  • The node uses internal methods to load available domains and aliases dynamically.
  • Network access to the EmailConnect API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Selecting an alias without specifying the correct domain may result in no options or errors.
    • Providing an invalid or unreachable destination email could cause the API to reject the update.
    • Network or authentication failures will prevent successful API calls.

  • Error messages:

    • Errors from the API are propagated; typical messages might include "Alias not found" if the alias ID is incorrect.
    • Authentication errors if the API key is missing or invalid.

  • Resolutions:

    • Ensure the domain is correctly selected before choosing an alias.
    • Verify the destination email format and validity.
    • Confirm that the API key credential is configured properly in n8n.

Links and References

Discussion