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 a specific public document based on provided identifiers. It is useful when you need to fetch detailed information about a document stored in Dokka, such as for displaying document data in workflows, integrating document metadata into other systems, or automating document processing tasks.
A practical example would be an automation that, given a document ID and company ID, retrieves the document details from Dokka and then uses this data to update records in a CRM or trigger further processing steps.
Properties
| Name | Meaning |
|---|---|
| Document Id | The unique identifier of the document to retrieve from Dokka. |
| Company ID | The identifier of the company associated with the document in Dokka. |
Both properties are required to specify exactly which document to fetch.
Output
The node outputs JSON data representing the retrieved document's details from the Dokka API. This typically includes all metadata and content fields returned by the API for the specified document.
No binary data output is indicated in the source code.
Dependencies
- Requires an API key credential for authenticating with the Dokka API.
- The base URL for the Dokka API must be configured in the node credentials.
- The node depends on the
n8n-openapi-nodepackage and an OpenAPI specification (openapi.json) bundled with the node for request building.
Troubleshooting
- Missing or invalid Document Id or Company ID: Ensure both IDs are correctly provided; otherwise, the API call will fail or return no data.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API endpoint issues: Confirm the base URL is correct and the Dokka API service is reachable.
- Unexpected API responses: Check if the document exists and the IDs correspond to accessible resources.
Links and References
- Dokka API documentation (not provided in source, check official Dokka developer resources)
- n8n documentation on creating custom nodes and using API credentials