The Team Inbox
Your workspace's own email address and phone number, the bridge between your team's messages and your automations.
Every workspace gets its own email address, something like
your-team@inbox.ramain.ai. It looks like a small thing, but it's one of the
most useful surfaces on the platform: it's how automations receive work,
receive codes, and report back, all over plain email, the tool your team
already lives in.
You'll see the address on the Workflows page banner and at the top of the Inbox page, where every message it receives is collected into threads.
Three jobs, one address
A subject-match rule turns an incoming email into a run, with the workflow's inputs extracted from the message itself.
When a website emails an OTP or a confirmation mid-run, agents watch the inbox for it and keep going. No one babysits the login.
Ground the Builder in real mail
While authoring, the agent can list recent inbox messages and build the demo around a real one, so the workflow is shaped by actual data from day one.
Triggering is the headline: set up an email trigger on the Triggers page, and any matching email from a workspace member launches a run automatically.
Codes and values solve a quieter problem. Plenty of sites email a verification code or a confirmation link partway through a task. When a workflow signs up or signs in with the team address, the running agent polls the inbox for the message it's waiting on, reads the code, and continues, unattended.
Authoring closes the loop. If you're building a workflow that processes incoming requests, you don't have to invent a fake example: the Builder can pull a recent real message from the inbox and teach the workflow against it.
A round trip, start to finish
The screenshot above shows a complete email-to-run round trip. It's worth walking through, because it's the experience your team actually gets:
Step 1
Priya sends an email. She emails the team address with the subject "Process May invoices". She isn't a builder and she doesn't open RamAIn; she just sends mail like she would to a colleague.
Step 2
The trigger matches. The subject contains the phrase configured on an email trigger, and Priya is a workspace member, so the trigger fires. The AI extractor reads her email (following the trigger's extraction instructions) and fills the workflow's inputs from what she wrote.
Step 3
The run launches. The inputs parse, so the workflow starts automatically and appears on the Sessions page like any other run. Priya can get a reply on the same thread confirming the run is underway.
Step 4
The agent replies with results. When the run finishes, the reply lands back on her thread: "Automation completed", which workflow ran (NetSuite Invoice Loader), what it did ("14 invoices loaded"), and the reconciliation report attached as a PDF.
For the sender, the entire automation is "send an email, get the answer back". The thread is the interface, the audit trail, and the delivery mechanism, all at once.
The Inbox page itself works the way you'd expect from email: threads with read state, attachments you can open, and the automated agent replies inline so you can audit exactly what was sent back and when.
Phone & SMS
Email isn't the only channel. Every workspace can also have its own phone number, shown under the Phone tab of the Inbox page.
It does for text messages what the address does for email:
- Inbound SMS shows up in the Phone tab, message by message, alongside the email threads. Whatever arrives at your workspace number is visible in one place.
- Verification codes sent by SMS are captured for running workflows. Plenty of sites insist on texting a code instead of emailing one. When a workflow signs in with the workspace number, the running agent polls for the incoming text and reads the code exactly the way it reads an email OTP. The run continues unattended either way; the channel the website chose stops mattering.
- SMS can forward to email, so texts land in the same inbox stream your team already watches and nothing is missed because nobody had the Phone tab open.
Between the address and the number, the workspace can receive nearly anything a website or a teammate sends it, and your automations can act on all of it.
Who can see the inbox
The Inbox page is available to workspace admins. Triggers, code capture, and authoring against inbox mail all work for the whole team; the page itself is just the admin's window into the raw messages.
Where to next
Set up the subject-match rules that turn inbox mail into runs.
Where every email-triggered run shows up: live view, history, and statuses.
The full picture: messaging channels, data sources, credentials, and the API.
Was this page helpful?