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 "Installments" under the V1 API version, specifically supporting the "Get Many" operation. It retrieves multiple installment records from the Kobana system, allowing users to fetch either all available installments or a limited subset based on specified criteria.
Common scenarios where this node is beneficial include:
- Retrieving a list of installment payments for reporting or reconciliation.
- Fetching installment data filtered by custom query parameters.
- Integrating installment data into workflows that require batch processing or analysis.
For example, a user might want to get all installments related to a specific customer or within a date range by specifying appropriate query parameters.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit (true/false). |
| Limit | Maximum number of results to return when "Return All" is false (range: 1 to 100). |
| Additional Fields | JSON object containing additional fields to include in the request (optional). |
| Query Parameters | JSON object with query parameters to filter or modify the GET request for installments. |
Output
The output is a JSON array where each item represents an installment record retrieved from the Kobana API. Each JSON object contains the details of an installment as returned by the API.
No binary data output is produced by 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).
- No other external dependencies are required.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing malformed JSON in "Additional Fields" or "Query Parameters" may result in request errors.
- Exceeding the maximum allowed limit (over 100) will be rejected by the node's input validation.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- JSON parsing errors suggest incorrect formatting in JSON input fields; ensure valid JSON syntax.
- API response errors may occur if query parameters are invalid or unsupported; review API documentation for correct usage.
Links and References
- Kobana API Documentation (for detailed API endpoints and parameters)
- n8n Documentation on Creating Custom Nodes