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 "Get Many" operation for the resource "Transfer > PIX Batches". It allows users to retrieve multiple PIX transfer batch records from their Kobana account.
Common scenarios where this node is beneficial include:
- Retrieving a list of PIX transfer batches for reconciliation or reporting.
- Fetching batches filtered by specific query parameters such as date ranges or status.
- Automating workflows that require processing or analyzing multiple PIX transfer batches at once.
For example, a user might want to fetch all PIX transfer batches created in the last month to generate a financial report or to trigger downstream processes based on batch statuses.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return (only used if Return All is false). Range: 1 to 100. |
| Additional Fields | JSON object with additional fields for the request (optional extra parameters). |
| Query Parameters | JSON object with query parameters to filter or modify the request (e.g., filters, sorting). |
Output
The node outputs an array of JSON objects representing PIX transfer batches retrieved from the Kobana API. Each object corresponds to one PIX transfer batch and contains its details as returned by the API.
If the API supports binary data for this resource (not indicated here), it would be summarized accordingly, but for this operation, the output is purely JSON data describing the batches.
Dependencies
- Requires an API key credential for Kobana API authentication.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- No other external dependencies are required.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in "Additional Fields" or "Query Parameters" may cause request errors.
- Exceeding API rate limits or requesting too many records without pagination can lead to errors or timeouts.
Error Messages:
- Authentication errors typically indicate invalid or missing API keys; verify credentials.
- JSON parsing errors suggest malformed JSON input in properties; ensure valid JSON syntax.
- API response errors may include messages about invalid parameters; check query parameters and limits.
To resolve these issues:
- Double-check API credentials and permissions.
- Validate JSON inputs using online tools before entering them.
- Use the "Return All" option carefully to avoid large data requests; prefer setting reasonable limits.
Links and References
- Kobana API Documentation (general reference for API endpoints and usage)
- n8n documentation on HTTP Request Node for understanding API calls
- JSON validation tools like JSONLint for verifying JSON inputs
