Overview
This node integrates with Temporal workflows, allowing users to start workflows, query running workflows, send signals to workflows, get the status of workflows, and retrieve workflow results. It is useful for automating and managing complex workflow executions in distributed systems. For example, it can start a new workflow with specific input, query a running workflow for its current state, or wait for and fetch the final result of a workflow execution.
Use Case Examples
- Starting a new workflow to process an order with input data.
- Querying a running workflow to check the progress of a task.
- Sending a signal to a workflow to trigger an event or update.
- Getting the final result of a completed workflow for further processing.
Properties
| Name | Meaning |
|---|---|
| Workflow ID | The ID of the workflow to interact with, required for querying, signaling, getting status, or getting results. |
Output
JSON
workflowId- The ID of the workflow involved in the operation.result- The result returned from the workflow, applicable when getting the workflow result.
Dependencies
- Requires connection to a Temporal server with address, namespace, and API key credentials.
Troubleshooting
- Ensure the provided Workflow ID exists and is correct to avoid errors when querying, signaling, or getting results.
- Verify the Temporal server address and API key credentials are correct and accessible.
- JSON input for queryArgs and signalArgs must be valid JSON strings to avoid parsing errors.
- If the workflow is not running or has completed, querying or signaling may fail.
Links
- Temporal Documentation - Official documentation for Temporal workflows and client usage.