Actions27
- Public Administration Actions
- Public Actions
- Public Transactions Actions
- Get Indexes Account
- Post Indexes Account
- Get Indexes Categories
- Post Indexes Categories
- Get Indexes Customer
- Post Indexes Customer
- Get Invoices
- Patch Invoices
- Get Orders
- Post Orders
- Get Payments
- Patch Payments
- Get Indexes Status
- Post Indexes Status
- Get Indexes Tax Rate
- Post Indexes Tax Rate
- Get Indexes Vendor
- Post Indexes Vendor
Overview
This node interacts with the Dokka API to retrieve vendor index data related to public transactions. Specifically, the "Get Indexes Vendor" operation fetches indexed vendor information for a given company identified by its company ID. This can be useful in scenarios where you need to analyze or process vendor-related transaction indexes from Dokka's public transaction data.
Practical examples include:
- Fetching vendor indexes for financial reporting or auditing.
- Integrating vendor transaction data into other systems for reconciliation.
- Automating workflows that require up-to-date vendor index information from Dokka.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka for which to retrieve vendor indexes. |
| X Fields | An optional header field mask to specify which fields should be included in the response. |
Output
The node outputs JSON data containing the vendor indexes associated with the specified company ID. The exact structure depends on the Dokka API response but generally includes indexed vendor details relevant to public transactions.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Dokka API.
- Needs an API authentication token or key configured in the node credentials (referred generically as "an API key credential").
- The base URL for the Dokka API must be set in the node credentials or environment configuration.
Troubleshooting
- Missing or invalid Company ID: Ensure the Company ID is provided and correctly formatted; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network issues: Check connectivity to the Dokka API endpoint.
- Invalid X Fields value: If using the optional X Fields property, ensure it matches expected field masks supported by the API.
Common error messages may include HTTP 401 Unauthorized (authentication failure), 400 Bad Request (invalid parameters), or 404 Not Found (company ID not found). Resolving these typically involves verifying credentials, input values, and API endpoint correctness.
Links and References
- Dokka API Documentation (refer to official Dokka API docs for detailed schema and usage)
- n8n Documentation on HTTP Request Nodes and Credential Setup