VendusInstall

Overview

The "Get All Suppliers" operation of the Vendus node retrieves a list of all suppliers from the Vendus API. This node is useful for businesses that manage supplier information and want to automate workflows involving supplier data, such as syncing supplier lists with other systems, generating reports, or triggering actions based on supplier details.

Practical examples include:

• Automatically fetching updated supplier lists to populate dropdowns in other applications.
• Integrating supplier data into inventory or purchasing workflows.
• Monitoring supplier changes or additions for compliance or auditing purposes.

Properties

Output

The node outputs an array of JSON objects, each representing a supplier retrieved from the Vendus API. Each JSON object contains the supplier's data fields as returned by the API, typically including identifiers, names, fiscal IDs, and other relevant supplier details.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "id": 123,
    "name": "Supplier A",
    "fiscal_id": "XYZ123456",
    ...
  },
  {
    "id": 456,
    "name": "Supplier B",
    "fiscal_id": "ABC789012",
    ...
  }
]

Dependencies

• Requires an API key credential configured in n8n to authenticate requests to the Vendus API.
• The node uses the base URL provided in the credentials configuration to make HTTP GET requests to the /suppliers endpoint.
• Optional debug logging depends on the node's internal logger.

Troubleshooting

• Common Issues:

  • Missing or invalid API credentials will cause authentication failures.
  • Network connectivity issues can prevent successful API calls.
  • If the API response structure changes, the node may not parse supplier data correctly.

• Error Messages:

  • "No routing configuration found for supplier.getAll": Indicates the operation or resource is not properly defined; ensure correct resource and operation selection.
  • Parameter substitution errors if required parameters are missing (not typical for this operation since it has no required parameters).
  • HTTP errors from the API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or endpoint issues.

• Resolutions:

  • Verify API credentials and permissions.
  • Check network access to the Vendus API.
  • Enable debug logging via the "Options" property to get detailed logs for troubleshooting.

Links and References

• Vendus API Documentation (as referenced in the node description)
• n8n documentation on HTTP Request Authentication