EmailConnect Trigger icon

EmailConnect Trigger

Trigger workflows when emails are received via EmailConnect - 100% EU-operated email service with multi-alias support

EmailConnect Trigger

AI-generated

Overview

The EmailConnect Trigger node integrates with the EmailConnect email service to trigger workflows when emails are received. It supports configuring email routing either via a domain catch-all or specific email aliases, automatically managing webhook endpoints for these aliases. This node is beneficial for automating email processing workflows such as support ticket creation, email notifications, or any email-driven automation within a 100% EU-operated secure email environment.

Use Case Examples

  1. Automatically trigger a workflow when an email is received at support@yourdomain.com by configuring a specific alias.
  2. Route all emails sent to any address at yourdomain.com to a single workflow using the domain catch-all option.

Properties

Name Meaning
Domain Name or ID Select the verified domain in EmailConnect to configure the trigger for. The domain's webhook endpoint will be updated to point to this workflow.
Alias Configuration Choose how to route emails to this workflow: either all emails to the domain (catch-all) or a specific alias email address.
Alias The local part of the email address (before @) to route to this workflow. Used only if 'Use Specific Alias' is selected. The alias will be created or updated automatically.
Webhook Name A descriptive name for the webhook configuration. Defaults to the email address plus 'endpoint trigger' if left empty.
Webhook Description Optional description for the webhook configuration.

Output

JSON

  • json - The JSON payload of the received email or webhook event data.

Dependencies

  • EmailConnect API key credential

Troubleshooting

  • Ensure the domain is verified in EmailConnect before selecting it in the node, otherwise webhook configuration will fail.
  • If using specific alias mode, the alias local part must be provided; otherwise, the node throws an error.
  • Webhook creation or update may fail if the API key is invalid or lacks necessary permissions.
  • If the webhook URL changes, the node attempts to update the webhook endpoint automatically, but stale webhook IDs in static data may cause issues; resetting the node's static data can help.

Links

Discussion