--- title: "Test workflows | Lansweeper Platform" slug: "test-workflows" description: "Learn how to test your Workflow in Flow Builder, view test results, and debug issues effectively with our comprehensive guide." tags: ["Lansweeper Platform", "Flow Builder", "Automation", "Build workflows"] status: "update" updated: 2026-10-19T19:04:29Z published: 2026-10-19T19:04:29Z canonical: "docs.lansweeper.com/test-workflows" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt > Use this file to discover all available pages before exploring further. # Test Workflows Plan availability: Available on Pro and Enterprise plans As you build your Workflow, you can test it to ensure that it works as expected. This article describes how to test your Workflow within the Flow Builder. ## The test runner drawer The test runner drawer appears at the bottom of the Flow Builder when you click **Test** or **Run history**. Within the drawer, you can see the results of test runs of your Workflow (both runs triggered by the **Test** button and runs triggered by a [webhook request](/docs/trigger-workflows#what-is-a-webhook)). ## Running a test of your Workflow To run a test of your Workflow, click the **Test** button at the bottom of the Flow Builder. This will open the test runner drawer and start a new test run of your Workflow. You can also click the **Run history** button to open the test runner drawer without starting a new test run. ### Running a test with a webhook request If your Workflow is triggered by a webhook request, you can run a test with a test payload in one of two ways: 1. Click the **trigger** of your Workflow and then open the **Test** tab. Click the **Trigger Payload** button and specify a payload. The next time you click the **Run** button, the test run will use that payload as the webhook request. ![Trigger Payload](https://cdn.document360.io/21d5935c-1b73-44fa-bf5a-a8b0f5c67f25/Images/Documentation/trigger-payload.png?sv=2026-02-06&spr=https&st=2026-11-07T02%3A15%3A37Z&se=2026-11-07T03%3A15%3A37Z&sr=c&sp=r&sig=YkuUuCPyEY31GAHzbt9r4a0NXHVA8%2B5RR15gQvUStCY%3D) 2. In your trigger's **Test** tab, expand **Webhook URLs**. Your **Test URL** represents the webhook URL of your test Workflow (the Workflow you see in the Flow Builder) and **Live URL** represents the URL of your workflow when you [enable](/docs/enable-workflows) it. Use a tool like [Postman](https://www.postman.com/) or [cURL](https://curl.se/) to send a POST request to your URL with a test payload. ## Test run results and logs You can observe the results of your test runs in the test runner drawer. Select a test run and then select a step of your Workflow to see the results of that step. You can also see the logs for each step, which can help you debug any issues that arise during the test run. ## Replaying test invocations If your Workflow relies on data sent from a third-party service, you can replay a test invocation to simulate the same data being sent again. That way, you don't have to configure the third-party service to send the data again, and you can test how your modified Workflow handles that same payload. Mouse over the test invocation you'd like to replay and click the circular **Replay Test Run** arrow icon that appears. ![Replay Test Run](https://cdn.document360.io/21d5935c-1b73-44fa-bf5a-a8b0f5c67f25/Images/Documentation/replay-test-run.png?sv=2026-02-06&spr=https&st=2026-11-07T02%3A15%3A37Z&se=2026-11-07T03%3A15%3A37Z&sr=c&sp=r&sig=YkuUuCPyEY31GAHzbt9r4a0NXHVA8%2B5RR15gQvUStCY%3D) A paid Lansweeper Platform plan that includes features the Free plan doesn't, such as creating dashboards and exporting views. For what each plan includes, see https://www.lansweeper.com/pricing/. Compare with the Free and Enterprise plans.The highest Lansweeper Platform plan. Some features are available only on Enterprise. For what each plan includes, see https://www.lansweeper.com/pricing/. Compare with the Free and Pro plans.