Skip to main content
Test mode lets you run your pipeline end-to-end without triggering real side effects. When test mode is enabled, output nodes (callback and email) produce a dry-run preview instead of sending actual requests or emails. All other nodes execute normally. Test mode applies to every run of the pipeline: manual runs from the Run button as well as automatic runs triggered by an upload, webhook, or inbound email.

​
How it works

New pipelines start in real mode (test mode off), so a configured pipeline sends real callbacks and emails whenever it runs. Turn test mode on whenever you want to run the pipeline without those side effects. In test mode:
  • All trigger, action, and processing nodes run normally. Extraction, parsing, transformation, validation, routing, merging, and review steps execute exactly as they would in production.
  • Callback nodes resolve the URL, method, headers, and body but do not send the HTTP request. Instead, they return a preview of what would have been sent.
  • Email output nodes render the email HTML but do not send the email. Instead, they return a preview showing the recipients, subject, rendered body, and attachment names.
The HTTP action node is not affected by test mode. It always sends real requests regardless of the test mode setting. Use caution when testing pipelines that include HTTP action nodes pointed at production endpoints.

​
Toggle test mode

You can toggle test mode from the pipeline editor toolbar:
  1. Open your pipeline and click the Pipeline tab to open the editor.
  2. Find the Run button in the toolbar. Click the dropdown arrow next to it.
  3. Select Test mode or Real mode.
When test mode is on, the Run button uses its default appearance. When test mode is off, the Run button turns red to indicate that output nodes will send real requests and emails.
When you switch to real mode and click Run, a confirmation dialog appears warning that output nodes will send real requests and emails. This safeguard prevents accidental production deliveries.

​
Dry-run preview

When a run completes in test mode, output steps display a special preview instead of raw output. The preview includes a blue “Test mode preview, not sent” banner and shows a structured breakdown of what would have been sent.

​
Callback preview

The callback dry-run preview shows:
  • HTTP method and resolved URL
  • Request headers (if configured)
  • Request body (formatted as JSON or HTML)
The rendered request body appears in a read-only JSON editor, pretty-printed for easy inspection. Because no delivery is recorded for a test-mode step, this prepared-request preview also shows up in the run-detail Callback Delivery History panel in place of an actual delivery record.

​
Email preview

The email dry-run preview shows:
  • Recipients (displayed as badges)
  • Subject line
  • Rendered email body (with HTML preview)
  • Attachment file names (if configured)
You can switch between a Preview tab (structured view) and a Raw tab (full JSON output) to inspect the dry-run payload.

​
Credit usage

Test runs consume credits for AI-powered nodes (extract, parse, AI validation, AI-based routing) because those steps execute fully. Output nodes (callback, email) do not consume credits regardless of test mode.

​
When to use test mode

Pipelines run in real mode by default. Turn test mode on when:
  • You are building or iterating on a pipeline and want to preview output nodes without sending real callbacks or emails
  • You want to inspect the exact payload a callback or email would produce before going live
  • You want to validate extraction and parsing results without delivering them downstream
Turn test mode off again once you have verified the pipeline and are ready to send real callbacks and emails.

Build your first pipeline

Step-by-step guide to building and testing a pipeline

Callback node

Configure webhook delivery for pipeline results

Email output node

Configure email delivery for pipeline results

Pipeline editor

Learn about the visual pipeline editor