Camunda Cloud Trigger icon

Camunda Cloud Trigger

Triggers an n8n workflow from Camunda Cloud

Camunda Cloud Trigger

AI-generated

Overview

The Camunda Cloud Trigger node is designed to initiate n8n workflows in response to tasks from Camunda Cloud (now known as Zeebe). It subscribes to a specific BPMN task type and listens for new jobs. When a job of the specified type becomes available, the node triggers the workflow and provides the job's details as output. This node is particularly useful for integrating business process automation with n8n, enabling seamless orchestration between Camunda Cloud processes and other systems.

Practical examples:

  • Automatically processing user requests or approvals when a BPMN task is reached.
  • Integrating external APIs or services into your Camunda workflows via n8n.
  • Handling human-in-the-loop tasks by triggering n8n workflows for manual review steps.

Properties

Name Type Meaning
Task Type String The BPMN task type to subscribe to. Determines which jobs will trigger this node.
Timeout Number Timeout in seconds before the BPMN task needs to be marked as completed.
Auto Complete Boolean Whether new jobs should automatically be marked as completed. If false, you must complete them manually.

Output

The node outputs a JSON object for each triggered job with the following structure:

{
  "jobKey": "<Zeebe job key>",
  "variables": { /* All variables associated with the job */ }
}
  • jobKey: Unique identifier for the Zeebe job.
  • variables: An object containing all process variables attached to the job.

Dependencies

  • External Service: Requires access to a Camunda Cloud (Zeebe) cluster.
  • Credentials: Needs camundaCloudApi credentials configured in n8n, including:
    • clientId
    • clientSecret
    • clusterId
    • clusterRegion
  • npm Dependency: Uses the zeebe-node package.

Troubleshooting

Common Issues:

  • Missing Credentials:
    Error: "Credentials are mandatory!"
    Solution: Ensure that valid Camunda Cloud API credentials are set up in n8n.

  • Incorrect Task Type:
    If no jobs are being triggered, verify that the "Task Type" matches the one defined in your BPMN model.

  • Timeouts:
    If jobs are not completed within the specified timeout, they may be retried or marked as failed by Camunda Cloud. Adjust the "Timeout" property as needed.

  • Auto Complete Disabled:
    If "Auto Complete" is set to false, you must use another node to explicitly complete the job; otherwise, jobs may remain active and block process execution.

Links and References

Discussion