AxelorInstall

Overview

The Document Service - File Listing operation in this custom n8n node allows users to retrieve a list of files from the Axelor DMS (Document Management System). This is useful for automating workflows that require access to document metadata, such as syncing file lists, monitoring new uploads, or integrating with other systems for document processing.

Practical examples:

• Fetching all files stored in Axelor DMS for reporting or auditing.
• Triggering downstream processes when new files are detected.
• Integrating Axelor file listings with external storage or document management solutions.

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 relevant to the operation. Not directly used in "File Listing".
Content JSON	json	Body request content. Not required for "File Listing" operation.

Note: For the "File Listing" operation, only the informational notice is shown. The "Domain Models" and "Content JSON" properties are not required or used.

Output

The output is a JSON array containing the list of files retrieved from the Axelor DMS. Each item in the array represents a file and includes its metadata as provided by the Axelor API.

Example output structure:

[
  {
    "id": 123,
    "name": "document.pdf",
    "size": 45678,
    "createdOn": "2024-06-01T12:34:56Z",
    // ...other file metadata fields
  },
  ...
]

The exact fields depend on the Axelor DMS API response.

Dependencies

• External Service: Requires access to an Axelor instance with the DMS 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:

• Invalid credentials: If the API key or credentials are incorrect, the node will fail to connect to Axelor.
• Network errors: Connectivity issues between n8n and Axelor may cause timeouts or failures.
• Permission denied: The user associated with the credentials may lack permission to list files.

Error messages and resolutions:

• "401 Unauthorized": Check and update your Axelor API credentials in n8n.
• "404 Not Found": Ensure the Axelor DMS endpoint is correct and accessible.
• "500 Internal Server Error": There may be an issue with the Axelor server; check server logs or contact your administrator.

Links and References

• Axelor Documentation
• n8n Documentation: Custom Nodes
• Axelor DMS Module