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 payment batches, specifically supporting the Update operation on the "Payment > PIX Batches" resource. It allows users to update existing PIX batch records by sending a JSON request body with the desired changes.
Typical use cases include:
- Modifying details of a PIX payment batch after its creation.
- Adjusting batch metadata or status fields as part of payment processing workflows.
- Automating updates to batches in response to external events or business logic.
For example, you might update a PIX batch to change its description, adjust scheduled payment dates, or modify other batch-level attributes supported by the API.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX batch to update. |
| Request Body | A JSON object containing the fields and values to update in the PIX batch. This is required. |
Note: There is also an "Additional Fields" collection available generally for some operations, but for this specific Update operation on PIX Batches, only the above properties are relevant.
Output
The node outputs the JSON response returned by the Kobana API after performing the update operation. This typically includes the updated PIX batch object with all its current properties reflecting the changes made.
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, which provides authentication tokens necessary to access the Kobana API endpoints.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- The API version used for PIX Batches is v2, and the endpoint path is
/payment/pix_batches/{id}with HTTP method PUT for updates.
Troubleshooting
- Invalid or missing ID: If the provided batch ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing PIX batch.
- Malformed JSON in Request Body: The request body must be valid JSON. Syntax errors or invalid field names may cause the API to reject the request.
- Authentication errors: If the API credentials are incorrect or expired, requests will fail. Verify that the Kobana API credential is properly set up and has the necessary permissions.
- API rate limits or downtime: Temporary failures may occur due to API limits or service issues. Retrying after some time or checking the Kobana status page can help.
- Unexpected errors: The node supports continuing on failure; enabling this option can help process multiple items even if some fail.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- PIX Payment Batch API Reference (specific details about PIX batch operations)
If you need further details on the exact JSON schema for the request body or examples of update payloads, please consult the official Kobana API documentation or provide additional context.
