[BENCHMARK] Multiple Webhook 2¶
A simple webhook endpoint designed for benchmarking and testing purposes. This workflow creates a single HTTP endpoint that can receive and respond to incoming requests, making it ideal for performance testing, load testing, or basic webhook functionality validation.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
This workflow appears to be part of a benchmarking suite, providing a minimal webhook endpoint for testing HTTP request handling capabilities.
How It Works¶
- Webhook Activation: The workflow starts when an HTTP request is made to the designated webhook URL
- Request Processing: The webhook node receives the incoming request and processes it
- Response: The workflow returns a response to the caller (using the default response mode)
This is a minimal implementation with just a single node, making it perfect for baseline performance measurements.
Workflow Diagram¶
graph TD
A[HTTP Request] --> B[Webhook Node]
B --> C[Response]
style B fill:#e1f5fe
style A fill:#f3e5f5
style C fill:#e8f5e8
Trigger¶
- Type: Webhook (HTTP endpoint)
- Path:
/multiple-webhook2 - Methods: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.)
- Authentication: None configured
The webhook URL will be: https://your-n8n-instance.com/webhook/multiple-webhook2
Nodes Used¶
| Node Type | Node Name | Purpose |
|---|---|---|
| Webhook | Webhook | Receives HTTP requests and triggers workflow execution |
External Services & Credentials Required¶
None - This workflow operates independently without requiring external services or credentials.
Environment Variables¶
No environment variables are required for this workflow.
Data Flow¶
Input: - HTTP request to the webhook endpoint - Request can include any headers, query parameters, or body content - All standard HTTP methods are supported
Output: - HTTP response (content depends on the request and n8n's default response handling) - Response includes standard HTTP status codes and headers
Data Processing: - Minimal processing - the webhook node simply receives and acknowledges requests - No data transformation or manipulation occurs
Error Handling¶
No explicit error handling is implemented in this workflow. Error responses will use n8n's default error handling: - Invalid requests return appropriate HTTP error codes - Server errors return 500-level status codes - Network issues are handled at the n8n platform level
Known Limitations¶
- No request validation or filtering
- No custom response formatting
- No logging or monitoring beyond n8n's built-in execution logs
- Single endpoint only (no routing or path parameters)
Related Workflows¶
Based on the naming convention, this appears to be part of a series of benchmark workflows. Look for related workflows with similar naming patterns like:
- [BENCHMARK] Multiple Webhook 1
- [BENCHMARK] Multiple Webhook 3
Setup Instructions¶
-
Import Workflow:
- Copy the workflow JSON
- In n8n, go to Workflows → Import from JSON
- Paste the JSON and save
-
Activate Workflow:
- Open the imported workflow
- Click the "Active" toggle to enable the webhook
-
Test the Endpoint:
1 2 3
curl -X POST https://your-n8n-instance.com/webhook/multiple-webhook2 \ -H "Content-Type: application/json" \ -d '{"test": "data"}' -
Monitor Execution:
- Check the Executions tab to see incoming requests
- Review logs for performance metrics during benchmarking
Note: Replace your-n8n-instance.com with your actual n8n instance URL. The webhook will be immediately available once the workflow is activated.