[BENCHMARK] Multiple Webhook 3

A simple webhook endpoint workflow 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 as a basic API endpoint for development and testing scenarios.

Purpose

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

How It Works

This workflow operates as a straightforward HTTP endpoint:

1. Webhook Trigger: The workflow listens for incoming HTTP requests on the /multiple-webhook3 path
2. Response: Returns the received data back to the caller (since no processing nodes are connected)

The workflow is intentionally minimal, containing only a webhook trigger node with no additional processing, making it ideal for benchmarking raw webhook performance.

Workflow Diagram

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

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

Trigger

Webhook Trigger - Path: /multiple-webhook3 - Methods: All HTTP methods accepted (GET, POST, PUT, DELETE, etc.) - Response Mode: Last node (returns the webhook data as received)

The webhook URL will be: https://your-n8n-instance.com/webhook/multiple-webhook3

Nodes Used

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

External Services & Credentials Required

This workflow requires no 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 requests sent to the webhook endpoint - Request body, headers, and query parameters are captured - Supports any content type (JSON, form data, plain text, etc.)

Output: - Returns the complete webhook payload back to the caller - Includes request body, headers, query parameters, and method information - Response format matches n8n's standard webhook response structure

Error Handling

This workflow has no explicit error handling mechanisms. Any errors would be handled by n8n's default webhook error responses: - Invalid requests return standard HTTP error codes - Server errors return 500 status codes - The workflow will log errors to n8n's execution history

Known Limitations

• No data processing or transformation occurs
• No validation of incoming requests
• No rate limiting or security measures implemented
• Responses are limited to n8n's default webhook response format

Related Workflows

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

3. Test the Endpoint:

   # Test with curl
   curl -X POST https://your-n8n-instance.com/webhook/multiple-webhook3 \
     -H "Content-Type: application/json" \
     -d '{"test": "data"}'
   

4. Monitor Executions:

   • Check the Executions tab to see incoming requests
   • Review response times and data flow

Note: This workflow is marked as active and ready to receive requests immediately after import. Ensure your n8n instance is accessible from wherever you plan to send test requests.