Send a test item

Updated 16 October 2026 · 2 min read

A test item behaves like a real item: it is checked, waits for its send rule, appears in the portal and triggers webhooks. But it is never printed, never handed to PostNL and never charged. Use test items to check an integration before you go live.

Create test items

You do not create test items in the portal itself. They come from your integration in test mode:

  • API: your developer creates items with a test key. In Developers, choose Create key and set Mode to Test. See API keys for your developers.
  • Salesforce: the "Send Mail Item" action has a test mode input. Set it to true in your flow, with a test key in the PostBuddy test credential. See Connect Salesforce.

Test items show the label Test in the Items list and on the item. Filter on them with Mode in the Items filters.

Run a simulated production run

Real production runs never collect test items. To see a test item go all the way to the end:

  1. Make sure the test item has the status Ready.
  2. Open Developers and choose the Test runs tab.
  3. Pick a Postflow, or keep All Postflows.
  4. Pick the Outcome: Completed or Failed.
  5. Choose Run simulation.

The ready test items move through scheduling, production, the carrier handoff and completion (or failure). Each step sends its webhook, so your Salesforce org or system receives the whole sequence. The result shows how many items completed, failed, were suppressed or were skipped.

Running a simulation needs a role that can edit items: Owner, Admin, Editor or Approver. Test mode is free and never limited by your plan.

Want a real printed card?

A test item is never printed. To hold a real card in your hands, order a sample from the template page. See Preview and proof PDF.

For developers, the full details are in the test mode guide.

Still need help?

Open a support ticket in the portal. Tell us what you tried and, if you can, which item or Postbatch it is about.

Contact support