sinch-api-messages-send-carousel

Send RCS carousel messages with multiple rich cards via the Sinch Conversation API.

6|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-carousel-sinch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sinch-api-messages-send-carousel
Source: https://github.com/sinch/sinch-plugins/tree/main/plugins/sinch-antigravity-plugin/skills/sinch-api-messages-send-carousel
Command: npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-messages-send-carousel-sinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sending rich, swipeable carousel messages over RCS requires correctly structuring the Sinch Conversation API carousel_message payload, handling OAuth2 authentication, and managing channel-specific formatting, which is tedious to do by hand. ## Core Features & Use Cases - Carousel Message Sending: Send 2-10 rich cards with titles, descriptions, images, and choice buttons to a recipient's phone number in E.164 format. - Flexible Card Input: Accept cards as an inline JSON array or a path to a JSON file, with validation of required fields. - MCP Fallback Handling: Use the Sinch MCP tool when available, otherwise call the Conversation API directly with CONVERSATION_* environment credentials. - Use Case: A marketing team wants to send a product showcase where recipients swipe through five product cards, each with an image and a "Buy now" button, delivered over RCS. ## Quick Start Ask the assistant to send an RCS carousel to a phone number with your cards defined as a JSON array of titles, descriptions, and image URLs.

Frequently Asked Questions about sinch-api-messages-send-carousel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send an RCS carousel message with Sinch?▼

Provide a recipient phone number in E.164 format and a JSON array of cards with titles, optional descriptions, image URLs, and choices. The skill builds a carousel_message payload and posts it to the Sinch Conversation API messages:send endpoint.

What card fields does the Sinch carousel message support?▼

Each card requires a title and optionally supports a description, an image_url rendered as media_message, and a choices array of objects with text and postback_data. Carousels typically contain 2 to 10 cards depending on channel limits.

Does Sinch carousel messaging work on channels other than RCS?▼

Carousels are best rendered on RCS, which is the primary supported channel. Other channels may receive a simplified version of the carousel content rather than the full swipeable card experience.

Why does the Sinch carousel send fail with a configuration error?▼

The send fails when the CONVERSATION_PROJECT_ID, CONVERSATION_KEY_ID, CONVERSATION_KEY_SECRET, CONVERSATION_REGION, or CONVERSATION_APP_ID environment variables are missing. Set these credentials from your Sinch dashboard before sending.

What happens if the Sinch MCP tool is not available?▼

The skill falls back to calling the Conversation API directly via HTTPS POST to the regional endpoint with OAuth2 authentication. It reads credentials from environment variables and reports a clear error if they are not configured.