Overview
This node sends messages via the Inboxino API, supporting multiple messaging channels such as Telegram, WhatsApp, Instagram, and SMS. It allows sending different types of messages including text, audio, document, image, location, and video. This node is useful for automating communication workflows where messages need to be sent programmatically to various receivers on different platforms.
Use Case Examples
- Sending a text message to a WhatsApp user.
- Sending an image with a caption to a Telegram channel.
- Sharing a location via SMS.
Properties
| Name | Meaning |
|---|---|
| Account | The account identifier used to send the message. |
| Channel | The messaging channel to use for sending the message (Telegram, WhatsApp, Instagram, SMS). |
| Receiver | The receiver identifier such as phone number or username. |
| Message Type | The type of message to send. |
| Message Content | The text content of the message to send (required if message type is text). |
| Media URL | The URL of the media file to send (required if message type is image, video, audio, or document). |
| Caption | Optional caption for the media message. |
| Latitude | Latitude coordinate for location messages. |
| Longitude | Longitude coordinate for location messages. |
Output
JSON
json- The JSON response from the Inboxino API after sending the message, containing details about the sent message or error information.
Dependencies
- Inboxino API with authentication credentials
Troubleshooting
- Common issues include invalid account identifiers, unsupported receiver formats, or incorrect media URLs which may cause API errors.
- Error messages from the API typically indicate issues with authentication, missing required parameters, or invalid message types.
- Ensure the correct credentials are configured and all required fields for the selected message type are provided to avoid errors.
Links
- Inboxino API Documentation - Official API endpoint documentation for sending messages via Inboxino.