Messaging and Email Credentials

Use these credentials for event-driven workflows and outbound notifications.

Supported targets

• Kafka brokers — used by kafka_consumer (trigger) and kafka_node (produce)
• SMTP servers — used by smtp_node for outbound email
• SendGrid API — used by sendgrid_node for transactional email
• IMAP servers — used by imap_trigger to receive and process inbound email

IMAP credentials

IMAP credentials connect an imap_trigger node to an incoming email mailbox.

Field	Description
Host	IMAP server hostname (e.g. imap.gmail.com, mail.example.com)
Port	993 for implicit TLS; 143 for STARTTLS
Username	Login username (usually the full email address)
Password	Login password (encrypted at rest using platform key)
Use TLS	Enable for direct TLS connections (port 993 recommended)

Validate before saving

Click Validate Connection in the credentials form to test the IMAP connection live before saving. This dials the server, authenticates, and verifies the target mailbox exists — without storing any data.

Tips

• For Gmail, use an App Password if 2-factor authentication is enabled. The regular account password will not work.
• For Office 365, enable IMAP access in the Exchange admin center; use outlook.office365.com port 993.
• Use a dedicated service account mailbox rather than a shared personal inbox.
• The mailbox field in the imap_trigger node must match the folder name exactly as the server reports it (case-sensitive on some servers).

Common fields (all types)

• Endpoint or host
• Port and protocol
• Username/password or API key
• TLS and authentication mode

Practical guidance

• Validate connectivity from the gateway runtime environment before saving.
• Use dedicated service accounts per integration channel.
• Monitor retry and dead-letter behavior for failed sends (Kafka, SMTP, SendGrid).
• Rotate credentials through the platform credential lifecycle — existing workflow runs are not interrupted during rotation.