Skip to content

Webhook Execution Test

A simple n8n workflow that demonstrates webhook execution timing by introducing sequential delays before responding to incoming HTTP requests. This workflow is useful for testing webhook timeouts, monitoring execution duration, and validating that external systems can handle delayed responses.

Purpose

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

How It Works

  1. Webhook receives request: An HTTP request is made to the /exec-test endpoint
  2. Sequential delays: The workflow introduces three consecutive 7-second delays (21 seconds total)
  3. Response sent: After all delays complete, the workflow responds with all incoming data

The workflow is designed to test how external systems handle delayed webhook responses and can be used to validate timeout configurations.

Workflow Diagram

graph TD
    A[Webhook] --> B[Wait 1<br/>7 seconds]
    B --> C[Wait 2<br/>7 seconds]
    C --> D[Wait 3<br/>7 seconds]
    D --> E[Respond to Webhook]

Trigger

  • Type: Webhook (HTTP)
  • Path: /exec-test
  • Method: Any HTTP method accepted
  • Response Mode: Uses response node (waits for workflow completion before responding)

Nodes Used

Node Type Node Name Purpose
Webhook Webhook Receives incoming HTTP requests on /exec-test path
Wait Wait 1 Introduces 7-second delay
Wait Wait 2 Introduces second 7-second delay
Wait Wait 3 Introduces third 7-second delay
Respond to Webhook Respond to Webhook Sends response back to webhook caller with all incoming data

External Services & Credentials Required

No external services or credentials are required for this workflow.

Environment Variables

No environment variables are used in this workflow.

Data Flow

Input: Any HTTP request data sent to the webhook endpoint Processing: Data passes through unchanged during the delay sequence Output: All original incoming data is returned in the webhook response after a 21-second delay

The workflow preserves all incoming request data (headers, body, query parameters) and returns it unchanged after the processing delays.

Error Handling

This workflow does not implement explicit error handling. If any wait node fails, the workflow will stop and no response will be sent to the webhook caller, potentially causing a timeout on the client side.

Known Limitations

  • Total execution time is fixed at 21 seconds (3 × 7 seconds)
  • No error handling for failed wait operations
  • Client systems must be configured to handle responses that take longer than 21 seconds
  • No validation of incoming webhook data

No related workflows specified in the current context.

Setup Instructions

  1. Import the workflow: Copy the workflow JSON and import it into your n8n instance

  2. Activate the workflow: Ensure the workflow is set to "Active" status

  3. Test the webhook:

    • Note the webhook URL provided by n8n (typically https://your-n8n-instance/webhook/exec-test)
    • Send a test HTTP request to the endpoint
    • Verify the response is received after approximately 21 seconds

  4. Configure client timeouts: Ensure any systems calling this webhook are configured with timeouts greater than 25 seconds to account for processing delays

  5. Monitor execution: Use n8n's execution log to verify the workflow completes successfully and timing is as expected

No additional configuration or credentials are required for this workflow to function.