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 customer index data under the "Public Transactions" resource. Specifically, the "Post Indexes Customer" operation allows users to send customer-related transaction indexes to the Dokka system. This is useful for integrating external systems with Dokka to automate the submission of customer transaction data, ensuring that financial or transactional records are synchronized.
Practical examples include:
- Automatically sending customer transaction indexes from an e-commerce platform to Dokka for accounting purposes.
- Integrating CRM systems to push updated customer transaction indexes into Dokka for consolidated reporting.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka where the customer indexes will be posted. |
| X Fields | An optional mask specifying which fields to include in the response or request headers. |
| Body | A JSON object containing the customer index data to be posted to Dokka. |
Output
The node outputs the JSON response returned by the Dokka API after posting the customer indexes. This typically includes confirmation details, status messages, or any data returned by the API related to the posted indexes.
If the API supports binary data output (not indicated here), it would represent files or attachments related to the transaction indexes, but this node primarily deals with JSON data.
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 building.
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 the request is sent.
- 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 no firewall or proxy blocks the requests.
- Unexpected API responses: Review the API documentation for required fields and correct request structure if errors occur.
Links and References
- Dokka API Documentation (general reference): https://dokka.api.docs (replace with actual URL if known)
- n8n OpenAPI Node Integration Guide: https://docs.n8n.io/integrations/builtin/app-nodes/n8n-openapi-node/