Skip to content

[BENCHMARK] Multiple Webhook 9

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 straightforward webhook receiver:

  1. Webhook Trigger: The workflow listens for incoming HTTP requests at the /multiple-webhook9 endpoint
  2. Response: Returns the received data back to the caller (default behavior for single-node webhook workflows)

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

Workflow Diagram

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

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

Trigger

Webhook Trigger - Path: /multiple-webhook9 - Method: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.) - Authentication: None configured - Response Mode: Last node (returns webhook data)

Nodes Used

Node Type Node Name Purpose
Webhook Webhook Receives HTTP requests and triggers workflow execution

External Services & Credentials Required

This workflow requires no external services or credentials. It operates entirely within the n8n environment using the built-in webhook functionality.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input: - HTTP request data (headers, body, query parameters, etc.) - Request method and path information - Client IP and user agent details

Output: - Returns the complete webhook payload as received - Includes all request metadata and body content - Response format matches the input format

Error Handling

This workflow implements no custom error handling. It relies on n8n's default webhook error responses: - Invalid requests return standard HTTP error codes - Server errors are handled by the n8n runtime - No retry logic or custom error messages are configured

Known Limitations

Since no business context is provided, specific limitations are unknown. General webhook limitations apply: - No request validation or filtering - No authentication or authorization - No request size limits beyond n8n defaults - No custom response formatting

No related workflows identified. This appears to be part of a benchmark series (indicated by the "[BENCHMARK]" prefix and "9" suffix).

Setup Instructions

  1. Import Workflow:

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

  2. Activate Workflow:

    • Click the "Active" toggle to enable the webhook
    • The workflow will immediately start listening for requests

  3. Test the Endpoint: 

    1
2
3
4
    # Replace YOUR_N8N_INSTANCE with your actual n8n URL
curl -X POST https://YOUR_N8N_INSTANCE/webhook/multiple-webhook9 \
  -H "Content-Type: application/json" \
  -d '{"test": "data"}'

  4. Monitor Performance:

    • Use the n8n execution history to track response times
    • Monitor webhook calls in the workflow execution list
    • Check logs for any errors or performance issues

Note: This workflow is ready to use immediately after import and activation. No additional configuration is required.