Multiple Webhook 1 (Benchmark)¶
A simple webhook endpoint workflow designed for benchmarking and testing purposes. This workflow creates a single HTTP endpoint that can receive incoming requests, making it useful for performance testing, load testing, or as a basic integration point for external systems.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
This appears to be a benchmark or testing workflow based on the naming convention. It provides a basic webhook endpoint that can be used to measure n8n's performance characteristics or serve as a minimal integration point for testing external system connectivity.
How It Works¶
- Webhook Reception: The workflow listens for incoming HTTP requests on the
/multiple-webhook1endpoint - Request Processing: When a request is received, the webhook node captures the incoming data
- Response: The workflow returns a response to the caller (default webhook behavior)
This is a minimal workflow with just one node, making it ideal for baseline performance measurements or simple connectivity tests.
Mermaid Diagram¶
graph TD
A[Webhook Trigger<br/>Path: /multiple-webhook1] --> B[End]
style A fill:#e1f5fe
style B fill:#f3e5f5
Trigger¶
Webhook Trigger
- Path: /multiple-webhook1
- Method: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.)
- Authentication: None configured
- URL Pattern: https://your-n8n-instance.com/webhook/multiple-webhook1
Nodes Used¶
| Node Type | Node Name | Purpose |
|---|---|---|
| Webhook | Webhook | Receives incoming HTTP requests and triggers the workflow |
External Services & Credentials Required¶
None - This workflow operates independently without requiring external service connections or credentials.
Environment Variables¶
No environment variables are required for this workflow.
Data Flow¶
Input: - HTTP request to the webhook endpoint - Request can include headers, query parameters, and body data - All standard HTTP methods are supported
Output: - HTTP response (default webhook response) - Response includes standard n8n webhook response format - Status code and response body depend on execution success
Data Structure:
1 2 3 4 5 6 7 8 | |
Error Handling¶
This workflow uses n8n's default error handling: - HTTP 500: Returned if the workflow execution fails - HTTP 200: Returned on successful execution - No custom error handling is implemented
Known Limitations¶
- Single node workflow provides minimal functionality
- No data processing or transformation capabilities
- No integration with external systems
- Suitable primarily for testing and benchmarking purposes
Related Workflows¶
No related workflows identified from the current context.
Setup Instructions¶
-
Import Workflow
1 2
# Import the workflow JSON into your n8n instance # No additional configuration required -
Activate Workflow
- Open the workflow in n8n editor
- Click the "Active" toggle to enable the webhook
- Note the webhook URL provided by n8n
-
Test the Endpoint
1 2 3 4
# Test with curl curl -X POST https://your-n8n-instance.com/webhook/multiple-webhook1 \ -H "Content-Type: application/json" \ -d '{"test": "data"}' -
Verify Setup
- Check workflow execution history
- Confirm webhook responses are received
- Monitor for any execution errors
Note: This workflow is currently inactive and marked as a backup version. Activate it through the n8n interface to begin receiving webhook requests.