Temporal Workflow Node icon

Temporal Workflow Node

Temporal Workflow Node
Join our community

Overview

This node integrates with the Temporal workflow orchestration system, allowing users to start and execute Temporal workflows directly from an n8n automation. It is useful for automating complex, stateful business processes that require reliable execution and coordination over time.

Typical use cases include:

  • Triggering a Temporal workflow with specific input parameters.
  • Passing contextual task IDs into the workflow execution.
  • Merging input parameters with workflow outputs for downstream processing.
  • Managing workflow execution timeouts and task queues via configuration.

For example, you might use this node to start a payment processing workflow in Temporal by providing payment details as input parameters, then handle the workflow result within your n8n automation.

Properties

Name Meaning
Temporal 工作流 (workflow) Select the Temporal workflow to execute. The list is dynamically loaded from the Temporal server.
Temporal执行参数 (args) Input parameters for the Temporal workflow execution. Schema depends on the selected workflow.
追加任务ID到执行参数 (appendTaskId) Boolean flag to append the current task ID to the workflow execution parameters.
追加执行参数到输出 (inputToOutput) Boolean flag to merge the input parameters into the output JSON of the node.
输出字段名 (outputFieldName) Optional field name under which to nest the workflow execution result in the output JSON.

Output

The node outputs JSON data representing the result of the executed Temporal workflow. The structure depends on the workflow's return value:

  • If outputFieldName is set, the output JSON will have a single property with that name containing the workflow result.
  • If inputToOutput is true, the output JSON merges the original input parameters with the workflow result.
  • Otherwise, the output JSON contains only the workflow result.

No binary data output is produced by this node.

Dependencies

  • Requires connection credentials to the Temporal server, including:
    • Client API credentials with address and TLS certificates.
    • Workflow API credentials with authorization headers.
  • Uses the official Temporal client library (@temporalio/client) to connect and start workflows.
  • Requires n8n to be configured with these credentials and network access to the Temporal server.

Troubleshooting

  • Common issues:

    • Failure to load workflows or schemas if credentials are missing or incorrect.
    • JSON parsing errors if the workflow parameter or args are malformed.
    • Connection errors due to invalid TLS certificates or unreachable Temporal server.
    • Workflow execution failures due to invalid input parameters or workflow logic errors.

  • Error messages:

    • Errors during workflow start include context with the generated workflow ID for easier debugging.
    • If continueOnFail is enabled, errors are returned as part of the output JSON instead of stopping execution.

  • Resolutions:

    • Verify all credential fields and ensure proper TLS certificate formats.
    • Validate JSON inputs before running the node.
    • Check Temporal server logs for workflow-specific errors.
    • Use the appendTaskId option carefully to avoid conflicts in input parameters.

Links and References

Discussion