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 status updates related to public transactions, specifically for posting index statuses. It is useful in scenarios where you need to update or synchronize invoice or transaction statuses programmatically within a workflow. For example, you might use this node to mark invoices as cancelled or update their subtype status automatically based on external triggers or data processing results.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka for which the status update applies. |
| X Fields | An optional header field that acts as a mask to specify which fields should be returned or affected. |
| Body | A JSON object representing the status details to post. Typical fields include sub_type (e.g., "Invoice Status") and cancelled (boolean indicating cancellation status). |
Output
The node outputs JSON data corresponding to the response from the Dokka API after posting the index status. This typically includes confirmation of the updated status or any relevant metadata returned by the API. There is no indication that binary data is output by this node.
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's credential configuration.
Troubleshooting
- Missing or invalid Company ID: The API call will fail if the company ID is not provided or incorrect. Ensure the company ID is valid and correctly entered.
- Invalid JSON in Body: The body property expects valid JSON. Malformed JSON will cause errors. Use proper JSON formatting.
- Authentication errors: If the API key or token is missing or expired, the request will be unauthorized. Verify credentials are correctly configured.
- API endpoint issues: Network problems or incorrect base URL settings can cause failures. Confirm the base URL and network connectivity.
- Unexpected API responses: If the API changes or returns errors, check the response message for clues and verify the request payload matches expected schema.
Links and References
- Dokka API documentation (refer to official Dokka API docs for detailed endpoint and payload specifications)
- n8n documentation on HTTP Request nodes and credential management for API integrations