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 retrieve public payment transactions associated with a specified company. It is useful for scenarios where you need to fetch payment data such as invoices, payment statuses, or bank account details from Dokka's public transaction records. For example, an accounting workflow could use this node to automatically pull recent payments for reconciliation or reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Company ID | The unique identifier of the company in Dokka whose public payment transactions you want to retrieve. |
| Filter | A query string filter to narrow down results based on fields like document_id, erp_invoice_id, payment_status, payment_id, payment_date, bank_account, or publication_date. |
| X Fields | An optional mask specifying which fields to include in the response, allowing you to limit the returned data to only what is needed. |
Output
The node outputs JSON data representing the list of payment transactions retrieved from the Dokka API. Each item in the output typically contains details such as payment IDs, invoice references, payment status, dates, and bank account information depending on the applied filters and field masks.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Dokka API.
- Needs an API authentication token configured in the node credentials.
- The base URL for the Dokka API must be set in the node credentials or environment configuration.
Troubleshooting
- Missing or invalid Company ID: Ensure that the Company ID is correctly provided and corresponds to a valid company in Dokka.
- API authentication errors: Verify that the API key or token used in credentials is valid and has sufficient permissions.
- Filter syntax issues: The
$filterproperty must follow the allowed fields and correct syntax; otherwise, the API may return errors or empty results. - Empty responses: If no payments are returned, check if the filter criteria are too restrictive or if there are genuinely no matching records.
- Network or connectivity problems: Confirm that the base URL is reachable and that there are no firewall or proxy issues blocking access.
Links and References
- Dokka API Documentation (example link, replace with actual)
- n8n Documentation on HTTP Request Node for understanding API interactions
- General guidance on OData Filtering Syntax which might be relevant for the
$filterproperty usage