Axelor icon

Axelor

Consume Axelor API

Actions16

REST & Advances Service → Action Service

AI-generated

Overview

The Axelor node for n8n, when configured with the Resource REST & Advances Service and Operation Action Service, allows you to trigger custom actions on the Axelor platform via its REST API. This is particularly useful for invoking server-side business logic, workflows, or any custom action defined in your Axelor instance.

Common scenarios:

  • Automating business processes by triggering Axelor actions from n8n workflows.
  • Integrating Axelor with other systems, where a specific action (like validation, calculation, or workflow step) needs to be executed programmatically.
  • Batch processing or mass-updating records using Axelor's action services.

Practical example:
Suppose you have a custom action in Axelor that approves an invoice. You can use this node to call that action automatically whenever a new invoice is created in another system, streamlining your approval process.

Properties

Name Type Meaning
Content JSON json The full request body as JSON. For Action Service, you must include the model domain in this data field. This property defines all parameters required by the Axelor action being called. See Axelor documentation.

Output

  • The output will be a JSON array containing the response(s) from the Axelor /ws/action endpoint.
  • The structure of each item in the output array depends on the specific action invoked and the Axelor API's response format.
  • Typically, it includes fields such as status, data, message, or any custom fields returned by your action.

Example output:

[
  {
    "status": 0,
    "data": { /* ...action-specific data... */ },
    "message": "Action executed successfully"
  }
]

Dependencies

  • External Service: Requires access to an Axelor instance with the relevant action service(s) configured.
  • Authentication: Needs valid Axelor API credentials set up in n8n under the credential type axelorApi.
  • n8n Configuration: No special environment variables are needed beyond standard credential setup.

Troubleshooting

Common issues:

  • Missing Model Domain: If the model domain is not included in the Content JSON, the action may fail or return an error, as it's required but not always documented in Axelor's official docs.
  • Malformed JSON: If the Content JSON is not valid JSON, the node will throw a parsing error.
  • Permission Denied: If the provided credentials lack permission to execute the specified action, you'll receive an authorization error from Axelor.
  • Action Not Found: If the action name or parameters do not match what's defined in Axelor, the API will return an error indicating the action is unknown or invalid.

Error messages and resolutions:

  • "Unexpected token ... in JSON": Check your Content JSON for syntax errors.
  • "Missing required parameter: domain": Ensure the model domain is present in your JSON payload.
  • "401 Unauthorized": Verify your Axelor API credentials in n8n.
  • "Action not found": Double-check the action name and parameters against your Axelor configuration.

Links and References

Discussion