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

missive-automation skill

safe

/missive-automation

This skill automates Missive tasks through Rube MCP, prioritizing tool schema discovery to execute up-to-date workflows safely and efficiently.

npx playbooks add skill composiohq/awesome-claude-skills --skill missive-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: missive-automation
description: "Automate Missive tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Missive Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["missive"]
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 Missive-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `missive` |
| 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 Missive tasks through Composio’s Missive toolkit using the Rube MCP gateway. It provides a clear discovery->connect->execute pattern so agents reliably find current tool schemas, manage connections, and run composio tools. The skill emphasizes always searching tools first and validating connections to avoid schema drift and execution errors.

How this skill works

The skill instructs the agent to call RUBE_SEARCH_TOOLS first to retrieve available tool slugs, input schemas, and execution recommendations. It then verifies Missive connection status via RUBE_MANAGE_CONNECTIONS and runs actions with RUBE_MULTI_EXECUTE_TOOL (including a memory object and consistent session IDs). It also covers pagination, bulk operations, and how to fetch full schemas when needed.

When to use it

Automate Missive mailbox and message workflows via Composio tools
Run multi-step Missive operations where exact input schemas are required
Build reliable agents that must adapt to changing tool schemas
Execute bulk or remote workbench operations against Missive
Integrate Missive actions into larger Rube MCP orchestrations

Best practices

Always call RUBE_SEARCH_TOOLS first—never hardcode tool slugs or fields
Confirm toolkit connection is ACTIVE with RUBE_MANAGE_CONNECTIONS before executing
Pass a memory object (even empty {}) in RUBE_MULTI_EXECUTE_TOOL calls
Reuse a session_id for a single workflow; generate a new session for new workflows
Respect schema types and exact field names returned by search results
Handle pagination tokens and iterate until full results are retrieved

Example use cases

Discover available Missive actions and build an execution plan for message routing
Verify and activate a Missive connection, then run a tool to send templated messages
Execute bulk message updates using RUBE_REMOTE_WORKBENCH run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS before constructing complex inputs
Orchestrate multi-step workflows: search tools -> check connection -> multi-execute with session state

FAQ

What is the first API call I should make?

Always call RUBE_SEARCH_TOOLS to get current tool slugs and input schemas for your Missive use case.

Do I need API keys to use Rube MCP?

No API keys are required; add https://rube.app/mcp as an MCP server in your client and use the provided MCP calls.