$ ~/registry/skill/composiohq-composio-skills-sendloop-automation

SKILL

sendloop-automation

Automate Sendloop tasks through Rube MCP with tool discovery first.

Stars

★ 73,862

Source

GitHub

Updated

2026-08-29

// securityLow risk

Prompt only, no code
Open source
Community-trusted· 73.9k

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "sendloop-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/sendloop-automation/SKILL.md
2. Save it as ~/.claude/skills/sendloop-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Marketing team automates Sendloop workflows

When marketers want AI to handle repetitive Sendloop operations, they can use Rube MCP to discover the right tools first and then run the workflow. This reduces manual parameter lookup and repetitive work.

Developers integrate Sendloop automation

After connecting Rube MCP in a client, developers can follow the documented pattern: discover tool schemas, verify the connection, and then execute Sendloop tools. This is useful when schemas may change over time.

Validate connection and parameters before execution

Before running a Sendloop workflow, users can confirm the connection is ACTIVE and use exact field names and types from the discovered schemas. This reduces failures caused by incomplete setup or argument mismatches.

// docs

AI summary

The README explains how to automate Sendloop operations through Composio's toolkit via Rube MCP. It covers prerequisites, connection and authorization steps, and the recommended workflow: search tools first, verify the Sendloop connection, then execute with schema-compliant arguments. It also highlights common pitfalls such as changing schemas, required memory fields, session reuse, and pagination handling.

Show full docs ▾

Sendloop Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/sendloop

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Sendloop connection via RUBE_MANAGE_CONNECTIONS with toolkit sendloop
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 sendloop
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: "Sendloop 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 Sendloop task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["sendloop"]
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 Sendloop-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `sendloop`
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

// FAQ

What prerequisites are required before using this skill?

You need Rube MCP connected and `RUBE_SEARCH_TOOLS` available first. You also need an active Sendloop connection set up through `RUBE_MANAGE_CONNECTIONS`.

Why does the documentation insist on searching tools first?

Because tool slugs, input fields, and schemas may change, the docs explicitly say not to hardcode them. Calling `RUBE_SEARCH_TOOLS` first gives you the current tools, schemas, and known pitfalls.

Do I need an API key to use Rube MCP?

The docs say no API key is needed when adding `https://rube.app/mcp` as the MCP server endpoint. However, you still need to authorize the sendloop toolkit connection and confirm it is ACTIVE.

Automate Resend operations through Rube MCP using current tool schemas.

ComposioGet→

$ loading_