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 customer index data from public transactions. Specifically, the "Get Indexes Customer" operation fetches indexed customer information for a given company. This is useful in scenarios where you need to programmatically access summarized or indexed transaction data related to customers within a specific company context.
Practical examples include:
- Automating financial reporting by pulling customer transaction indexes.
- Integrating Dokka's customer transaction summaries into dashboards or other business intelligence tools.
- Syncing customer transaction indexes with other systems for reconciliation or auditing purposes.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka for which to retrieve customer indexes. |
| X Fields | An optional mask specifying which fields to include in the response (customizable output). |
Output
The node outputs JSON data containing the customer indexes retrieved from the Dokka API for the specified company. The structure typically includes indexed transaction details per customer, but the exact schema depends on the API response and any field masking applied via the "X Fields" property.
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 n8n credentials to authorize requests.
- The base URL for the Dokka API must be set in the node credentials configuration.
Troubleshooting
- Missing or invalid Company ID: Ensure the "Company ID" property is correctly set; otherwise, the API will reject the request.
- Authentication errors: Verify that the API key or token credential is valid and has sufficient permissions.
- Incorrect "X Fields" format: If using the optional "X Fields" header, ensure it matches the expected format; otherwise, the API may ignore it or return errors.
- Network issues: Confirm network connectivity to the Dokka API endpoint.
- API rate limits or downtime: Check Dokka service status if requests fail repeatedly.
Links and References
- Dokka API Documentation (replace with actual URL)
- n8n documentation on HTTP Request Node for understanding how headers and query parameters are handled.