All docs
Feature reference Build tests 2 min reference

Email received validation

An email received validation waits for a matching message in the Rima test inbox and fails if it does not arrive.

This reference explains the term, its purpose, a practical example, common use cases, where it appears in Rima, and the closest product visual.
Adding a validation in the Rima extension
Validations define the result that must be true for a test to pass.

Definition

An email received validation waits for a matching message in the Rima test inbox and fails if it does not arrive.

What it is for

It verifies workflows where sending an email is part of the expected product behavior.

How it works

  • The test first generates an inbox address with a random-email step; the validation then waits for a message to that address.
  • Optional matchers narrow the check: sender contains, subject contains, body contains, and link URL contains.
  • Matchers left blank are ignored, so you only assert on the fields you care about.
  • If no matching email arrives during the run, the validation fails.

Example

Register with a generated address and require a “Verify your account” email from the expected sender to arrive within the run.

Common use cases

  • Registration verification.
  • Password reset email.
  • Order receipt.
  • Notification and alert testing.

Where to find it

Insert an email validation in the test editor and configure the generated address plus matching sender, subject, or content.

Limitations, requirements, and permissions

  • Available only in tests that already have a random-email step to create the inbox.
  • Checks messages sent to the generated Rima test address, not your personal inbox.

Related features and guides

Ready to try it yourself?

Create your free account, record your first flow, add a validation, and let Rima run it on a schedule for you.

Start free trial