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 allows you to interact with the Kobana API specifically for managing PIX charges under the "Charge > PIX" resource. The "Get" operation retrieves detailed information about a specific PIX charge by its unique ID. This is useful when you need to fetch the current status, details, or metadata of a particular PIX charge in your financial workflows.
Common scenarios:
- Retrieving payment status for reconciliation.
- Fetching charge details to display in dashboards or reports.
- Validating charge existence before further processing.
Practical example:
You have created a PIX charge and want to check if it has been paid or canceled. Using this node with the "Get" operation and providing the charge ID will return all relevant data about that charge.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the PIX charge to retrieve. This is a required string input. |
Output
The node outputs a JSON object representing the PIX charge details as returned by the Kobana API. This includes all available fields describing the charge such as amount, status, creation date, expiration, payer information, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an active Kobana API credential configured in n8n with appropriate permissions.
- The node dynamically selects the API base URL depending on whether the environment is production or sandbox.
- Network access to the Kobana API endpoints is necessary.
Troubleshooting
- Invalid or missing ID: If the provided ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing PIX charge.
- Authentication errors: If the API key or credentials are invalid or expired, requests will fail. Verify the Kobana API credential configuration.
- Network issues: Connectivity problems can cause request failures. Check network access and firewall settings.
- API rate limits: Excessive requests may be throttled by the Kobana API. Implement retry logic or reduce request frequency if needed.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- PIX Payment System Overview (for understanding PIX payments in Brazil)