Skip to content

[BENCHMARK] Multiple Webhook 5

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.

This workflow appears to be part of a benchmarking suite, likely used to test webhook performance, response times, or system load handling capabilities.

How It Works

  1. The workflow starts when an HTTP request is received at the webhook endpoint
  2. The webhook processes the incoming request and automatically returns a response
  3. Since this is configured as a single-node workflow, the response is generated directly from the webhook node

Workflow Diagram

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

    style B fill:#e1f5fe
    style A fill:#f3e5f5
    style C fill:#e8f5e8

Trigger

Webhook Trigger - Path: /multiple-webhook5 - Method: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.) - Response Mode: Last node response

The webhook listens for incoming HTTP requests at the specified path and triggers the workflow execution immediately upon receiving a request.

Nodes Used

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

External Services & Credentials Required

This workflow does not require any external services or credentials. It operates as a standalone webhook endpoint.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input: - HTTP request (any method) to the webhook endpoint - Request headers, body, query parameters, and other HTTP data are automatically captured

Output: - HTTP response generated by the webhook node - Response includes standard HTTP status codes and any data processed by the workflow

Error Handling

This workflow does not implement custom error handling. It relies on n8n's default error handling mechanisms: - Invalid requests return standard HTTP error responses - Workflow execution errors are handled by n8n's built-in error management

Known Limitations

  • Single-node workflow provides minimal processing capabilities
  • No data transformation or business logic implementation
  • Limited to basic webhook functionality for benchmarking purposes

Based on the naming convention, this appears to be part of a series of benchmark workflows. There may be related workflows named: - [BENCHMARK] Multiple Webhook 1-4 - Other benchmark workflows in the same testing suite

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 webhook URL will be generated automatically

  3. Test the Webhook

    • Note the webhook URL provided by n8n (typically: https://your-n8n-instance.com/webhook/multiple-webhook5)
    • Send test requests using curl, Postman, or any HTTP client
    • Verify responses are received as expected

  4. Benchmarking Setup

    • Use load testing tools (Apache Bench, JMeter, etc.) to send multiple requests
    • Monitor response times and throughput
    • Adjust concurrent requests to test system limits

Example Test Request: 

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