How to test and run workflows

What this feature does

Opus provides three levels of workflow testing: node-level simulation with mock data, full workflow execution in the staging environment, and real-time monitoring of running workflows. Together, these ensure your workflow behaves correctly before production deployment.

Scope: This guide covers testing, running, and monitoring workflows. It does not cover creating workflows (refer to How to build workflows) or releasing to production (refer to How to publish and release).

Who this applies to

• Audience: Developers testing workflow automations in Opus
• Access required: Editor or Administrator role on the project
• Assumed knowledge: You have a workflow with configured trigger and nodes. Refer to How to build workflows.

Steps

Step 1: Test individual nodes

The Node Test Panel at the bottom of each node’s settings lets you test a single node with sample JSON input without triggering the full workflow.

1. Select a node on the canvas and open its settings.
2. In the Node Test Panel, enter test data as a JSON object.
3. Select Run Test. The output shows what the node would return during execution.

Not all nodes can be mocked. Decision, Decision Table, Expression, Function, Switch, Workflow, Delay, Extract File, and Convert File nodes require real values.

Step 2: Mock external integrations

For nodes that call external systems, use mock data to test without making real API calls.

To mock a trigger node:

1. Select the trigger node and open Settings.
2. Enable the Mock Data (Optional) toggle.
3. Enter mock data in JSON format — this replaces the real trigger payload during testing.

To mock other nodes: follow the same toggle-and-enter-data pattern in each node’s settings panel.

Step 3: Run the workflow in staging

After node-level testing, run the full workflow in the staging environment with real integrations.

1. In the Workflow Editor toolbar, select Run Workflow.
2. Enter the Payload (JSON input data) and an optional Identifier for tracking.
3. Select Execute. The workflow runs in the staging environment.

Running workflows executes in staging only. For production, create a release — refer to How to publish and release.

Step 4: Monitor execution

Track running workflows in real time to identify where errors occur.

1. After execution starts, the monitoring view shows each step’s progress and status.
2. Select a node to view its execution details — input data, output data, and timing.
3. If the data exceeds 2 KB, download the full payload as a file.

Constraints and limitations

Related features

• How to build workflows — create workflows, configure triggers, add nodes.
• How to publish and release — commit changes, regression test, and release to production.