What is this skill for?

It automates Sendbird operations through Composio's toolkit using Rube MCP to fetch up-to-date tool schemas and execute tasks.

Do I need API keys to use it?

No API keys are required. You connect via a Rube MCP server and manage the Sendbird connection through RUBE_MANAGE_CONNECTIONS.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to fetch current schemas before executing tools; avoid hardcoding tool slugs or arguments and include memory in multi-execute calls.

sendbird-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/sendbird-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Sendbird Automation via Rube MCP

Automate Sendbird operations through Composio's Sendbird toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/sendbird

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Sendbird connection via RUBE_MANAGE_CONNECTIONS with toolkit sendbird
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit sendbird
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Sendbird operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Sendbird task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["sendbird"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Sendbird-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `sendbird`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/sendbird-automation/SKILL.mdView on GitHub

Overview

Automate Sendbird operations through Composio's toolkit using Rube MCP. The workflow starts by discovering current tool schemas with RUBE_SEARCH_TOOLS, then establishing and verifying a Sendbird connection before executing tools. Keeping tool schemas fresh ensures compatibility with changes.

How This Skill Works

Begin by discovering available Sendbird tools with RUBE_SEARCH_TOOLS using a Sendbird use_case. Then verify the Sendbird connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE. Finally, execute the chosen tools with RUBE_MULTI_EXECUTE_TOOL, supplying the discovered schema fields and a memory object.

When to Use It

Automating routine Sendbird operations (channel management, messaging) using the latest tool schemas.
Setting up a new Sendbird integration or workflow when first connecting to Sendbird.
Adapting to tool API changes by re-fetching current schemas before running tasks.
Verifying the connection is ACTIVE before any workflow execution.
Running multi-tool sequences that benefit from session reuse and memory across steps.

Quick Start

Step 1: Configure Rube MCP by adding https://rube.app/mcp as an MCP server in your client and verify RUBE_SEARCH_TOOLS responds.
Step 2: Manage the Sendbird connection with RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE.
Step 3: Discover the required Sendbird tools with RUBE_SEARCH_TOOLS and execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL, including the necessary arguments and a memory object.

Best Practices

Always search tools first to obtain current schemas; do not hardcode slugs or args.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before execution.
Use exact field names and types from the search results.
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty).
Reuse session IDs within a workflow; generate new IDs for separate workflows.

Example Use Cases

Onboard a new Sendbird project: discover tools, connect, then run an initial setup tool.
Automate a welcome message sequence for new Sendbird users by discovering and executing a messaging tool.
Create multiple channels for a product launch by discovering a channel-management tool and issuing bulk create commands.
Synchronize user attributes daily by discovering and executing a user-metadata update tool, reusing session.
Migrate data between environments by reusing session IDs and chaining discovered tools, handling pagination if needed.

Frequently Asked Questions

Add this skill to your agents