Skip to content

Multiple Webhook 5 - Benchmark Testing Endpoint

A simple webhook endpoint designed for benchmarking and testing purposes. This workflow provides a basic HTTP endpoint that can receive requests and return responses, making it useful for performance testing, load testing, or as a placeholder endpoint during development.

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

This is a straightforward single-node workflow:

  1. Webhook receives request - The workflow listens for incoming HTTP requests at the /multiple-webhook5 endpoint
  2. Response returned - The webhook automatically returns a response to the caller (using n8n's default response behavior)

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 - 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-webhook5

Nodes Used

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

External Services & Credentials Required

None - this workflow operates entirely within n8n without external service dependencies.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input: - HTTP requests of any type (GET, POST, PUT, DELETE, etc.) - Request body, headers, and query parameters are accepted but not processed - No specific data format requirements

Output: - HTTP response with default n8n webhook response - Response includes execution metadata - Status code: 200 (success) or appropriate error codes

Error Handling

This workflow uses n8n's default error handling: - Invalid requests return appropriate HTTP error codes - Workflow execution errors are logged in n8n's execution history - No custom error handling logic is implemented

Known Limitations

  • No data processing or transformation occurs
  • No validation of incoming requests
  • No custom response formatting
  • Limited to basic webhook functionality

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 "Multiple Webhook 1", "Multiple Webhook 2", etc.

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 automatically generated

  3. Test the endpoint 

    1
    curl -X GET https://your-n8n-instance.com/webhook/multiple-webhook5

  4. Monitor executions

    • Check the Executions tab to see incoming requests
    • Review logs for any issues

Note: No additional configuration is required as this is a minimal webhook setup designed for benchmarking purposes.