01
Workspace
Connect a mailbox when the product belongs in Gmail.
Google Workspace is available as a connected email channel. Its receive-side path can also use Gmail Pub/Sub when inbound is enabled and configured.
← All features
05 / provider layer
Use the email connections your team already operates.
ZSend connects product email to Google Workspace, AWS SES, Cloudflare Email, or SMTP. The provider details stay visible instead of becoming another opaque dependency in your stack.
Repository checkThose four channel types are represented in the application provider and sender configuration surfaces.
WHAT IS HERE
- +Google Workspace through its connected account
- +AWS SES with verified sending identities
- +Cloudflare Email for supported domain flows
- +SMTP for applications that already speak SMTP
02
SES and Cloudflare
Keep cloud email infrastructure in the delivery picture.
AWS SES and Cloudflare Email are supported channel types for sending. Domain setup and provider configuration remain explicit in the dashboard, so teams can see which connection a sender uses.
03
SMTP
Give older integrations a supported route forward.
The SMTP proxy and SMTP channel let applications that already speak SMTP send through ZSend. It is a compatibility path for existing software, alongside the REST API and SDK.
NEXT / YOUR EMAIL LAYER
Make sending
part of the product.
Join the ZSend waitlist and help shape an email workflow that keeps application code, content, and provider context together.