Pattern for multiple triggers combined to continue workflow
Overview This template describes a possible approach to handle a pseudo-callback/trigger from an independent, external process (initiated from a workflow) an...
🔌 Nodes & Integrations Used (1)
📖 Implementation & Setup Guide
Overview
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.
Primary Workflow Trigger/Execution 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.
External, Independent Process The external, independent process could be anything like a Telegram conversation, or a web-service as long as: 1. it results in a single execution of the `Secondary Workflow Trigger`, and 2. it can pass through the value of `resumeUrl` associated with the `Primary Workflow Execution`
Secondary Workflow Trigger/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.
Notes * **IMPORTANT**: The workflow ids in the `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.** * Note: The `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. * **ALERT:** This pattern is NOT suitable for a workflow that handles multiple items because the first workflow execution will only be waiting for one callback. * The second workflow (not the second trigger in the first workflow) is just to demonstrate how the `Independent, External Process` needs to work.
⚡ How to import this workflow into n8n:
- Click the Direct Download JSON button above to save
Pattern for multiple triggers combined to continue workflow.json. - Log in to your n8n Cloud or self-hosted n8n instance.
- In your workflow canvas, click the menu in top-right and select Import from File (or paste the JSON directly).
- Configure your credentials (e.g. API keys, database URLs) in the corresponding node settings.
- Click Execute Workflow to test and switch to Active!
Related General Automation Workflows
View All in General Automation →Generate Application Copy
Production-ready n8n automation template for Generate Application Copy built by AhiXLight. Seamlessly connects Execute Workflow Trigger, OpenAI with 4 configured nodes.
2-way sync Google Contacts and Notion
Sync your Google Contacts with your Notion database. You can filter contacts by label or sync all contacts. All contact information is kept in sync between G...
2D Image to 3D Model Automation
Production-ready n8n automation template for 2D Image to 3D Model Automation built by AhiXLight. Seamlessly connects HTTP Request, Google Sheets, Google Drive with 17 configured nodes.
2 way sync assignments completion between Canvas LMS and Notion
Syncs assignments and completion states to and fro between Canvas LMS and a Notion database. Automatically triggers every 2 hours during the schoolday by def...