Workflow Inbox Hosting

Let automation agents send and receive email/messages safely without client credentials

Problem

When a client automation workflow needs to send or receive emails or messages, developers must either use the client's account or build their own forwarding setup, making access and handover painful (one poster asks 'when a workflow needs to receive and send emails or messages, whose accounts does it use? how do you handle setup, access and handing it over to the client?'). Existing options either involve insecure password sharing or complex configuration.

Solution

A hosted inbox and messaging channel service that provisions dedicated addresses/numbers per workflow, supports sending and receiving via API, and allows one-click ownership transfer to the client. Includes a simple handover UI and call logs, eliminating password sharing.

Users

Developers building client automation workflows, AI automation agencies, freelancers

MVP

Create dedicated email addresses and SMS channels per workflow; simple API and webhook for receiving; one-click ownership transfer to client; call logs and message history; support both email and SMS.

Revenue

Tiered subscription by number of workflows or message volume; free tier with limited channels and messages; enterprise plan with audit and SLA.

Why now

AI automation agents are proliferating, messaging channels are a common need but costly to set up; indie developers can wrap existing email/SMS APIs quickly.