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
V1 > Email Deliveries → Get Many
AI-generatedOverview
This node interacts with the Kobana API to manage email delivery records under the "V1 > Email Deliveries" resource. Specifically, the Get Many operation retrieves multiple email delivery records from the Kobana system. It supports fetching either all available records or a limited subset based on user-defined parameters.
Typical use cases include:
- Retrieving a list of email deliveries for reporting or auditing purposes.
- Filtering email deliveries by specific query parameters such as date ranges, status, or recipient.
- Integrating Kobana email delivery data into workflows for further processing or notifications.
For example, a user might want to fetch the last 50 email deliveries sent in the past week to analyze delivery success rates or troubleshoot issues.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all email delivery records or limit the number of results returned. |
| Limit | The maximum number of email delivery records to return when "Return All" is false (1-100). |
| Additional Fields | JSON object containing additional fields to customize the request (optional). |
| Query Parameters | JSON object with query parameters to filter or modify the retrieval of email deliveries. |
Output
The node outputs an array of JSON objects representing email delivery records retrieved from the Kobana API. Each object corresponds to one email delivery and contains details such as recipient, status, timestamps, and other metadata provided by the API.
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this operation focuses on JSON data only.
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 required beyond the Kobana API access.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Providing invalid JSON in the "Additional Fields" or "Query Parameters" properties may result in request errors.
- Exceeding the allowed limit (max 100) will be rejected by the API.
Error Messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- JSON parsing errors suggest malformed JSON input; ensure proper formatting.
- API rate limits or server errors should be handled by retrying after some delay or contacting Kobana support.
Links and References
- Kobana API Documentation (general reference for API endpoints and parameters)
- n8n documentation on HTTP Request Node for understanding request customization (conceptual)
