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 SMS deliveries under the "V1 > SMS Deliveries" resource. The "Get" operation fetches details of a specific SMS delivery by its unique ID.
Typical use cases include:
- Retrieving the status and details of an SMS message sent through Kobana.
- Monitoring delivery reports or troubleshooting SMS sending issues.
- Integrating SMS delivery data into workflows for notifications, logging, or analytics.
For example, you might use this node to get the delivery status of a transactional SMS sent to a customer, enabling your workflow to react accordingly (e.g., retry sending if failed).
Properties
| Name | Meaning |
|---|---|
| ID | The unique identifier of the SMS delivery resource to retrieve. This is required to specify which SMS delivery record to fetch. |
Output
The node outputs JSON data representing the SMS delivery object retrieved from the Kobana API. This typically includes fields such as delivery status, timestamps, recipient information, message content, and any metadata related to the SMS delivery.
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 connectivity to the Kobana API endpoints is necessary.
Troubleshooting
Common Issues:
- Invalid or missing ID parameter will cause the API request to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network issues or Kobana service downtime can cause request failures.
Error Messages:
"Resource not found"or similar indicates the provided ID does not exist.- Authentication errors suggest checking the API key or token validity.
- JSON parsing errors may occur if the input body is malformed (not applicable here since only ID is used).
Resolutions:
- Verify the ID is correct and corresponds to an existing SMS delivery.
- Ensure the Kobana API credential is valid and has access rights.
- Check network connectivity and Kobana service status.
Links and References
- Kobana API Documentation (general reference; check for SMS delivery endpoints)
- n8n documentation on API Credentials for setting up the Kobana API key
Note: This summary is based solely on static analysis of the node's source code and provided property definitions. Runtime behavior depends on actual API responses and environment configuration.