Overview
This node enables interaction with Temporal, a workflow orchestration platform. It allows users to start new workflows, check the status of existing workflows, and test connectivity to a Temporal server. This is useful in automation scenarios where complex, stateful processes need to be managed reliably over time.
Typical use cases include:
- Starting a predefined workflow with specific input data to automate business processes.
- Monitoring the execution status of workflows to trigger subsequent actions or alerts.
- Verifying connection settings to ensure the Temporal server is reachable before running workflows.
For example, you might start a payment processing workflow by providing its ID, type, task queue, and input parameters, then later query its status to see if it completed successfully.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | The unique identifier for the workflow execution. |
| Workflow Type | The type/name of the workflow to execute. |
| Task Queue | The task queue on the Temporal server that will handle the workflow tasks. |
| Input | JSON-formatted input data passed as arguments to the workflow when starting it. |
Output
The node outputs an array of items corresponding to each input item processed:
For Start Workflow operation:
json.result: Contains the result returned by the started workflow execution (usually a run ID or confirmation).
For Get Workflow Status operation:
json.workflowId: The workflow's unique ID.json.runId: The current run ID of the workflow.json.status: The current status name of the workflow execution (e.g., Running, Completed).json.startTime: Timestamp when the workflow started.json.closeTime: Timestamp when the workflow closed (if applicable).
For Test Connection operation:
json.success: Boolean indicating if the connection was successful.json.message: Informational message about the connection test.json.serverAddress: The Temporal server address used.json.namespace: The namespace targeted on the Temporal server.json.timestamp: ISO timestamp of the test.
The node does not output binary data.
Dependencies
- Requires a Temporal server accessible via network.
- Needs credentials including server address, namespace, and optionally TLS certificate/key paths.
- Uses the official Temporal client library to connect and interact with the Temporal server.
- Requires proper configuration of TLS certificates if secure connections are used.
- The node expects the input property "Input" to be valid JSON.
Troubleshooting
- Connection failures: Errors connecting to the Temporal server may occur if the server is down, the address is incorrect, network issues exist, or TLS settings are misconfigured. The error message will suggest verifying these points.
- Invalid JSON input: If the "Input" property contains malformed JSON, the node will throw a parsing error. Ensure the input is valid JSON.
- Workflow not found: When getting workflow status, if the workflow ID does not exist or is incorrect, the node may throw an error.
- Continue on Fail: If enabled, the node will continue processing remaining items even if one fails, returning error messages in the output JSON.