icon will appear in the top-right corner, indicating the specific step and action that requires configuration or connections. Clicking the step link expands the step and takes you directly to the step that needs to be configured or requires a connection to be added.

*** ### Testing Different Workflow Trigger Types You can test an [On-Demand Workflow](/docs/workflows/building-workflows/triggers/on-demand-triggers/on-demand-triggers) by providing test input parameters. Follow the steps below to configure and execute a test run. Click the 'Test parameters' button to open the configuration panel where you can define input values for the test run You can change the runner to execute the Workflow with a different environment. By default, the Blink Cloud runner is used. Click **Apply** to confirm your test parameters. Any action requiring input parameters will use the values you’ve set. Click **Run test** to execute the workflow with the configured test parameters. This allows you to simulate the workflow using your specified input values and environment settings. ## Testing On-Demand Workflows- Use Case Example ### Overview In this use case, we demonstrate how to test an [On-Demand Workflow](/docs/workflows/building-workflows/triggers/on-demand-triggers/on-demand-triggers) by providing test values for its [input parameters](/docs/workflows/building-workflows/triggers/on-demand-triggers/input-parameters). By entering test data, such as an email list and a user name, we can simulate a real execution and ensure the workflow functions as expected. This process allows us to validate how the workflow processes user data, checks for publicly accessible files, and takes appropriate actions based on its logic.

## 1. Webhooks An **Event-Based Workflow** can be tested using a JSON sample of a potential incoming payload event triggered by a [Webhooks](/docs/workflows/building-workflows/triggers/event-based-triggers/webhooks). Follow the steps below to configure and execute a test run. Start by selecting the Webhook of your choice option as the trigger for your workflow. This will generate a unique Webhook URL that the workflow listens to for incoming events.

After configuring the trigger, click the 'Test parameters' button to open the configuration panel.

Next, click **“Listen to Event”** to activate the webhook listener. This step ensures that Blink is ready to receive and process an incoming payload request. The platform now displays the Webhook URL that external services (or test tools) can send data to.

To test how the workflow reacts to an event, you send a **test request** to the Webhook URL. Using [Postman](https://www.postman.com) (or another API testing tool), you: * Copy and paste a sample **JSON object** representing the type of event your workflow will handle. * Send an **HTTP POST request** to the Webhook URL. Once the request is received, Blink captures the event data and displays it in the interface. When configuring an event-based (webhook) trigger, you can define conditions that determine whether an incoming event starts the workflow. During testing: * Enabled: The workflow runs in test mode even if the payload does not meet the trigger conditions. * Disabled (default): The workflow runs only if the test payload satisfies the configured conditions. **Note**: This setting does not affect the published workflow behavior.

If needed, you can change the runner to execute the workflow in a different environment. By default, Blink uses the **Blink Cloud runner**, but you can select another runner if required.

Finally, you click **“Run Test”** to execute the workflow using the test event. This simulates a real event and allows you to verify that the workflow processes the incoming data correctly. ### Using the Custom Webhook - Use Case Example

A [Scheduled Workflow](/docs/workflows/building-workflows/triggers/scheduled-triggers) can be tested using the following instructions: * No test parameters are needed when testing a scheduled trigger workflow. Ensure that all steps within the workflow are configured correctly. * Afterward, simply click the "Test Run" button. This will simulate the execution of the workflow as if it were triggered by the schedule. However, note that the workflow will not run according to its actual scheduled time until that time arrives.

*** ### Complete Workflow Execution Statuses A status indicator at the top of the editor provides real-time feedback on the Workflow’s execution. Including total run time, who ran the workflow, the number of completed steps, and details on any failures. When you stop a test run of a workflow, any temporary changes or test data used during the execution will be discarded. The workflow will revert to its last saved version, ensuring that no test modifications persist in the live configuration. This allows you to safely test workflows without affecting the original setup. The table below lists the possible execution statuses of a Workflow

| Workflow Status | Description | Icon | | --------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Completed** | The workflow completed successfully without any errors. |

| | **In Progress** | The workflow is currently running and has not yet finished. |

| | **Failed** | The workflow encountered an error and did not complete. |

*** ### Using Test Parameters from Previous Runs You can use past executions and their parameters to test a workflow. These past executions include both test runs and executions of the published version. Running a test with real inputs from a previous execution helps you identify issues, troubleshoot failures, and refine the workflow for better performance. When testing a draft workflow using input parameters from a past execution, only parameters that match both by name and type to the current input parameters will be used in the test. Any other parameters, which do not match, will be ignored and not included in the test run. Click 'Test parameters' button to open the configuration panel where you can define input values for the test run. Click **Run history**, then select the parameters of a past run execution to test with your current workflow draft.