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 allows users to post public transaction orders to the Dokka API. It is designed to send order data, including detailed line items, to a specified company within Dokka's system. This functionality is useful for automating the creation of sales or purchase orders in accounting or ERP workflows, enabling seamless integration between n8n and Dokka.
Practical examples include:
- Automatically creating sales orders from e-commerce platforms.
- Posting purchase orders generated by procurement systems.
- Syncing order data from CRM tools into Dokka for financial tracking.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the Dokka company where the order will be posted. |
| X Fields | An optional mask specifying which fields to include in the response or request headers. |
| Body | The JSON payload representing the order details, including an array of line items. |
Output
The node outputs JSON data representing the response from the Dokka API after posting the order. This typically includes confirmation details such as order IDs, status, and any 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 via an API key or authentication token configured in n8n credentials.
- The base URL for the Dokka API must be set in the node’s credential configuration.
- The node depends on the
n8n-openapi-nodepackage and the bundled OpenAPI specification (openapi.json) for request construction.
Troubleshooting
- Missing or invalid Company ID: Ensure the Company ID is correctly provided; otherwise, the API will reject the request.
- Malformed JSON in Body: The body property expects valid JSON. Invalid JSON will cause parsing errors before sending the request.
- Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- Network issues: Check connectivity to the Dokka API endpoint and ensure the base URL is correct.
- Unexpected API responses: Use the optional "X Fields" header to control response content if needed, which may help with debugging or reducing payload size.
Links and References
- Dokka API Documentation (general reference): https://dokka.docs.api (replace with actual URL if known)
- n8n Documentation on HTTP Request Nodes: https://docs.n8n.io/nodes/n8n-nodes-base.httpRequest/