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

SKILL

resend-automation

Automate Resend operations through Rube MCP using current tool schemas.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityLow risk

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

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 "resend-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/resend-automation/SKILL.md
2. Save it as ~/.claude/skills/resend-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// use cases

Connect an AI assistant to Resend workflows

After connecting Rube MCP in an AI client, a developer can discover available tools first and then run Resend actions, reducing failures caused by schema changes.

Validate connection and parameters before execution

Before running any Resend automation, users can verify that the resend connection is ACTIVE and build arguments according to the fields returned by tool discovery.

Manage multi-step operations with a shared session

When a Resend flow includes discovery, connection checks, and execution, the same session ID can be reused to keep the workflow context consistent.

// docs

AI summary

The document explains how to automate Resend operations through Rube MCP using Composio’s Resend toolkit. It covers prerequisites, connection setup and activation, tool discovery with RUBE_SEARCH_TOOLS, and the standard execution flow with RUBE_MULTI_EXECUTE_TOOL. It also highlights key pitfalls such as always searching first for current schemas, verifying ACTIVE connection status, including the memory parameter, and reusing session IDs within a workflow.

Show full docs ▾

Resend Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/resend

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["resend"]
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 Resend-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `resend`
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 does this skill do?

It uses Rube MCP to access Composio’s Resend toolkit and automate Resend-related operations. The docs emphasize searching for tools first and executing against the latest schema.

What prerequisites are required?

You need Rube MCP connected and RUBE_SEARCH_TOOLS available. You also need to set up and activate a resend connection through RUBE_MANAGE_CONNECTIONS.

Why should I search tools first every time?

Because tool schemas can change, the docs explicitly advise against hardcoding tool slugs or arguments. You should call RUBE_SEARCH_TOOLS first to get current tools and exact fields.

Automate Respond.io tasks through Rube MCP to streamline customer communication workflows.

ComposioGet→

$ loading_