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 PIX transfer batches, specifically supporting the Update operation on the "Transfer > PIX Batches" resource. It allows users to update existing PIX transfer batch records by sending a JSON request body with the desired changes.
Typical use cases include:
- Modifying details of a PIX transfer batch after creation.
- Adjusting batch parameters or metadata before processing.
- Automating updates to batches based on external triggers or workflows.
For example, you might update the description or status of a PIX transfer batch to reflect new information or correct errors.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX transfer batch to update. |
| Request Body | A JSON object containing the fields and values to update in the PIX transfer batch. |
| Additional Fields | (Optional) A JSON object with extra fields for the request; can be used to send custom data. |
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated PIX transfer batch object with its current state and properties.
The output is structured as an array of JSON objects, each representing the updated batch data corresponding to the input item processed.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n for authentication.
- The node sends HTTP requests to the Kobana API endpoint, which varies depending on environment (production or sandbox).
- No additional external dependencies are required.
Troubleshooting
- Invalid ID error: If the provided batch ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
- Malformed JSON in Request Body: Ensure the JSON provided in the "Request Body" property is valid and correctly formatted.
- Authentication failures: Confirm that the Kobana API credential is properly set up and has necessary permissions.
- API rate limits or downtime: Temporary network or API issues may cause failures; retry or check Kobana service status.
- Unexpected errors: Enable "Continue On Fail" in the node settings to handle errors gracefully and inspect error messages in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics (conceptual)
Note: The above summary is based solely on static analysis of the provided source code and property definitions.