Overview
This node interacts with Camunda Cloud, a workflow and decision automation platform. Specifically, for the Job resource with the Complete operation, it allows you to complete an already activated BPMN job by providing its unique identifier (job key) and optionally passing variables back to the workflow engine.
Typical use cases include:
- Completing asynchronous service tasks in a BPMN process after external processing is done.
- Passing updated or new process variables back to the workflow instance upon job completion.
- Integrating external systems or APIs that perform work triggered by Camunda jobs and then signaling completion.
For example, if a workflow has a service task waiting for an external system to finish some processing, this node can be used to mark that job as completed and send any resulting data back into the workflow.
Properties
| Name | Meaning |
|---|---|
| Job Key | Identifier of an already activated BPMN job to complete, e.g., obtained from a previous node. |
| Variables (JSON) | Optional JSON object containing variables to pass back to Camunda Cloud when completing the job. |
Output
The node outputs a JSON array where each item corresponds to one input item processed. For the Complete operation on a job, the output for each item is:
{
"success": true
}
indicating the job was successfully completed.
No binary data is output by this node.
Dependencies
- Requires connection to a Camunda Cloud environment.
- Needs an API authentication credential configured in n8n to authorize requests to Camunda Cloud.
- Uses the Zeebe client library internally to communicate with Camunda Cloud's workflow engine.
Troubleshooting
- Invalid Job Key: If the provided job key does not correspond to an active job, the node will throw an error. Verify the job key is correct and that the job is currently activated.
- Malformed Variables JSON: If the "Variables (JSON)" property contains invalid JSON, parsing will fail. Ensure the JSON syntax is correct.
- Authentication Errors: If the API credentials are missing or incorrect, the node will fail to connect. Check your Camunda Cloud API credentials configuration.
- Network Issues: Connectivity problems to Camunda Cloud will cause errors. Confirm network access and endpoint availability.
If continueOnFail is enabled, the node will return error messages in the output JSON instead of stopping execution.