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 allows updating payment information for public transactions via a PATCH HTTP request. It is useful when you need to modify specific fields of a payment record without replacing the entire resource. For example, you might update the status or amount of a payment in a financial system that exposes a REST API supporting partial updates.
Properties
| Name | Meaning |
|---|---|
| X Fields | An optional string to specify a fields mask, controlling which fields are returned or affected. |
| Body | A JSON object representing the data to patch on the payment resource. |
Output
The node outputs the JSON response from the API after applying the patch to the payment. This typically contains the updated payment resource with its current state after modification. There is no binary output.
Dependencies
- Requires an API key credential for authenticating requests to the Dokka API.
- The base URL for the API must be configured in the node credentials.
- The node depends on the n8n-openapi-node package and the bundled OpenAPI specification (
openapi.json) for request construction.
Troubleshooting
- Invalid JSON in Body: If the "Body" property contains malformed JSON, the node will fail parsing it. Ensure valid JSON syntax.
- Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify the API key and base URL configuration.
- Field Mask Issues: Incorrect usage of the "X Fields" mask may result in unexpected responses or errors. Confirm the mask format matches API expectations.
- API Endpoint Errors: If the payment ID or other required identifiers are missing or invalid, the API may return 404 or 400 errors. Check input data correctness.
Links and References
- Dokka API Documentation (hypothetical link)
- n8n OpenAPI Node Integration Guide
