Actions39
- Account Actions
- Client Actions
- Document Actions
- Product Actions
- Receipt Actions
- Store Actions
- Supplier Actions
Store → Get All Stores
AI-generatedOverview
This node integrates with the Vendus API, a platform for invoicing and business management. Specifically, the "Get All Stores" operation under the "Store" resource retrieves a list of all stores configured in the Vendus account.
Common scenarios where this node is useful include:
- Synchronizing store data from Vendus into other systems or databases.
- Automating workflows that depend on store information, such as inventory updates or sales reporting.
- Fetching store details to dynamically populate options in subsequent workflow steps.
Example: A user wants to pull all their store locations from Vendus to generate a consolidated sales report across multiple outlets.
Properties
| Name | Meaning |
|---|---|
| Options | Collection of optional settings: |
| - Enable Debug Logging | Boolean flag to enable detailed debug logging for troubleshooting API calls. When enabled, the node logs detailed request and response information to help diagnose issues. |
Output
The node outputs an array of JSON objects, each representing a store retrieved from the Vendus API. The structure of each store object corresponds directly to the API's response format, typically including fields like store ID, name/title, and other store-specific details.
If debug logging is enabled, additional log entries are generated internally but do not affect the output structure.
No binary data is output by this operation.
Dependencies
- Requires an API key credential for authenticating with the Vendus API.
- The node expects the base URL of the Vendus API to be configured in the credentials.
- Uses HTTP requests with authentication to communicate with the Vendus API endpoints.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
- If the API endpoint changes or is unavailable, the node will fail to retrieve stores.
Error Messages:
"No routing configuration found for store.getAllStores": Indicates the node does not recognize the requested resource-operation combination; likely a misconfiguration.- Parameter substitution errors if required parameters are missing (not typical for this operation since it has no required parameters).
- HTTP errors returned by the Vendus API, which may include status codes and error messages indicating issues like unauthorized access or rate limiting.
Resolution Tips:
- Verify that the API key credential is correctly set up and has necessary permissions.
- Enable debug logging to get detailed request/response info for diagnosing issues.
- Check network connectivity and Vendus API status.
- Ensure the node parameters are correctly configured.
Links and References
- Vendus Official Website (developer site mentioned in description)
- Vendus API documentation (not provided here, but users should consult official API docs for detailed schema and capabilities)