KobanaInstall

Overview

This node integrates with the Kobana API, enabling users to perform a wide range of operations related to financial and billing management. It supports creating, retrieving, updating, and managing various resources such as bank slips (boletos), customer subscriptions, webhooks, customers, and payment types including PIX and utilities.

For the Default Resource with the Create Operation, the node allows you to create new entities by sending a JSON request body to the appropriate Kobana API endpoint. This is useful for automating the creation of financial documents or records, such as generating new bank slips, customer subscriptions, or other supported items.

Practical examples:

• Automatically create a new bank slip when an order is placed.
• Create a new customer subscription after a user signs up.
• Generate a new webhook configuration programmatically.

Properties

The "Request Body" property is required and must contain the necessary data formatted as JSON for the resource being created.

The "Additional Fields" collection allows adding custom JSON fields that may extend or modify the request payload.

Output

The node outputs the response from the Kobana API as JSON data. The output structure corresponds directly to the API's response for the created resource, typically including identifiers, status, timestamps, and other relevant details about the newly created entity.

If the API returns binary data (not typical for create operations), it would be included accordingly, but this node primarily handles JSON responses.

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 additional external dependencies are needed beyond the configured Kobana API credentials.

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 all JSON inputs are valid.
• Authentication Errors: If the API key credential is missing or invalid, requests will fail with authentication errors. Verify that the correct API key is configured.
• API Endpoint Errors: Providing incorrect resource names or unsupported operations can cause 404 or method not allowed errors. Confirm that the resource and operation match the API documentation.
• Rate Limits or Quotas: The Kobana API may enforce rate limits; exceeding these could result in temporary failures. Implement retry logic or reduce request frequency if needed.

Links and References

• Kobana API Documentation (official API docs for detailed resource and operation info)
• n8n Documentation on Creating Custom Nodes