Reference · Credentials

IMAP credentials

Used by 2 BusyBot nodes.

Type imap 6 fields

The IMAP credential connects directly to a mail server to read messages, holding the username, password, host, port and TLS setting. For Gmail and Outlook accounts with two-factor authentication, it needs an app-specific password rather than your normal one.

Fields

FieldTypeRequiredNotes
User
user
string Yes Email address or username for IMAP authentication
Password
password
password Yes Account password or app-specific password
Host
host
string Yes IMAP server hostname (e.g., imap.gmail.com)
Port
port
number Yes IMAP server port (993 for SSL/TLS, 143 for unencrypted)
SSL/TLS
secure
boolean Yes Whether to use SSL/TLS encryption
Allow Self-Signed Certificates
allowUnauthorizedCerts
boolean No Allow connections with self-signed certificates

Getting your credentials

  1. Find your mail provider’s IMAP settings — the host and port. Common examples are imap.gmail.com on port 993 and outlook.office365.com on port 993.
  2. Use port 993 with Secure enabled for TLS, which is what almost every provider expects. Port 143 is the unencrypted alternative and should be avoided.
  3. Enter the email address or username, and the password.
  4. If the account has two-factor authentication, generate an app-specific password in the provider’s security settings and use that instead of the account password.
  5. Make sure IMAP access is enabled on the mailbox — some providers disable it by default.

Permissions and scopes

IMAP grants access to the mailbox as that user, so it is broad by nature. For automation, a dedicated mailbox is preferable to a personal one.

Allow self-signed certificates only for internal servers you control, and never for a public provider.

Troubleshooting

  • Authentication failed on Gmail or Outlook — the account requires an app-specific password, or IMAP is disabled on the mailbox.
  • Connection timeout — the host or port is wrong, or the mail server is not reachable from the workflow environment.
  • Certificate errors — the server uses a self-signed certificate. Enable the option only if it is a server you control.
  • Works in a mail client but not here — the client may be using OAuth rather than password authentication.

Frequently asked questions

Why does my normal password not work?

Providers with two-factor authentication require an app-specific password for IMAP. Generate one in the account's security settings and use that instead.

Which port should I use?

993 with Secure enabled, for TLS. Port 143 is unencrypted and should be avoided for anything over the public internet.

Should I allow self-signed certificates?

Only for an internal server you control. Enabling it for a public provider defeats the point of TLS.

Why can it not see my mail?

IMAP may be disabled on the mailbox — several providers turn it off by default and it must be enabled in the account's settings.

Nodes that use IMAP

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.