Skip to content

[BENCHMARK] Multiple Webhook 7

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

  1. Webhook Trigger: The workflow starts when an HTTP request is made to the designated endpoint
  2. Response: The webhook automatically returns a response to the caller (using n8n's default response behavior)

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.

Workflow Diagram

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

Trigger

Webhook Trigger - Path: /multiple-webhook7 - Methods: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.) - Authentication: None configured - Response Mode: Last node response

The webhook can be accessed at: https://your-n8n-instance.com/webhook/multiple-webhook7

Nodes Used

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

External Services & Credentials Required

This workflow does not require any external services or credentials. It operates entirely within n8n using the built-in webhook functionality.

Environment Variables

No environment variables are required for this workflow.

Data Flow

Input: - HTTP request to the webhook endpoint - Request can include any headers, query parameters, or body data - All standard HTTP methods are supported

Output: - HTTP response returned to the caller - Response format depends on n8n's default webhook response behavior - Typically returns a 200 OK status with basic execution information

Error Handling

This workflow does not implement custom error handling. Any errors would be handled by n8n's default webhook error responses: - Invalid requests return appropriate HTTP error codes - Workflow execution errors return 500 Internal Server Error - Timeout errors return 408 Request Timeout

Known Limitations

  • No custom response formatting
  • No request validation or filtering
  • No logging or monitoring beyond n8n's built-in execution logs
  • Single endpoint only (no routing logic)

No related workflows identified from the provided 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

    • Open the imported workflow
    • Click the "Active" toggle to enable it
    • The webhook endpoint will become immediately available

  3. Test the Webhook

    • Note the webhook URL from the Webhook node
    • Send a test request using curl, Postman, or any HTTP client: 
      1
      curl -X GET https://your-n8n-instance.com/webhook/multiple-webhook7

  4. Monitor Execution

    • Check the Executions tab to see incoming requests
    • Review execution logs for debugging if needed

Note: This workflow is marked as a benchmark workflow, suggesting it's intended for performance testing rather than production use. Consider the load and frequency of requests when using it for testing purposes.