[BENCHMARK] Multiple Webhook 1¶
A simple webhook endpoint designed for benchmarking and testing purposes. This workflow creates a single HTTP endpoint that can receive incoming requests and return responses, making it useful for performance testing, load testing, or basic webhook functionality validation.
Purpose¶
No business context provided yet — add a context.md to enrich this documentation.
How It Works¶
This workflow operates as a basic webhook receiver:
- Webhook Trigger: The workflow listens for incoming HTTP requests at the
/multiple-webhook1endpoint - Response: Returns the received data back to the caller (since no additional processing nodes are configured)
The workflow is intentionally minimal, containing only a webhook trigger node, which makes it ideal for benchmarking scenarios where you want to measure baseline webhook performance without additional processing overhead.
Mermaid Diagram¶
graph TD
A[Webhook Trigger<br/>Path: /multiple-webhook1] --> B[End<br/>Return Response]
Trigger¶
Webhook Trigger
- Path: /multiple-webhook1
- Method: Accepts all HTTP methods (GET, POST, PUT, DELETE, etc.)
- Response Mode: Returns data from the last node (in this case, the webhook node itself)
The webhook URL will be: 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 execution |
External Services & Credentials Required¶
This workflow does not require any external services or credentials. It operates entirely within n8n using the built-in webhook functionality.
Environment Variables¶
No environment variables are required for this workflow.
Data Flow¶
Input: - HTTP request to the webhook endpoint - Request can include any valid HTTP payload (JSON, form data, query parameters, etc.)
Output: - Returns the received request data back to the caller - Response format depends on the incoming request format
Example Request:
1 2 3 | |
Example Response:
1 2 3 | |
Error Handling¶
This workflow does not implement specific error handling mechanisms. Standard n8n webhook error responses will apply: - Invalid requests will return appropriate HTTP error codes - Server errors will return 500-level status codes
Known Limitations¶
- No data validation or processing is performed on incoming requests
- No authentication or authorization mechanisms are implemented
- Response is limited to echoing back the received data
Related Workflows¶
No related workflows specified in the current context.
Setup Instructions¶
-
Import the Workflow:
- Copy the workflow JSON
- In n8n, go to Workflows → Import from JSON
- Paste the JSON and save
-
Activate the Workflow:
- Click the "Active" toggle to enable the webhook
- The webhook URL will be automatically generated
-
Test the Webhook:
- Use the generated webhook URL:
https://your-n8n-instance.com/webhook/multiple-webhook1 - Send a test request using curl, Postman, or any HTTP client
- Verify you receive the expected response
- Use the generated webhook URL:
-
Benchmarking Usage:
- Use this endpoint for load testing tools
- Monitor n8n performance metrics during testing
- Scale requests as needed for your benchmarking requirements
Note: This workflow is marked as active and ready to receive requests immediately after import.