Overview
This node acts as a trigger for n8n workflows based on tasks from Camunda, a workflow and decision automation platform. It listens for new jobs of a specified task type in a Camunda BPMN process and triggers the workflow when such jobs appear. This is useful for automating processes that depend on external BPMN tasks, enabling seamless integration between Camunda and n8n.
Common scenarios include:
- Automatically starting an n8n workflow when a specific BPMN task becomes available.
- Processing data from Camunda tasks and performing subsequent actions in n8n.
- Coordinating complex workflows by bridging Camunda's process engine with other systems via n8n.
Example: Triggering an n8n workflow whenever a "paymentProcessing" task appears in Camunda, allowing automated handling of payment steps outside Camunda.
Properties
| Name | Meaning |
|---|---|
| Task Type | The specific Camunda BPMN task type to subscribe to and listen for. |
| Timeout | Time in seconds before the BPMN task should be marked as completed if not handled earlier. |
| Auto Complete | Whether the node should automatically mark new jobs as completed upon receiving them (true), or require explicit completion through another node (false). |
Output
The node outputs JSON data representing the received Camunda job when triggered. The output JSON contains:
jobKey: A unique identifier for the Camunda job.variables: An object containing all variables associated with the job.
If "Auto Complete" is enabled, the job is automatically marked as completed after emitting the data. Otherwise, the job remains active until explicitly completed by another node.
No binary data output is produced by this node.
Dependencies
- Requires connection to a Camunda Cloud instance using an API key credential (configured in n8n).
- Uses the Zeebe Node client library internally to interact with Camunda's workflow engine.
- Proper configuration of the Camunda API credentials in n8n is necessary for authentication and communication.
Troubleshooting
Common issues:
- Incorrect or missing API credentials will prevent connection to Camunda.
- Specifying a non-existent or misspelled task type will result in no triggers firing.
- Network connectivity problems can cause failures in subscribing to tasks.
Error messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials.
- Timeout-related errors may occur if the timeout value is too low or network latency is high; consider increasing the timeout.
- If no jobs are received, check that the Camunda process is correctly publishing tasks of the subscribed type.