Vendus icon

Vendus

Interact with Vendus API for invoicing and business management. Developed by Pixel Infinito (https://pixel.ao)

Store → Get Store by ID

AI-generated

Overview

This node interacts with the Vendus API, specifically to retrieve detailed information about a store by its ID. It is useful in scenarios where you need to fetch and use store data within an automation workflow, such as integrating store details into invoices, reports, or other business processes.

For example, you might use this node to:

  • Retrieve a specific store's information to include in a sales report.
  • Fetch store details dynamically based on user input or previous workflow steps.
  • Validate store existence before processing transactions related to that store.

Properties

Name Meaning
Store Name or ID The identifier of the store to retrieve. You can select from a list or specify an ID via expression.
Options Additional settings for the request:
  Enable Debug Logging When enabled, provides detailed debug logs for troubleshooting API calls.

Output

The node outputs JSON data representing the store details retrieved from the Vendus API. The structure corresponds directly to the API response for a single store entity, typically including fields like store name, address, contact info, and other metadata.

No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "id": "123",
  "title": "Main Store",
  "address": "123 Example St.",
  "phone": "+123456789",
  "email": "store@example.com"
}

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the Vendus API.
  • The base URL for the API must be set in the credentials.
  • Optional debug logging can be enabled via the node property for troubleshooting.

Troubleshooting

  • Missing or invalid Store ID: If the Store Name or ID parameter is empty or incorrect, the node will throw an error indicating the required parameter is missing or invalid.
  • API authentication errors: Ensure the API key credential is correctly configured and has access rights to the Vendus API.
  • Network or connectivity issues: Check network access to the Vendus API endpoint.
  • Debug logging: Enable the "Enable Debug Logging" option to get detailed logs that help identify request construction issues or API response errors.
  • No routing configuration found: This internal error indicates a misconfiguration in the node parameters; verify that the resource is set to "Store" and operation to "Get Store by ID".

Links and References

Discussion