Heliont Contract Rematerializer icon

Heliont Contract Rematerializer

Rematerialize the contract in a new workflow after teleportation

Overview

This node, named "Heliont Contract Rematerializer," is designed to restore or "rematerialize" a contract payload within a new workflow after it has been teleported (transferred) from another workflow. It is particularly useful in scenarios where data contracts are passed between workflows using a teleportation mechanism, allowing the receiving workflow to reconstruct the original contract and its associated input data for further processing.

A practical example would be a multi-step automation where one workflow sends a contract payload to another via a Teleporter node, and this node then rehydrates that contract so the subsequent workflow can continue processing with the full context of the original contract.

Properties

Name Meaning
Test Handoff (JSON) A JSON object used only in manual mode within the editor to simulate a teleported payload. This allows testing the node without actual teleportation by providing a sample contract handoff payload.

Output

The node produces two outputs:

  1. Output 1: An array of items representing the input data extracted from the handoff payload. Each item contains a json field with the input data cleaned of contract-specific metadata (using a utility function to strip contract details).

  2. Output 2: A single item containing the rematerialized contract under the json.contract field. This represents the restored contract data as received or simulated.

No binary data output is produced by this node.

Dependencies

  • The node depends on receiving a valid handoff payload containing a contract property, typically provided by a preceding Teleporter node.
  • It uses an internal utility function to clean input data of contract metadata.
  • No external services or API keys are required.
  • For manual testing, users must provide valid JSON in the "Test Handoff (JSON)" property.

Troubleshooting

  • Error: "No handoff payload with contract found. Did you use a Teleporter node before this?"

    • Cause: The node did not receive any input data containing a handoff.contract property.
    • Resolution: Ensure that the node is connected downstream of a Teleporter node that provides the expected contract payload. When running manually, provide a valid JSON object simulating the handoff payload in the "Test Handoff (JSON)" property.

  • Error: "Invalid JSON in Test Handoff field"

    • Cause: The JSON entered in the "Test Handoff (JSON)" property is malformed.
    • Resolution: Correct the JSON syntax in the property to ensure it is valid JSON.

  • If the node outputs empty arrays or missing contract data, verify that the input data structure matches the expected format with a handoff object containing a contract and optional input array.

Links and References

  • No external links are referenced in the source code.
  • For more information on teleportation patterns in n8n workflows, consult the official n8n documentation on data passing between workflows.

Discussion