Actions215
- V1 > Bank Billets Actions
- V1 > Bank Billet Accounts Actions
- V1 > Bank Billet Batches Actions
- V1 > Bank Billet Batch Exports Actions
- V1 > Bank Billet Discharges Actions
- V1 > Bank Billet Payments Actions
- V1 > Bank Billet Registrations Actions
- V1 > Bank Billet Remittances Actions
- V1 > Customers Actions
- V1 > Customer Subscriptions Actions
- V1 > Discharges Actions
- V1 > Email Deliveries Actions
- V1 > Events Actions
- V1 > Imports Actions
- V1 > Installments Actions
- V1 > Remittances Actions
- V1 > Reports Actions
- V1 > SMS Deliveries Actions
- V1 > User Info Actions
- V1 > Webhook Deliveries Actions
- V1 > Webhooks Actions
- Admin > Users Actions
- Admin > Connections Actions
- Admin > Certificates Actions
- Admin > Subaccounts Actions
- Charge > PIX Actions
- Charge > PIX Accounts Actions
- Data > Bank Billet Queries Actions
- EDI > EDI Boxes Actions
- Financial > Accounts Actions
- Financial > Balances Actions
- Financial > Commands Actions
- Financial > Statement Transactions Actions
- Financial > Transaction Imports Actions
- Financial > Providers Actions
- Payment > Bank Billets Actions
- Payment > Bank Billet Batches Actions
- Payment > Batches Actions
- Payment > DARFs Actions
- Payment > DARF Batches Actions
- Payment > PIX Actions
- Payment > PIX Batches Actions
- Payment > Utilities Actions
- Payment > Utility Batches Actions
- Transfer > Batches Actions
- Transfer > Internal Actions
- Transfer > Internal Batches Actions
- Transfer > PIX Actions
- Transfer > PIX Batches Actions
- Transfer > TED Actions
- Transfer > TED Batches Actions
Overview
This node integrates with the Kobana API to manage remittances and other financial resources. Specifically, the V1 > Remittances - Update operation allows users to update an existing remittance record by specifying its ID and providing a JSON request body with the updated data.
Common scenarios for this node include automating updates to remittance details in financial workflows, such as correcting information, changing statuses, or adding metadata. For example, a user might update a remittance's payment status or modify associated fields after receiving new information from a financial institution.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the remittance resource to update. |
| Additional Fields | A JSON object containing any extra fields to include in the request (optional). |
| Request Body | The JSON-formatted request body containing the updated remittance data (required). |
Output
The node outputs the JSON response returned by the Kobana API after updating the remittance. This typically includes the updated remittance object with all its properties reflecting the changes made.
- The output is structured as an array of JSON objects, each representing the updated remittance.
- No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Proper configuration of the Kobana API credentials within n8n is necessary.
Troubleshooting
- Invalid ID Error: If the provided remittance ID does not exist or is malformed, the API will return an error. Verify that the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON in the "Request Body" property is valid and correctly formatted; otherwise, the API will reject the request.
- Authentication Failures: Check that the API key credential is valid and has the required permissions.
- API Rate Limits: Excessive requests may be throttled by the Kobana API; implement retry logic or reduce request frequency if needed.
- Unexpected Errors: If the node returns an unknown error, enable "Continue On Fail" to capture error messages for debugging.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes