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 perform operations on customer data within the "V1 > Customers" resource. Specifically, the "Get" operation retrieves detailed information about a single customer by their unique ID. This is useful in scenarios where you need to fetch customer details for further processing, reporting, or integration with other systems.
Practical examples include:
- Retrieving customer profile information before updating records.
- Fetching customer data to display in dashboards or CRM systems.
- Using customer details to trigger workflows based on specific attributes.
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the customer to retrieve. This is a required string input. |
Output
The output is a JSON object representing the customer data retrieved from the Kobana API. It contains all available fields related to the customer record identified by the provided ID.
The node does not output binary data for 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 the environment (production or sandbox).
- Network access to the Kobana API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing customer ID will result in an error from the API.
- Authentication failures if the API key or credentials are incorrect or expired.
- Network connectivity problems can cause request timeouts or failures.
Error messages and resolutions:
"404 Not Found": The specified customer ID does not exist. Verify the ID is correct."401 Unauthorized"or"403 Forbidden": Check that the API credentials are valid and have sufficient permissions."Invalid JSON"errors when providing additional fields or body parameters usually indicate malformed JSON input; ensure proper formatting.
Links and References
- Kobana API Documentation (general reference for API endpoints and data structures)
- n8n documentation on API Credentials for setting up authentication tokens
