[BENCHMARK] Multiple Webhook 10

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 as a basic integration point for external systems.

Purpose

No business context provided yet — add a context.md to enrich this documentation.

How It Works

This workflow operates as a straightforward HTTP endpoint:

1. Incoming Request: The workflow listens for HTTP requests at the /multiple-webhook10 endpoint
2. Request Processing: When a request is received, the webhook node captures the incoming data
3. Response: The workflow returns a response to the caller (using the last node response mode)

The workflow is intentionally minimal, containing only a single webhook node, which makes it ideal for benchmarking scenarios where you want to measure baseline performance without additional processing overhead.

Mermaid Diagram

graph TD
    A[Webhook Trigger<br/>Path: /multiple-webhook10] --> B[Response Sent]

Trigger

Webhook Trigger - Type: HTTP Webhook - Path: /multiple-webhook10 - Methods: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.) - Authentication: None configured

The webhook is accessible at: https://your-n8n-instance.com/webhook/multiple-webhook10

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 service connections or credentials.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input: - HTTP request with any payload (JSON, form data, query parameters, etc.) - Request headers and metadata

Output: - HTTP response (content depends on the incoming request and n8n's default response behavior) - Response includes standard HTTP status codes and headers

Data Processing: - No data transformation occurs in this workflow - Input data is passed through unchanged

Error Handling

This workflow uses n8n's default error handling: - Invalid requests return standard HTTP error responses - Network issues are handled at the n8n platform level - No custom error handling logic is implemented

Known Limitations

• Single endpoint only - no routing or path parameters
• No authentication or rate limiting
• No data validation or transformation
• Minimal logging capabilities
• Response format depends on n8n's default webhook response behavior

Related Workflows

No related workflows specified in the current context.

Setup Instructions

1. Import Workflow

   # Import the workflow JSON into your n8n instance
   # Either through the UI or API
   

2. Activate Workflow

   • Open the workflow in n8n editor
   • Click the "Active" toggle to enable the webhook
   • The workflow will automatically generate a webhook URL

3. Test the Endpoint

   # Test with a simple GET request
   curl https://your-n8n-instance.com/webhook/multiple-webhook10
   
   # Test with POST data
   curl -X POST https://your-n8n-instance.com/webhook/multiple-webhook10 \
        -H "Content-Type: application/json" \
        -d '{"test": "data"}'
   

4. Verify Operation

   • Check the workflow execution history in n8n
   • Confirm responses are returned as expected
   • Monitor for any error logs

Note: This workflow is marked as a benchmark workflow, suggesting it's intended for performance testing rather than production use. Consider the load and usage patterns when deploying.