Email (sending)

What it is

An email connection is how workflows send mail. Pick a provider, verify a sending domain with them, and give Honeybase the credential.

Two ways to authenticate, decided by the provider you pick: an API key for Resend, SendGrid and Postmark, or an SMTP username and password for everything else.

This integration only sends. To read mail and trigger workflows from it, use the IMAP integration.

Before you start

Verify your sending domain with the provider first, and add their SPF and DKIM records to your DNS. Sending from an unverified domain either fails outright or lands in spam, and no Honeybase setting can compensate for a missing DKIM record.

Setup fields

These are the fields the guided setup collects — both the Add integration form and the setup card Barry raises in chat. Additional settings live on the connection's settings page once it exists.

Connection settings

Field	Type	Required	Secret	Notes
name	Text	Yes	No	Display name for this connection. This is what you pick from in a workflow node.
provider	Choice	Yes	No	Which service sends the mail — Resend, SendGrid, Postmark, or a plain SMTP server. Your choice here decides which credential fields apply.
fromEmail	Text	Yes	No	The address messages are sent from. It must be on a domain you have verified with the provider.
fromName	Text	No	No	Display name shown next to the from address. Optional.
smtpHost	Text	No	No	Hostname of the SMTP server. SMTP provider only.
smtpPort	Number	No	No	Port for the SMTP server — usually 587 for STARTTLS or 465 for implicit TLS. SMTP provider only.
smtpSecurity	Choice	No	No	How the connection is encrypted — STARTTLS, SSL, or none. SMTP provider only.

Credentials

This integration has 2 credential options. You supply the fields for the one you pick.

API key

For Resend, SendGrid and Postmark. The provider is called over HTTPS and there is nothing to configure on your mail server.

Field	Type	Required	Secret	Notes
apiKey	Password	Yes	Yes	The API key issued by Resend, SendGrid or Postmark. See the per-provider steps below.

SMTP username and password

For any SMTP server, including mailbox providers such as Google Workspace or Microsoft 365, and for the SMTP endpoints of the API providers.

Field	Type	Required	Secret	Notes
smtpUsername	Text	Yes	No	The username for SMTP authentication. Often the full email address; some providers use a fixed literal such as apikey.
smtpPassword	Password	Yes	Yes	The password for SMTP authentication. For a mailbox provider this is usually an app password rather than your account password.

Getting an API key

Resend — resend.com/api-keys → Create API Key. Sending permission is enough. Verify your domain under Domains first.

SendGrid — Settings → API Keys → Create API Key. Choose Restricted Access and grant only Mail Send. Complete Sender Authentication for your domain before sending.

Postmark — open the server you want to send from and copy its Server API token from the API Tokens tab. Add and confirm a Sender Signature or domain first.

Using SMTP instead

Any SMTP server works. Typical settings:

Server	Host	Port	Security
Google Workspace	smtp.gmail.com	587	STARTTLS
Microsoft 365	smtp.office365.com	587	STARTTLS
SendGrid over SMTP	smtp.sendgrid.net	587	STARTTLS

For Google Workspace and Microsoft 365, generate an app password for the account rather than using its sign-in password — accounts with two-factor authentication will refuse a plain password. For SendGrid's SMTP endpoint the username is the literal string apikey and the password is the API key.

Note that the SMTP username is stored as an ordinary setting, not as a secret — it is an identifier, and keeping it readable makes a misconfigured connection diagnosable. Only the password is held in the secret store.