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
The node interacts with the Dokka API to retrieve public transaction orders for a specified company. It is useful in scenarios where you need to fetch order data from Dokka for reporting, auditing, or integration with other systems. For example, a finance team could use this node to automatically pull recent orders for reconciliation or analysis.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka whose orders are fetched. |
| X Fields | An optional header to specify a fields mask, controlling which fields are returned in the response. |
Output
The node outputs JSON data representing the list of orders retrieved from the Dokka API for the specified company. The structure corresponds to the API's response schema for public transactions/orders. If the X Fields property is used, the output will include only the specified fields. There is no indication that binary data is returned by this node.
Dependencies
- Requires an active connection to the Dokka API.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- The base URL for the Dokka API must be set in the node credentials.
Troubleshooting
- Missing or invalid Company ID: The node requires a valid company ID; ensure it is correctly provided.
- Authentication errors: Verify that the API key credential is correctly configured and has sufficient permissions.
- Empty or incomplete responses: If using the
X Fieldsmask, ensure the field names are valid according to the Dokka API documentation. - Network issues: Check connectivity to the Dokka API endpoint and confirm the base URL is correct.
Links and References
- Dokka API Documentation (please refer to the official Dokka API docs for detailed information on endpoints and fields)
- n8n HTTP Request Node documentation (for understanding how headers and query parameters are routed)