home / skills / composiohq / awesome-claude-skills / sendlane-automation

sendlane-automation skill

safe

/sendlane-automation

This skill automates Sendlane tasks via Rube MCP, ensuring tool schemas are current by always searching tools first.

npx playbooks add skill composiohq/awesome-claude-skills --skill sendlane-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: sendlane-automation
description: "Automate Sendlane tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Sendlane Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/sendlane](https://composio.dev/toolkits/sendlane)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Sendlane connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `sendlane`
- 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.

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

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Sendlane 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 Sendlane task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["sendlane"]
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 Sendlane-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `sendlane` |
| 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](https://composio.dev)*

Overview

This skill automates Sendlane tasks by orchestrating Composio’s Sendlane toolkit through a Rube MCP connection. It provides a repeatable pattern for discovering tools, validating connections, and executing toolkit actions while enforcing schema compliance. Use it to run single or bulk Sendlane operations reliably from an automated workflow agent.

How this skill works

The skill always begins by calling RUBE_SEARCH_TOOLS to fetch current tool slugs, input schemas, and execution recommendations. It verifies or establishes an active Sendlane connection via RUBE_MANAGE_CONNECTIONS, and then runs actions using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH for bulk jobs. The workflow enforces session reuse, memory inclusion, and schema-accurate arguments.

When to use it

Automate campaign creation, update, or deletion in Sendlane
Sync subscriber lists or perform bulk subscriber operations
Trigger Sendlane events from external workflows or agents
Run scheduled or conditional email workflows through Composio tools
When you need schema-driven, auditable automation for Sendlane tasks

Best practices

Always call RUBE_SEARCH_TOOLS first—do not hardcode tool slugs or input fields
Confirm connection status with RUBE_MANAGE_CONNECTIONS and follow the provided auth link if not ACTIVE
Use exact field names and types returned by the tool search; validate payloads before execute calls
Include a memory object (even {}) in every RUBE_MULTI_EXECUTE_TOOL call
Reuse session IDs for a single workflow; generate new session IDs for separate runs
Handle pagination tokens in responses and loop until complete

Example use cases

Add or update subscribers in bulk using a discovered Sendlane bulk import tool
Create or schedule an email campaign by discovering the campaign creation tool and executing with schema-compliant args
Fetch campaign analytics or subscriber activity via tools found with RUBE_SEARCH_TOOLS and aggregate results
Run a remote workbench job to apply tags or automate lifecycle emails across multiple lists
Onboard a new account: connect Sendlane, verify ACTIVE status, then run initial setup scripts

FAQ

Do I need API keys to use Rube MCP?

No. Add the MCP endpoint (https://rube.app/mcp) to your client configuration; Rube MCP works without separate API keys for tool discovery and orchestration.

What if a tool schema changes mid-workflow?

Always call RUBE_SEARCH_TOOLS before executing. If schemas change, update your arguments to match the returned schema and restart the execution with the correct session flow.