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 categories of indexes related to public transactions for a specified company. It is useful when you want to fetch categorized index data from Dokka’s public transaction records, which can be used for financial analysis, reporting, or integration into other workflows.
A practical example would be automating the retrieval of index categories for a company to update dashboards or trigger alerts based on specific financial categories.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka for which the index categories are fetched. This is required. |
| X Fields | An optional header field mask that allows specifying particular fields to include in the response, optimizing data retrieval. |
Output
The node outputs JSON data containing the categories of indexes associated with the specified company’s public transactions. The structure typically includes category identifiers, names, and possibly additional metadata depending on the API response.
No binary data output is involved.
Dependencies
- Requires an active connection to the Dokka API.
- Needs an API authentication token configured in the node credentials.
- 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 correctly provided; otherwise, the API will return an error or empty results.
- Authentication errors: Verify that the API key or token is valid and has sufficient permissions.
- Network issues: Check connectivity to the Dokka API endpoint.
- Invalid X Fields value: If using the optional fields mask, ensure it matches expected API field names to avoid malformed requests.
Links and References
- Dokka API documentation (refer to official Dokka API docs for detailed endpoint and field descriptions)
- n8n HTTP Request node documentation (for understanding how headers and query parameters are routed)