Connect Email (SMTP) to B6AI

Overview

The Email (SMTP) integration lets B6AI send outbound email through any SMTP server (your email provider, Google Workspace, Microsoft 365, Amazon SES, SendGrid and more) so bots and workflows can send confirmations, notifications and transcripts from your own domain.

Unlike the Gmail integration (which reads and replies to a specific mailbox), this is a general-purpose send-only channel for transactional mail.

What you can do with Email (SMTP)

Once connected, your bots and agents can use Email (SMTP) inside conversations and automations. Typical uses include:

1. Send a confirmation or notification email from a flow.
2. Email a conversation transcript to the customer or an internal address.
3. Send verification codes or one-time passwords.
4. Alert a team distribution list when something needs attention.
5. Deliver receipts and follow-ups after a conversation.

How the integration works

B6AI connects to your SMTP host on a specified port using a username and password over TLS, and sends mail as your configured “From” address. There is no OAuth, you provide the host, port, credentials and encryption.

Credentials are stored encrypted at rest. For good deliverability, your sending domain should have SPF and DKIM configured.

Prerequisites

Make sure all of the following are in place before you start. Each one is required, skipping any will cause the connection to fail later.

1. An SMTP account from your email provider or a sending service (for example Amazon SES SMTP or SendGrid SMTP).
2. The SMTP host, port, username and password.
3. A “From” address (and ideally a verified domain with SPF/DKIM) you are allowed to send as.
4. The Enterprise Admin role in B6AI.

Choose a connection method

B6AI supports more than one way to connect Email (SMTP). Pick the one that fits your organization’s policies, the rest of this guide works for either.

Generate your SMTP server credentials

B6AI authenticates with Email (SMTP) using your SMTP server credentials. Follow these steps exactly, each field you copy here is entered into B6AI later.

1. In your email provider, find the SMTP settings (host and port).
2. Create or copy an SMTP username and password. For Gmail/Workspace with 2-Step Verification, create an App Password (Google Account → Security → App passwords), not your normal login password.
3. For Microsoft 365, enable SMTP AUTH for the mailbox and use its credentials (or an app password).
4. For Amazon SES, create SMTP credentials in the SES console (these differ from your AWS keys).
5. Confirm the exact “From” address you are authorized to send as.

Connect Email (SMTP) in B6AI

Now enter your credentials in B6AI. Signed in as an Enterprise Admin, open Settings → Integrations, find the Email (SMTP) card and click Connect, then complete the form. Every field is explained below.

1. In B6AI, open Settings → Integrations → Email (SMTP).
2. Enter the host, port and encryption method.
3. Enter the username and password (or app password).
4. Set the From name and From address.
5. Click Send test to email yourself, then Save.

{
  "provider": "smtp",
  "host": "smtp.gmail.com",
  "port": 587,
  "encryption": "starttls",
  "username": "support@yourco.com",
  "from": "YourCo Support <support@yourco.com>"
}

Verify the connection

Confirm the integration is live before you rely on it in a bot.

1. Enter a recipient in Send test and send a test email.
2. Confirm it arrives (check the spam folder too).
3. Confirm the From name/address and any branding look right.

Troubleshooting

If the connection fails or an action does not work, match the symptom below to its cause and fix.

Limitations & rate limits

Keep these constraints in mind so your bots behave predictably at scale.

1. Providers cap how many emails you can send per second and per day.
2. Some networks block port 25; prefer 587 or 465.
3. Deliverability depends on SPF, DKIM and DMARC, this is for transactional mail, not bulk marketing.

Security best practices

1. Use an app password or a dedicated SMTP credential, never your primary email login.
2. Always use encryption (STARTTLS on 587 or SSL on 465); avoid unencrypted port 25 over the internet.
3. Configure SPF, DKIM and DMARC for your sending domain to protect deliverability and prevent spoofing.
4. Restrict the From addresses to domains you control.
5. Rotate the SMTP credential periodically and immediately if it’s exposed.

Recommendations

1. Test against a sandbox or non-production Email (SMTP) account before connecting live data.
2. Document which bots and flows depend on this integration so changes are predictable.
3. Set a recurring reminder to review scopes and rotate credentials.
4. Enable only the capabilities you actually use today; you can widen scopes later.