Overview
This node, named "Heliont Contract Teleporter," is designed to transfer ("teleport") a contract along with input data to another workflow within the n8n environment. It enables chaining workflows by passing complex contract objects and associated data seamlessly from one workflow to another.
Common scenarios where this node is beneficial include:
- Modularizing large automation processes by splitting them into smaller workflows and passing contracts between them.
- Reusing contract logic across multiple workflows without duplicating code.
- Coordinating multi-step processes where each step is handled by a different workflow but requires shared contract context.
For example, you might have a contract defining business rules or configurations that need to be applied in several workflows. This node allows sending that contract and relevant input data to a target workflow identified by its ID, optionally waiting for that workflow to complete before continuing.
Properties
| Name | Meaning |
|---|---|
| Target Workflow ID | The ID of the workflow to which the contract and input data will be sent (required). |
| Wait For Completion | Boolean flag indicating whether to wait for the target workflow to finish execution before proceeding. |
Output
This node does not produce any output items (outputs: []). Its purpose is to trigger another workflow by teleporting the contract and input data to it. Therefore, no JSON or binary data is returned from this node itself.
Dependencies
- Requires access to a stored contract object in the global static data memory of the current workflow. If no contract is found, the node throws an error.
- Needs the ID of the target workflow to send the contract and data to.
- No external API keys or services are required.
- The target workflow must be configured to accept and process the incoming contract and input data.
Troubleshooting
Error: "No contract found in memory. Please create a contract before teleporting."
This indicates that the node could not find a contract object in the global static data. Ensure that a contract has been created and stored in the workflow's global static data before using this node.Invalid or missing Target Workflow ID
Make sure the "Target Workflow ID" property is correctly set to the ID of an existing workflow.Waiting for completion issues
If "Wait For Completion" is enabled, ensure the target workflow completes successfully; otherwise, the calling workflow may hang or fail.