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 provides integration with the Kobana API, enabling users to perform various operations on financial and transfer-related resources. Specifically, for the Transfer > TED resource with the Get operation, the node retrieves detailed information about a specific TED (Electronic Transfer Document) transfer by its unique ID.
Typical use cases include:
- Fetching details of a particular TED transfer to verify its status or data.
- Automating workflows that require confirmation or processing of TED transfers.
- Integrating TED transfer data into reporting or accounting systems.
Example: A user can input the ID of a TED transfer and retrieve all associated information such as amount, sender, receiver, date, and status.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the TED transfer resource to retrieve. This is a required string property. |
Output
The node outputs a JSON object representing the TED transfer resource corresponding to the provided ID. The structure includes all relevant fields returned by the Kobana API for a TED transfer, such as transfer details, amounts, dates, and statuses.
If the node supports binary data output for other operations or resources, it would typically represent files or documents related to transfers, but for the Get operation on TED transfers, the output is purely JSON.
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 Kobana API access.
Troubleshooting
- Invalid or missing ID: If the ID parameter is empty or incorrect, the API will likely return an error indicating the resource was not found. Ensure the ID is correct and corresponds to an existing TED transfer.
- Authentication errors: If the API key credential is invalid or missing, requests will fail with authentication errors. Verify that the API key is correctly configured in n8n credentials.
- Network or API availability issues: Temporary network problems or Kobana API downtime may cause request failures. Retry after some time or check the API status.
- JSON parsing errors: When providing additional JSON parameters (not applicable here for Get), ensure valid JSON syntax to avoid errors.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on creating custom nodes for further customization guidance
