Bear Brown
← All N8N workflows
Automation & utilitiesHTTP RequestManual TriggerRespond To WebhookEdit FieldsWait

Independent "Async" Process

Configured with HTTP Request, Respond To Webhook, Wait, Webhook. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗13 nodes · MIT
Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerWaitWaitWaitWeb / APIHTTP Request - InitiateIndependent ProcessHTTP RequestWeb / APIHTTP Request - ResumeOther Workflow…HTTP RequestTransformThis Node Can AccessPrimary and SecondaryEdit FieldsTransformSet Primary ExecutionContextEdit FieldsTriggerReceive Input fromExternal, Independent…WebhookWeb / APIRespond to WebhookRespond To WebhookWeb / APISimulate Event thatHits the 2nd…HTTP RequestWaitSimulate some ConsumedService TimeWaitWeb / APIHTTP Request - Get ARandom JokeHTTP RequestTransformDemo "Trigger" CallbackSetupEdit FieldsTriggerWebhookWebhook

Node categories in this workflow

  • Trigger
  • Wait
  • Web / API
  • Transform

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
WaitWaitWaitSee node parameters
HTTP Request - Initiate Independent ProcessWeb / APIHTTP RequestPOST
HTTP Request - Resume Other Workflow ExecutionWeb / APIHTTP RequestPOST
This Node Can Access Primary and SecondaryTransformEdit FieldsSee node parameters
Set Primary Execution ContextTransformEdit FieldsSee node parameters
Receive Input from External, Independent ProcessTriggerWebhookSee node parameters
Respond to WebhookWeb / APIRespond To WebhookSee node parameters
Simulate Event that Hits the 2nd Trigger/FlowWeb / APIHTTP RequestPOST
Simulate some Consumed Service TimeWaitWaitSee node parameters
HTTP Request - Get A Random JokeWeb / APIHTTP RequestSee node parameters
Demo "Trigger" Callback SetupTransformEdit FieldsSee node parameters
WebhookTriggerWebhookSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

Independent "Async" Process

Independent "Async" Process

This 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. For 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.

Only One Item Will Work

Only One Item Will Work

If the previous steps could result in multiple initiations via the Secondary Trigger below, only the first one will resume the workflow. Others will be rejected.

Secondary Trigger From Independent Process

Secondary Trigger From Independent Process

When something runs the workflow through this trigger, it is a completely separate execution. By passing through the resumeUrl from the Primary Execution, it is possible to join back into it via the "webhook callback" to the Wait node.

  • Note: This trigger could be anything that would support input including the resumeUrl, not just a webhook. The Webhook node is just used to demonstrate a separate trigger.
Sticky Note3

These are the nodes that combine the Secondary execution back to the Primary execution via the resumeUrl.

Simulated External Independent Process

Simulated External Independent Process

Cut/Paste these nodes into a separate workflow instance Then activate the trigger Then activate the workflow

Independent "Async" Process

Independent "Async" Process

Purpose and structure

This folder contains the Independent "Async" Process workflow. Its executable nodes use httpRequest, manualTrigger, respondToWebhook, set, wait, webhook. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

When clicking ‘Test workflow’, Receive Input from External, Independent Process, Webhook

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0716_Wait_Webhook_Process_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Primary Trigger/Execution
  • Main Workflow - Keep these together in the same workflow instance
  • Update Me
  • Execute This Node to Test

More in Automation & utilities

1/ Add Your credentials2. Refresh Pipedrive tokens6