All nodes/Integrations/Email

Email Config

Selects a saved email connection of the workspace. Credentials are set in the workspace settings, not in the graph.

Try it

When to use it

A separate node for the mailbox is not always needed. Send Email, Fetch Emails and the Email Tool each carry an “Email connection” field of their own, which is enough for a graph that sends one message. This node earns its place when several nodes share one mailbox: the connection is picked in a single place, and the canvas shows where the mail comes from.

How it works

The node stores neither address nor password. It references an integration from Settings → Integrations (kind Email: provider, IMAP/POP3 host and port, login, password, SMTP host and port) and, during a run, passes the resolved settings along the wire into the consumer’s email_config port.

It needs no execution wiring: the node has no execution input, the platform resolves the connection when the first consumer asks for it and reuses the result for the rest of the run. In the run log this node shows only the connection name — credentials reach neither the logs nor the event stream.

The wire always beats the field on the consumer: if a node has “Email connection” filled in and something is also wired into its email_config port, the port wins.

Common mistakes

• An empty “Connection” field. The node stops with an error instead of guessing a mailbox.
• An account password instead of an app password. Gmail, Yandex and Mail.ru reject the account password over IMAP and SMTP; the integration form says so when you pick the provider.
• A blank SMTP host on the integration. Sending then falls back to the mailbox host, which is not the submission host at any major provider. In that case “Check connection” reports that SMTP is not configured and verifies reading only.
• One mailbox, one node. Two different mailboxes need two config nodes; a single one can feed any number of email nodes.
• Expecting an edited integration to apply mid-run. Nothing is copied into the graph, but a run reads the connection once — the change takes effect on the next run.

Inputs

—

Outputs

Configuration