Camunda Cloud icon

Camunda Cloud

Interact with Camunda Cloud

Actions4

Job → Fail

AI-generated

Overview

This node interacts with Camunda Cloud (now known as Zeebe) to manage BPMN workflow jobs. Specifically, for the Job resource and the Fail operation, it allows you to mark an already activated BPMN job as failed in Camunda Cloud. This is useful when a process step in your n8n workflow encounters an error and you want to notify Camunda Cloud that the job could not be completed successfully.

Common scenarios:

  • Handling errors in automated workflows where a BPMN job cannot proceed.
  • Integrating n8n with Camunda Cloud to provide detailed error feedback for failed process steps.
  • Automating failure reporting from external systems back into your BPMN orchestrations.

Practical example:
If your n8n workflow processes data and encounters a validation error, you can use this node to fail the corresponding Camunda Cloud job and provide a custom error message, ensuring the BPMN process is aware of the failure and can react accordingly (e.g., trigger compensating actions or escalate).

Properties

Name Type Meaning
Job Key String Identifier of an already activated BPMN job, e.g., as returned by the Camunda Cloud Trigger node. Required to specify which job to fail.
Error Message String The error message to return to Camunda Cloud, describing why the job failed.

Output

The node outputs a JSON object for each input item processed:

[
  {
    "success": true
  }
]
  • If the operation fails but Continue On Fail is enabled, the output will include an error message:
[
  {
    "error": "Error: <error details>"
  }
]

No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to Camunda Cloud (Zeebe).
  • API Credentials: Needs camundaCloudApi credentials (Client ID, Client Secret, Cluster ID, Cluster Region) configured in n8n.
  • npm Packages: Uses zeebe-node and uuid packages (bundled with the node).

Troubleshooting

Common issues:

  • Invalid Job Key: If the provided Job Key does not correspond to an active job, the node will throw an error.
  • Authentication Errors: Incorrect or missing Camunda Cloud credentials will result in authentication failures.
  • Network Issues: Connectivity problems between n8n and Camunda Cloud may cause timeouts or connection errors.

Common error messages:

  • "Error: <detailed error from Zeebe client>": Indicates a problem with the request (e.g., invalid job key, network issue, or authentication failure).
    Resolution: Double-check the Job Key, ensure credentials are correct, and verify network connectivity.

Links and References

Discussion