Requirements: Admin or Editor role.
“Email (read)” is a special integration: it only supports named connections (it has no shared “main” connection) — every mailbox you connect is always its own connection, with its own scope. It reads your inbox (Gmail, Microsoft 365, Outlook.com, Yahoo, iCloud, or a generic IMAP server) — read-only, it never sends email.
4.1 Provider presets
Section titled “4.1 Provider presets”Choosing your provider preloads the server, port and encryption — editable, in case your provider needs something different. All you need to type is the email address and the password (or app password):
| Provider | What you need |
|---|---|
| Gmail / Google Workspace | Email + app password (requires two-step verification enabled on your Google account). |
| Microsoft 365 | Email + app password (your administrator has to enable them). |
| Outlook.com | Email + app password from your personal Microsoft account. |
| Yahoo Mail | Email + app password. |
| iCloud Mail | Email + app-specific password from your Apple ID. |
| Generic IMAP | Email + password, plus your provider’s server/port/encryption (not preloaded). |
Note — For billing mailboxes, “This flow only”
The form recommends it by default: that way no other flow can read that mail. Choose “Shared” only if several flows need to use the same mailbox.
4.2 Testing and honest errors
Section titled “4.2 Testing and honest errors”“Connect and test” checks the credentials LIVE against your real mail server before saving anything — a credentials or server error is explained by its cause, never a generic message:
This piece’s 4 actions — list new messages, read a message, download an attachment and mark as processed — are always internal: the conversational assistant never uses them with the customer, only your own flows do.