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 invoices for a specified company. It is designed to fetch invoice data based on filtering criteria and optional field selection, making it useful for automating financial workflows, accounting integrations, or reporting systems that require up-to-date invoice information from Dokka.
Typical use cases include:
- Automatically retrieving all invoices for a company within a certain date range.
- Filtering invoices by status or document ID to process only relevant records.
- Selecting specific fields of invoice data to optimize payload size and processing.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka whose invoices are to be retrieved. This is required. |
| Filter | A query string filter to narrow down invoices by allowed fields such as document_id, status, date, due_date, publication_date, last_approval_date, last_update, filename. Example: status eq 'paid' and date gt 2023-01-01. Optional. |
| X Fields | An optional mask specifying which fields of the invoice data to return. This can reduce response size by selecting only needed fields. Optional. |
Output
The node outputs JSON data representing the list of invoices matching the request parameters. Each invoice object contains fields as returned by the Dokka API, potentially filtered by the "X Fields" property.
If binary data were involved (e.g., PDF invoice files), it would be indicated here, but this node focuses on JSON invoice metadata.
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.
- No additional external dependencies beyond the Dokka API and standard HTTP requests.
Troubleshooting
- Missing or invalid Company ID: The node requires a valid company identifier; ensure this is correctly provided.
- API authentication errors: Verify that the API key or token is correctly configured and has sufficient permissions.
- Invalid filter syntax: Filters must conform to allowed fields and syntax; incorrect filters may cause API errors.
- Empty results: If no invoices are returned, check filter criteria and confirm that the company has invoices matching those filters.
- Network issues: Ensure connectivity to the Dokka API endpoint and that the base URL is correct.
Links and References
- Dokka API documentation (refer to official Dokka API docs for detailed filter syntax and available invoice fields)
- n8n documentation on HTTP Request nodes and credential setup for API integrations