Axelor icon

Axelor

Consume Axelor API

Actions16

Document Service → File Upload

AI-generated

Overview

The Document Service - File Upload operation in this n8n node allows you to upload files to the Axelor platform via its API. This is useful for automating document management workflows, such as attaching files to business records, archiving documents, or integrating file uploads into broader business processes.

Practical examples:

  • Automatically uploading signed contracts to a CRM record.
  • Storing scanned invoices in a document management system.
  • Integrating with other n8n nodes to fetch, process, and then upload files to Axelor.

Properties

Name Type Meaning
Work in progress in this part of node. Please do not break everything. notice Informational notice; does not affect execution.
Domain Models resourceLocator Selects the domain model (e.g., type of business object) to which the file may be related.
Content JSON json The body of the request; specify all necessary parameters for the file upload in JSON format.

Output

  • The output is a JSON array containing the response from the Axelor API after attempting the file upload.
  • The structure of each item in the output array depends on the Axelor API's response to the /ws/files/upload endpoint.
  • Typically, this will include metadata about the uploaded file, such as file ID, name, size, and possibly status or error messages.

Example output:

[
  {
    "id": 123,
    "name": "contract.pdf",
    "size": 45678,
    "status": "uploaded"
  }
]

Note: Actual fields depend on the Axelor API.

Dependencies

  • External Service: Requires access to an Axelor instance with the Document Management module enabled.
  • API Credentials: Needs valid axelorApi credentials configured in n8n.
  • n8n Configuration: No special environment variables required beyond standard credential setup.

Troubleshooting

Common issues:

  • Missing or invalid credentials: Ensure that the axelorApi credentials are correctly set up in n8n.
  • Incorrect domain model: If the selected domain model is incorrect or misspelled, the upload may fail or attach to the wrong entity.
  • Malformed Content JSON: If the JSON body is not properly formatted, the node may throw parsing errors or the API may reject the request.

Error messages and resolutions:

  • "Invalid JSON": Check the Content JSON property for syntax errors.
  • "401 Unauthorized": Verify your API credentials.
  • "404 Not Found": Ensure the endpoint URL and domain model are correct.
  • "500 Internal Server Error": May indicate a server-side issue; check Axelor logs or contact support.

Links and References

Discussion