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 customer subscriptions and other related resources. Specifically, for the V1 > Customer Subscriptions resource with the Create operation, it allows users to create new customer subscription records by sending a JSON request body to the Kobana API.
Typical use cases include automating subscription management workflows such as onboarding new customers with subscriptions, integrating subscription creation into larger business processes, or syncing subscription data from other systems.
For example, you might use this node to:
- Automatically create a subscription when a customer signs up on your website.
- Batch-create multiple subscriptions based on external data feeds.
- Integrate subscription creation into a CRM or billing system workflow.
Properties
| Name | Meaning |
|---|---|
| Request Body | The JSON object representing the subscription details to be created in the API request. This must contain all required fields for creating a subscription. |
| Additional Fields | Optional JSON object with extra fields that can be added to the request for extended customization. |
Output
The node outputs the JSON response returned by the Kobana API after creating the subscription. This typically includes details of the newly created subscription such as its ID, status, customer information, plan details, and timestamps.
The output is structured as an array of JSON objects, each corresponding to an input item processed. Each object contains the full API response for that subscription creation request.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions to create customer subscriptions.
- The node dynamically selects the API base URL depending on the environment (production or sandbox).
- Network connectivity to the Kobana API endpoints is necessary.
Troubleshooting
- Invalid JSON in Request Body: If the JSON provided in the "Request Body" property is malformed, the node will throw a parsing error. Ensure the JSON syntax is correct.
- Missing Required Fields: The API may reject requests missing mandatory subscription fields. Verify the request body includes all required data 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 Rate Limits or Downtime: Temporary failures may occur due to rate limiting or service outages. Implement retry logic or check Kobana's service status if errors persist.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output.
Links and References
- Kobana API Documentation (general reference for API endpoints and request formats)
- n8n Documentation on Using Credentials
- JSON validation tools (e.g., https://jsonlint.com) to verify request body correctness
