Actions17
- Contacts Actions
- SMS Messages Actions
- WhatsApp Messages Actions
- RCS Messages Actions
- Omni Rooms Actions
- Message Templates Actions
Overview
This node integrates with the Yup.chat API to send RCS (Rich Communication Services) messages. It allows users to send different types of RCS messages such as text, media, cards, and carousels to recipients via their phone numbers in E.164 format.
Typical use cases include:
- Sending rich, interactive messages to customers for marketing or transactional purposes.
- Delivering multimedia content or structured message formats like cards and carousels.
- Enhancing customer engagement through advanced messaging features beyond SMS.
For example, a business could use this node to send a promotional carousel showcasing multiple products or a card with detailed information and call-to-action buttons.
Properties
| Name | Meaning |
|---|---|
| To | Recipient phone number in E.164 format (e.g., "5511999999999"). |
| Message Type | Type of RCS message to send. Options: Text, Media, Card, Carousel. |
| Text | The text content to send (only applicable if Message Type is "Text"). |
Output
The node outputs the response from the Yup.chat API after sending the RCS message. The output JSON structure corresponds to the API's response, typically including details about the sent message such as message ID, status, recipient, and any metadata returned by the service.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Yup.chat API.
- The base URL for the Yup.chat API defaults to
https://api.yup.chatbut can be configured via credentials. - Network access to the Yup.chat API endpoint is necessary.
Troubleshooting
- Invalid phone number format: Ensure the "To" property uses the correct E.164 format (country code + number, no spaces or symbols).
- API authentication errors: Verify that the API key credential is correctly set up and has the required permissions.
- Unsupported message type: Confirm that the selected message type matches the provided content fields (e.g., "Text" requires the "Text" field).
- Empty or missing message content: For text messages, the "Text" property must not be empty.
- HTTP request failures: Check network connectivity and Yup.chat service status if requests fail.
If the node throws errors related to HTTP requests or invalid parameters, reviewing the input properties and API credentials usually resolves the issue.
Links and References
- Yup.chat API Documentation (for detailed API usage and message formats)
- RCS Messaging Overview (background on RCS technology)