Robotic Process Automation (RPA) tools like UiPath, Automation Anywhere, and Power Automate can automate many desktop and web workflows. But email verification flows are a common blocker. When a bot needs to fill out a form and the service sends a verification code, the bot has no way to retrieve it from a shared inbox reliably.

The Problem with Shared Email Accounts

Most RPA teams create a shared email account for bots. This works for one bot running sequentially. When you scale to multiple bots running simultaneously, OTPs get mixed up. Bot A picks up Bot B's code and fails. The only fix is serializing the bots, which eliminates the performance benefit of RPA.

The AgentMailr Solution

Each bot execution creates its own inbox via API, uses that address in the form, and retrieves the OTP from that inbox. There are no shared resources and no collisions.

HTTP Calls from RPA Platforms

Most RPA platforms support HTTP requests natively:

  • UiPath: Use the HTTP Request activity
  • Power Automate: Use the HTTP connector
  • Automation Anywhere: Use the REST Web Service task
  • n8n / Make.com: Use the HTTP node

All three operations (create inbox, use address in form, retrieve OTP) are simple GET and POST HTTP calls with an API key header.

Example Flow

  1. Bot starts. HTTP POST to create inbox. Get back address and id.
  2. Bot opens web form. Types address into the email field.
  3. Bot submits form.
  4. HTTP GET to /v1/inboxes/{id}/otp?timeout=60. Waits. Gets OTP.
  5. Bot types OTP into verification field.
  6. Done.