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 manage Rich Communication Services (RCS) messages, among other messaging resources. Specifically for the RCS Messages - Get Many operation, it retrieves multiple RCS message records from the Yup.chat platform. This is useful for scenarios where you want to fetch a list of RCS messages for analysis, reporting, or further processing within an automation workflow.
Practical examples include:
- Retrieving all RCS messages sent or received within a certain timeframe.
- Fetching a limited number of recent RCS messages for display or logging.
- Applying filters to get messages matching specific criteria such as creation date.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all available RCS messages or limit the number of results returned. |
| Limit | Maximum number of RCS messages to return if "Return All" is false. Range: 1 to 500. |
| Filters | Optional filter parameters to narrow down the results, e.g., filter=created_at:2023-01-01. |
Output
The output is an array of JSON objects representing individual RCS messages retrieved from the Yup.chat API. Each object contains the details of one RCS message as provided by the API response.
If multiple messages are returned, each message is output as a separate item in the node's output array.
The node does not output binary data for this operation.
Dependencies
- Requires an active Yup.chat API key credential configured in n8n.
- The node makes HTTP requests to the Yup.chat API endpoint, defaulting to
https://api.yup.chat. - Proper API authentication via the API key is mandatory for successful requests.
Troubleshooting
Common issues:
- Invalid or missing API key credential will cause authentication failures.
- Incorrect filter syntax may result in empty responses or errors.
- Requesting too many items without setting "Return All" to true may truncate results unexpectedly.
Error messages:
- Authentication errors typically indicate invalid or expired API keys; verify and update credentials.
- HTTP request errors may occur due to network issues or incorrect API endpoint configuration.
- Parsing errors on filters usually mean the filter string format is incorrect; ensure it matches Yup.chat API expectations.
To resolve these, check your API key validity, confirm the filter syntax, and ensure network connectivity to the Yup.chat service.
Links and References
- Yup.chat API Documentation (for detailed API usage and filter syntax)
- n8n Documentation (for general node usage and credential setup)