ZSend can receive inbound email through supported provider integrations, persist the message, and emit an inbound webhook event for the rest of your system.
Repository checkInbound processing is implemented for Google Workspace and Cloudflare Email Routing integrations.
Important context: Inbound support is provider-specific. Google Workspace requires Gmail Pub/Sub and Cloudflare requires Email Routing and Worker setup; AWS SES and SMTP do not support inbound email in the current channel implementation.
A connected Workspace account can use Gmail Pub/Sub notifications. ZSend receives the notification, processes the message, and makes the inbound event available to downstream webhook consumers.
Cloudflare Email Routing can deliver inbound mail to a ZSend Worker. The receive path resolves the destination domain, persists the message and attachments, and emits the inbound webhook event.
Inbound processing is connected to the existing inbox UI and webhook system. That gives a product team a path from a received message to an application-specific action without presenting inbound as a universal provider abstraction.
Join the ZSend waitlist and help shape an email workflow that keeps application code, content, and provider context together.