0716 Wait Webhook Process Webhook

Complex

High

Nodes

Complex

Trigger

High

Complexity

7/22/2025

Added

Workflow Overview

Total Nodes

Node Types

sticky Note

Sticky Note8, Sticky Note, Sticky Note1, Sticky Note2, Sticky Note3, Sticky Note4, Sticky Note5, Sticky Note6, Sticky Note7, Sticky Note9

10 nodes

manual Trigger

When clicking ‘Test workflow’

1 node

wait

Wait, Simulate some Consumed Service Time

2 nodes

http Request

HTTP Request - Initiate Independent Process, HTTP Request - Resume Other Workflow Execution, Simulate Event that Hits the 2nd Trigger/Flow, HTTP Request - Get A Random Joke

4 nodes

set

This Node Can Access Primary and Secondary, Set Primary Execution Context, Demo "Trigger" Callback Setup

3 nodes

webhook

Receive Input from External, Independent Process, Webhook

2 nodes

respond To Webhook

Respond to Webhook

1 node

Workflow JSON

14.88 KB

{
  "meta": {
    "instanceId": "37c9b6d3ee04c3e15f526d799209783b3fa8da2950c0e8241dc8ad516d7eb4df"
  },
  "name": "0716 Wait Webhook Process Webhook",
  "nodes": [
    {
      "id": "ba9d786a-0698-4306-adba-40c928c1a340",
      "name": "Sticky Note8",
      "type": "n8n-nodes-base.stickyNote",
      "position": [
        840,
        1100
      ],
      "parameters": {
        "width": 718.7339166606896,
        "height": 141.0983289105648,
        "content": "## Independent \"Async\" Process\nThis could be anything that eventually triggers another workflow and passes through something (e.g. resumeUrl) that identifies the original workflow execution that needs to be joined.\nFor instance, this could be a Telegram conversation where the trigger is watching for a message containing a \"reply\" to something that was originally sent out via Telegram."
      },
      "typeVersion": 1
    },
    {
      "id": "d90e6fa4-2f88-4446-8522-e3ae7b1334d2",
      "name": "When clicking ‘Test workflow...

Showing first 1000 characters. Click "Expand" to view the full JSON.