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 post vendor index data related to public transactions. It is designed to send structured JSON data representing vendor indexes to a specified company within Dokka's system. This operation is useful for automating the submission of transaction-related vendor information, which can be part of financial reporting, bookkeeping, or compliance workflows.
Practical examples include:
- Automatically sending vendor index updates after processing invoices.
- Integrating with accounting systems to keep vendor transaction indexes synchronized.
- Submitting batch vendor transaction data as part of a larger financial data pipeline.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka to which the vendor index data will be posted. This is required. |
| X Fields | An optional string used as a fields mask to specify which fields should be included or returned by the API. |
| Body | A JSON object containing the vendor index data to be posted. This must be valid JSON and represents the payload sent to the API. |
Output
The node outputs the JSON response from the Dokka API after posting the vendor index data. The structure of this JSON depends on the API's response but typically includes confirmation of the posted data, status messages, or any errors encountered.
If the API supports binary data responses (not indicated here), the node would handle them accordingly, but based on the provided code and properties, the output is purely JSON.
Dependencies
- Requires an active connection to the Dokka API, including a valid API authentication token configured in n8n credentials.
- The base URL for the Dokka API must be set in the node's credential configuration.
- The node uses standard HTTP headers for JSON content negotiation (
Accept: application/jsonandContent-Type: application/json).
Troubleshooting
- Invalid Company ID: If the company ID is incorrect or not found, the API may return an error. Verify the company ID is correct and exists in Dokka.
- Malformed JSON Body: The body property must contain valid JSON. Errors in parsing or invalid JSON structure will cause the request to fail. Use proper JSON formatting.
- Authentication Errors: Missing or invalid API credentials will result in authorization failures. Ensure the API key/token is correctly configured.
- API Field Mask Issues: Incorrect usage of the optional "X Fields" header might lead to unexpected results or errors. Use it only if you understand the API's field masking capabilities.
- Network Issues: Connectivity problems between n8n and the Dokka API endpoint can cause timeouts or failed requests.
Links and References
- Dokka API Documentation (general reference): https://docs.dokka.com/api (Replace with actual URL if known)
- JSON Formatting Guide: https://www.json.org/json-en.html
- n8n HTTP Request Node Documentation (for understanding routing and headers): https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/