VendusInstall

Overview

This node interacts with the Vendus API, specifically to retrieve users associated with an account in the "Get Account Users" operation. It is useful for scenarios where you need to programmatically access user information linked to a specific store or account within Vendus, such as managing permissions, auditing user activity, or integrating user data into other workflows.

For example, you might use this node to:

• Fetch all users of a particular store to synchronize them with another system.
• Exclude accountant users from the list when generating reports or notifications.
• Debug and verify which users have access to certain stores.

Properties

Output

The output is a JSON array where each item corresponds to a user retrieved from the Vendus API for the specified account/store. The structure of each JSON object matches the API response for account users, typically including user details such as name, role, email, and other relevant metadata.

No binary data is output by this node.

Dependencies

• Requires an API key credential for Vendus API authentication.
• The node uses the base URL configured in the credentials to make HTTP requests.
• The node depends on the Vendus API being accessible and the authenticated user having permission to query account users.
• Optional: Enabling debug logging requires that the node's logger is available and properly configured.

Troubleshooting

• Common Issues:

  • Missing or invalid API credentials will cause authentication failures.
  • Specifying an invalid or non-existent store ID may result in empty responses or errors.
  • Network connectivity issues can prevent successful API calls.
  • If the "Exclude Accountants" option is enabled but no users are returned, verify if accountants exist in the selected store.

• Error Messages:

  • No routing configuration found for account.getAccountUsers: Indicates a misconfiguration or unsupported operation; ensure the resource and operation names are correct.
  • Parameter-related errors like Parameter 'storeId' is required but not provided occur if mandatory parameters are missing.
  • HTTP errors from the Vendus API (e.g., 401 Unauthorized, 404 Not Found) indicate credential or resource issues.

• Resolutions:

  • Verify API credentials and permissions.
  • Confirm the store ID or name is valid and accessible.
  • Enable debug logging to get detailed request/response info for diagnosing issues.
  • Use expressions carefully to ensure parameters resolve correctly.

Links and References

• Vendus API Documentation (as referenced in the node description)
• n8n Expressions Documentation
• General n8n HTTP Request Node documentation for understanding API call mechanics.