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 account index data related to public transactions. It is useful for automating the submission of financial or accounting indexes to the Dokka system, which can be part of workflows involving bookkeeping, auditing, or financial reporting.
A practical example would be a workflow that collects transaction data from various sources and then posts summarized account indexes to Dokka for further processing or compliance purposes.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka where the account indexes will be posted. |
| X Fields | An optional header field used as a mask to specify which fields should be included in the response or request. |
| Body | A JSON object containing the detailed data of the account indexes to be posted. |
Output
The node outputs JSON data representing the response from the Dokka API after posting the account indexes. This typically includes confirmation details, status messages, or any returned data relevant to the posted indexes.
If the API supports binary data responses, this node does not explicitly handle them based on the provided code.
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's credential configuration.
Troubleshooting
- Common issues:
- Missing or incorrect Company ID can cause the API call to fail.
- Malformed JSON in the Body property may result in parsing errors.
- Incorrect or missing API credentials will lead to authentication failures.
- Error messages:
- Authentication errors usually indicate invalid or missing API keys; verify credentials.
- Validation errors from the API often point to missing required fields or incorrect data formats in the Body.
- Network or connectivity errors suggest checking the base URL and network access.
Links and References
- Dokka API documentation (refer to your internal or official Dokka API docs for detailed endpoint and schema information).