Published 6 days ago
This template describes a possible approach to handle a pseudo-callback/trigger from an independent, external process (initiated from a workflow) and combine the received input with the workflow execution that is already in progress. This requires the external system to pass through some context information (resumeUrl
), but allows the "primary" workflow execution to continue with BOTH its own (previous-node) context, AND the input received in the "secondary" trigger/process.
The workflow path from the primary trigger
initiates some external, independent process and provides "context" which includes the value of $execution.resumeUrl
. This execution then reaches a Wait
node configured with Resume - On Webhook Call
and stops until a call to resumeUrl
is received.
The external, independent process could be anything like a Telegram conversation, or a web-service as long as:
Secondary Workflow Trigger
, andresumeUrl
associated with the Primary Workflow Execution
The secondary workflow execution
can start with any kind of trigger as long as part of the input can include the resumeUrl
. To combine / rejoin the primary workflow execution
, this execution passes along whatever it receives from its trigger input to the resume-webhook endpoint on the Wait
node.
Set
nodes marked Update Me have embedded references to the workflow IDs in the original system. They will need to be CHANGED to make this demo work.Resume Other Workflow Execution
node in the template uses the $env.WEBHOOK_URL
configuration to convert to an internal "localhost" call in a Docker environment. This can be done differently.Independent, External Process
needs to work.