VendusInstall

Overview

This node integrates with the Vendus API, a platform for invoicing and business management. Specifically, the "Get Document Types" operation under the "Document" resource fetches the list of available document types from Vendus. This is useful when you want to dynamically retrieve and use document type information (such as invoices, credit notes, receipts) in your workflows without hardcoding them.

Practical examples include:

• Automatically populating dropdowns or options in subsequent nodes based on current document types.
• Validating or filtering documents by their type before processing.
• Synchronizing document types between Vendus and other systems.

Properties

Output

The node outputs an array of JSON objects representing document types retrieved from the Vendus API. Each object typically contains fields such as:

• id or value: The unique identifier/code of the document type (e.g., "FT" for Invoice).
• title or name: The human-readable name of the document type (e.g., "Invoice", "Credit Note").

Example output JSON snippet:

[
  {
    "id": "FT",
    "title": "Invoice"
  },
  {
    "id": "FS",
    "title": "Simplified Invoice"
  },
  {
    "id": "FR",
    "title": "Invoice Receipt"
  }
]

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential configured in n8n to authenticate requests to the Vendus API.
• The base URL for the Vendus API must be set in the credentials.
• The node uses HTTP requests with authentication to communicate with Vendus endpoints.

Troubleshooting

• Common issues:

  • Missing or invalid API credentials will cause authentication failures.
  • Network connectivity problems can prevent reaching the Vendus API.
  • If the API endpoint changes or is unavailable, the node will fail to retrieve document types.

• Error messages:

  • "No routing configuration found for Document.Get Document Types": Indicates the node does not recognize the resource-operation pair; ensure correct selection.
  • Parameter substitution errors if required parameters are missing.
  • HTTP errors returned by the Vendus API (e.g., 401 Unauthorized, 404 Not Found).

• Resolutions:

  • Verify that the API key credential is correctly set up and has necessary permissions.
  • Enable debug logging via the "Enable Debug Logging" option to get detailed logs for troubleshooting.
  • Check network access and Vendus API status.
  • Confirm that the resource and operation names are correctly selected in the node.

Links and References

• Vendus API Documentation (as referenced in the node description)
• n8n documentation on HTTP Request Authentication
• General info on Vendus invoicing and business management tools at Pixel Infinito's website