Skip to content

[BENCHMARK] Multiple Webhook 10

A simple benchmark workflow that provides a single webhook endpoint for testing HTTP request handling and response performance. This workflow serves as a minimal test case for measuring webhook response times and throughput.

Purpose

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

This workflow appears to be designed for benchmarking purposes, specifically testing webhook performance with multiple concurrent requests. It provides a basic HTTP endpoint that can be used to measure response times, throughput, and system performance under load.

How It Works

This workflow operates as a simple HTTP endpoint:

  1. Webhook Trigger: The workflow listens for incoming HTTP requests on the /multiple-webhook10 path
  2. Response: Returns the received data back to the caller (default webhook behavior)

The workflow is intentionally minimal to provide accurate benchmarking results without additional processing overhead.

Workflow Diagram

graph TD
    A[HTTP Request] --> B[Webhook Trigger]
    B --> C[Return Response]

Trigger

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

Nodes Used

Node Type Node Name Purpose
Webhook Webhook Receives HTTP requests and returns responses for benchmarking

External Services & Credentials Required

No external services or credentials are required for this workflow.

Environment Variables

No environment variables are used in this workflow.

Data Flow

Input: - HTTP requests sent to the webhook endpoint - Any request body, headers, and query parameters

Output: - HTTP response containing the original request data - Response includes request body, headers, query parameters, and metadata

Data Format: The webhook accepts any content type and returns JSON by default.

Error Handling

No explicit error handling is implemented in this workflow. The webhook node will handle basic HTTP errors automatically: - Returns appropriate HTTP status codes for malformed requests - Handles connection timeouts based on n8n's default settings

Known Limitations

  • No authentication or rate limiting implemented
  • No request validation or sanitization
  • Limited to n8n's default webhook timeout settings
  • No logging or monitoring of request patterns

No related workflows specified in the context.

Setup Instructions

  1. Import the Workflow:

    • Copy the workflow JSON
    • In n8n, go to Workflows → Import from JSON
    • Paste the JSON and save

  2. Activate the Workflow:

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

  3. Test the Endpoint:

    • Note the webhook URL provided by n8n
    • Send test requests to: https://your-n8n-instance.com/webhook/multiple-webhook10
    • Verify responses are returned correctly

  4. Benchmarking Setup:

    • Use tools like Apache Bench, wrk, or curl for load testing
    • Monitor response times and throughput
    • Scale concurrent requests to test performance limits

Example Test Request: 

1
2
3
curl -X POST https://your-n8n-instance.com/webhook/multiple-webhook10 \
  -H "Content-Type: application/json" \
  -d '{"test": "benchmark data"}'