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 interacts with the Kobana API to manage remittances and other financial resources. Specifically, the "V1 > Remittances" resource with the "Get Many" operation allows users to retrieve multiple remittance records from their Kobana account. This is useful for scenarios where you need to list or analyze batches of remittances, such as generating reports, auditing transactions, or syncing data with other systems.
For example, a finance team might use this node to fetch all remittances within a certain date range or filter by status to reconcile payments. Developers can automate workflows that require bulk retrieval of remittance data without manually querying the Kobana dashboard.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all remittance results or limit the number of returned items. |
| Limit | The maximum number of remittance records to return when "Return All" is false (max 100). |
| Additional Fields | JSON object containing extra fields to include in the request for extended filtering or options. |
| Query Parameters | JSON object with query parameters to filter or modify the request (e.g., date ranges, statuses). |
Output
The node outputs an array of JSON objects representing remittance records retrieved from the Kobana API. Each item corresponds to one remittance entry with its associated data fields as provided by the API.
If binary data were involved (not applicable here), it would be summarized accordingly, but this operation returns only JSON data.
Dependencies
- Requires an API key credential for authenticating with the Kobana API.
- The node automatically selects the API base URL depending on whether the environment is production or sandbox.
- No additional external dependencies are required beyond the Kobana API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in "Additional Fields" or "Query Parameters" may result in request errors.
- Exceeding the allowed limit (more than 100) will be rejected by the API.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- JSON parsing errors suggest malformed input in the JSON fields; ensure valid JSON syntax.
- Rate limiting or quota exceeded errors may occur if too many requests are made; consider enabling "Return All" carefully or adding delays.
Links and References
- Kobana API Documentation (general reference for API endpoints and parameters)
- n8n documentation on Using API Credentials
