Pulse has two levels of testing: you can test the full workflow end-to-end, or test individual nodes in isolation. Both use real data so you can verify your logic before activating the workflow.Documentation Index
Fetch the complete documentation index at: https://knowledge.goautonomous.io/llms.txt
Use this file to discover all available pages before exploring further.
Test the full workflow
Click Test Workflow
Click the Test Workflow button at the bottom of the canvas. The workflow enters a listening state — indicated by a spinner — and waits for an incoming event.
Send a request to the test URL
Open the webhook node to find the Test URL. Send a POST request to this URL with your test payload. You can use any API testing tool (Postman, curl, etc.) or trigger it from the system that would normally send events to the workflow.
| Status | Meaning |
|---|---|
| Success | The workflow (or node) completed without errors |
| Error | Something went wrong — check the node’s output viewer for details |
| Started | The workflow was triggered but hasn’t completed yet |
Test individual nodes
Each node can also be tested on its own without running the full workflow. This is useful for debugging a specific step. Open any node by clicking it, then click the Test button inside the node panel. The node runs against the current input data shown in the input viewer and displays the output. For the webhook node specifically, use the Listen for Event button to put that node into listening mode independently — useful for capturing a live payload to inspect before building the rest of the workflow.Test URL vs. Production URL
The webhook node has two separate URLs:- Test URL — active only when the workflow is in testing mode. Use this during development. Events sent here are processed but do not affect live data.
- Production URL — the live endpoint used when the workflow is active. Events sent here are processed by the published workflow.
Tips for effective testing
- Build incrementally — test after adding each node rather than building the entire workflow first. This makes it easier to isolate where issues occur.
- Check input/output at every node — the input and output viewers on each node show exactly what data is entering and leaving. Use these to trace unexpected values.
- Use a real payload — testing with data that closely resembles actual requests gives the most accurate results, especially for switch node conditions.
- Verify switch routes — after testing a switch node, confirm that data followed the intended route by checking which output connection is highlighted.