Overview
Simulate step responses with mock outputs
Mock outputs let you simulate step execution using realistic sample data instead of running the actual step. This makes it easier to test workflow behavior, validate logic, and understand how changes affect downstream steps without sending live API requests.
Mock outputs are especially useful when working with time-consuming steps, incomplete integrations, user-dependent actions, or edge cases that are difficult to reproduce on demand. They provide a safe and efficient way to test workflows before moving to production.
Common use cases
Mock outputs can help you in several testing scenarios:
Test part of a workflow: Run specific sections of a workflow without executing every preceding step.
Simulate edge cases: Manually define responses for failures, unusual outputs, or other hard-to-reproduce scenarios.
Build new workflow sections: Reuse outputs from earlier executions to test new logic in context.
Work without full integration setup: Continue developing and validating steps even before integrations are fully configured.
Important behavior
Mock outputs are available only during workflow development and testing.
Mock outputs are disabled in published workflows and do not affect production executions.
When a step runs with mock output, the step’s properties, input parameters, integration, and Execution Options are ignored.
Mock output configurations are saved with the workflow when published and remain available for future development.
Mock output configurations are also included in workflow export and import.
How to use
Configure a mock output
Select step: Identify the step you want to test with mock output.
Open Mock Output tab: Navigate to the step’s Mock Output tab.
Enter mock data: Add the desired mock response in the Output field. You can use the suggested output example as a starting point or paste output copied from a previous execution log.
Reference output example: Use the step three-dot (...) menu and select Output Example to view a sample response format. You can use it as a reference when updating or reverting your mock output configuration.
Enable mock output: Turn on Enable mock output. When enabled, the step is marked with a yellow frame.
Execute a step with mock output
Execute with mock output: Use Execute with mock output to simulate the selected step with the predefined data. The mock data is added to the workflow context without triggering live actions.
Run a workflow with mock outputs
Open test options: Click the arrow next to Test Run.
Select mock run: Choose Test run with mock output to test the workflow using the configured mock data.
A standard Test Run executes the workflow using live step behavior instead of mock data.
Troubleshooting and tips
Use valid JSON: Ensure the mock output is valid JSON.
Check size limit: Keep mock output under 100 KB.
Test in sections: For complex workflows, test smaller sections to isolate issues more easily.
Simulate edge cases intentionally: Use mock outputs to validate how the workflow behaves under error conditions or unusual responses.
Use cases
These examples demonstrate how mock outputs can be used for different testing scenarios. They are based on a simplified version of the Suspend Contractor Accounts with no logins in 7 days template.
Use output examples as mock data
Use the step output example as a baseline and modify it to match your test scenario.
Copy the output example from the step
Update the values with safe test data
Preserve the original structure to ensure compatibility with downstream steps
This approach is useful when you want realistic responses without calling the actual integration.
In the example below, a mock output for the Okta List Users with Filters step is created by copying the step output example and modifying it to include test users that are safe to use for workflow validation.
Avoid live API requests
Use mock outputs to simulate step execution without triggering real actions.
Configure a mock output for steps that perform write operations
Run the workflow with real upstream data while preventing changes in external systems
This is useful for safely testing workflows that include sensitive actions (for example, suspending users).
Test nested workflows
Mock outputs can also be applied to nested workflows.
Configure a mock output on the nested workflow step
Validate the expected output by reviewing the Exit operators of the nested workflow
This allows you to test parent workflows without executing the full nested logic.
Use Go templates in mock outputs
You can use Go templates to further customize your mock outputs. In the example below, a variable from the workflow context determines which of two mock output variations is returned.
For more information, see Go templates.
