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 Bank Billet Accounts (billing wallets). Specifically, the Create operation allows users to create a new billing wallet in the Kobana system. This is useful for businesses that need to organize and manage multiple billing wallets for issuing bank slips (boletos) or other payment methods.
Typical use cases include:
- Automating the creation of billing wallets when onboarding new clients or business units.
- Integrating billing wallet creation into larger financial workflows.
- Managing multiple billing wallets programmatically without manual intervention.
Example: A company wants to automatically create a new billing wallet for each regional office to segregate payments and collections by location.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the details of the billing wallet to be created. This must contain all required fields as per the Kobana API specification for creating a billing wallet. |
| Additional Fields | Optional JSON object with extra fields to include in the request. Useful for adding any custom or less common parameters supported by the API. |
Output
The node outputs the JSON response returned by the Kobana API after creating the billing wallet. This typically includes details about the newly created billing wallet such as its ID, name, status, and other metadata provided by the API.
If the API returns binary data (not typical for this operation), it would be included accordingly, but for the Create operation on Bank Billet Accounts, the output is standard JSON.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- The request uses HTTP POST method to the
/bank_billet_accountsendpoint of the Kobana API v1.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" or "Additional Fields" is malformed, the node will throw a parsing error. Ensure valid JSON syntax.
- Missing Required Fields: The API may reject requests missing mandatory fields. Verify the request body contains all required properties according to Kobana's API documentation.
- Authentication Errors: If the API key or credentials are invalid or expired, the node will fail authentication. Check and update the Kobana API credentials in n8n.
- API Endpoint Errors: Network issues or incorrect environment selection (sandbox vs production) can cause failures. Confirm the environment setting matches your intended API endpoint.
- Rate Limits or Quotas: Excessive requests might be throttled by the API. Implement error handling or delays if needed.
Links and References
- Kobana API Documentation (general reference for API endpoints and payloads)
- Bank Billet Accounts API Reference (specific details on creating billing wallets)
This summary is based solely on static analysis of the provided source code and input property definitions.
