The Test inbox is where email sent with a test key lands. The call is accepted in full β sender, attachments, block list, all checked as in production β but nothing is delivered to anyone and nothing uses quota. It's where the team integrating Casa Moura CafΓ©s' online store can test pedido-confirmado as many times as they want without a single customer receiving a fake order.
The tab is under Settings βΊ Test inbox and belongs to the Owner, like keys and webhooks. If it doesn't show for you, contact support.
How messages get here
Under Settings βΊ Integrations, create a key with Test key checked and use it in the system's test environment. Every send made with it shows up here instead of going out. The production key keeps sending for real β that's why the flag lives on the key and not in a detail of the call: a test environment holding only the test key can't send for real, even by mistake.
Remember the test key doesn't access contacts: it only sends and reads fields and lists.
Checking a message
The list shows Recipient, Status, Engagement (simulated opens and clicks) and Received at. Click a row to open the Test message:
- From, To and Reply to β check that the sender is Renata da Casa Moura <contato@casamoura.com.br> and not someone's test address;
- Attachments β name, type and size of each file, to check it arrived whole;
- Preview β the email as the recipient would see it, with the template variables already filled in.
Simulating an outcome
Under Simulate outcome, each button makes "happen" to the message what would happen in production: Delivered, Opened, Clicked, Bounced, Marked as spam, Unsubscribed and the other events a webhook can subscribe to. The event is recorded and the webhook is delivered for real, to the address you registered, just like production. That's how you test your receiver without waiting for a real bounce to happen to a customer.
Three things to watch:
- The simulated event also reaches your production webhook, flagged as test. Your production receiver must ignore it β or a simulated bounce unsubscribes a real customer in your system.
- Simulating doesn't block the address. In production, an unsubscribe, a hard bounce or a spam complaint would block the recipient; here, it doesn't. You can test the same bounce as many times as you need.
- An address that was already blocked has no outcome to simulate. In production the message would never go out, and the screen says so in place of the buttons.
How long messages stay
Test messages are deleted after a retention period. Opening one that is past it shows This message has expired. The inbox is a working tool, not an archive: whatever you need to keep, keep on your side.
Where to go next
- API keys β create the test key.
- Webhooks β add the address that will receive simulated events and see the deliveries in the history.
In short: use a test key in your test environment, check the sender, attachments and preview of each message in the Test inbox, simulate outcomes to watch the webhook arrive, and handle events flagged as test in your production receiver.