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 category indexes related to public transactions. Specifically, it sends a POST request to create or update categories under the "Public Transactions" resource. This is useful for users who want to programmatically manage transaction categories within their Dokka company account, such as automating categorization of financial data or integrating external systems that classify transactions.
Practical examples include:
- Automatically posting new transaction categories based on external business logic.
- Syncing category data from other financial tools into Dokka.
- Managing and updating category metadata in bulk via workflows.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the Dokka company for which the categories are being posted. |
| X Fields | An optional header field to specify a mask of fields to be returned or processed. |
| Body | JSON object representing the category data to post. By default, it includes "sub_type": "Category". |
Output
The node outputs JSON data corresponding to the response from the Dokka API after posting the category indexes. This typically includes confirmation details about the created or updated categories, such as IDs, names, and any metadata returned by the API.
If the API supports binary data responses (not indicated here), the node would handle them accordingly, but this operation primarily deals with JSON payloads.
Dependencies
- Requires an active connection to the Dokka API, authenticated via an API key or token configured in n8n credentials.
- The base URL for the Dokka API must be set in the node's credential configuration.
- No additional external dependencies beyond the Dokka API and standard HTTP request handling.
Troubleshooting
- Missing or invalid Company ID: Ensure the
Company IDproperty is correctly set; otherwise, the API will reject the request. - Invalid JSON in Body: The body must be valid JSON. Errors parsing the body will cause the node to fail.
- Authentication errors: Verify that the API key/token credential is valid and has sufficient permissions.
- API endpoint errors: If the Dokka API returns errors (e.g., 4xx or 5xx status codes), check the request parameters and network connectivity.
- Incorrect X Fields usage: Misuse of the optional
X Fieldsheader might result in unexpected API responses or errors.
Links and References
- Dokka API documentation (general reference for endpoints and data structures)
- n8n HTTP Request node documentation (for understanding how routing and request options work)