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 data and other related resources. Specifically, the "Find by Email" operation under the "V1 > Customers" resource allows users to search for a customer by their email address. This is useful in scenarios where you need to retrieve customer details based on their email, such as verifying if a customer exists before creating an order or updating customer information.
Practical examples:
- Automatically fetching customer details during a signup or checkout process using their email.
- Validating customer existence in your system before sending marketing emails.
- Integrating with CRM systems to sync customer data based on email addresses.
Properties
| Name | Meaning |
|---|---|
| Query Parameters | JSON object with additional query parameters to customize the search request. |
| The email address used to find the corresponding customer record (required). |
Output
The node outputs a JSON array containing the customer data returned from the Kobana API that matches the provided email address. Each item in the output corresponds to a customer record found.
- The
jsonfield contains the customer details as returned by the API. - No binary data output is produced by this operation.
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).
- Proper configuration of the Kobana API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing an invalid email format may result in no results or API errors.
- Network connectivity issues can prevent successful API calls.
Error messages:
- Authentication errors typically indicate incorrect or expired API keys; verify and update credentials.
- If the API returns no customers, ensure the email exists in the Kobana system.
- JSON parsing errors may occur if the input JSON in query parameters is malformed; validate JSON syntax carefully.
Links and References
- Kobana API Documentation (general reference for API endpoints)
- n8n documentation on HTTP Request Node for understanding API integrations