The SMTP integration sends email. Recipients continue conversations and decisions in the authenticated Beepgrid workspace. Replying to the email itself does not create a native inbound Beepgrid reply.
Connect SMTP
Section titled “Connect SMTP”- Open Integrations → Email (SMTP) → Add connection.
- Enter your provider’s SMTP host and port, sender address and, when required, username and password or app password.
- Save the connection and add the intended recipient email address as a destination.
- Configure the person’s delivery preference and current contact access.
Find these values in your mail provider’s SMTP settings. Use its supported sender/domain verification. Production connections require STARTTLS; a local development relay is a separate self-hosting setup.
An unauthenticated local relay does not need an artificial username or password. Do not use that development configuration as a public production mail service.
Verify actual receipt
Section titled “Verify actual receipt”Send a harmless test, open the recipient’s real mailbox and follow the workspace continuation link. Sign in as the intended person and verify that the correct conversation is accessible.
An SMTP server accepting a message does not prove mailbox delivery. Check spam, sender verification, recipient routing and provider delivery logs if the email does not arrive.
Protect the account
Section titled “Protect the account”Keep SMTP credentials in the connection’s secret storage. Do not put them in agent prompts or frontend code. Configure a Reply-To address that your organization actually monitors; it does not create an inbound message adapter.
Use Slack, Telegram or Discord when you need supported native replies and approval buttons.