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

poptin-automation skill

safe

/poptin-automation

This skill automates Poptin tasks via Rube MCP, discovering current tool schemas first to ensure accurate tool execution.

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

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

Files (1)

SKILL.md

2.8 KB

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

# Poptin Automation via Rube MCP

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

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["poptin"]
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 Poptin-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `poptin` |
| 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 Poptin tasks by orchestrating Composio's Poptin toolkit through Rube MCP. It provides an operational pattern to discover available tools, verify connections, and execute Composio tools reliably. The skill emphasizes always searching for current tool schemas before any execution and reusing session context across workflows.

How this skill works

First, call RUBE_SEARCH_TOOLS to retrieve available tool slugs, input schemas, execution plans, and pagination tokens. Then verify Poptin connection status with RUBE_MANAGE_CONNECTIONS and follow any auth links until the connection is ACTIVE. Finally, run one or more tools with RUBE_MULTI_EXECUTE_TOOL (including a memory object and session_id) or use RUBE_REMOTE_WORKBENCH for bulk jobs. Always use the exact field names and types returned by the search schema.

When to use it

Automating Poptin campaign creation, editing, or reporting via Composio.
Integrating Poptin operations into larger Claude agent workflows.
Running bulk or scheduled Poptin operations from a remote workbench.
When tool schemas may change and you need runtime discovery.
When you require reliable session and connection management for multi-step flows.

Best practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool slugs and schemas; never hardcode them.
Check RUBE_MANAGE_CONNECTIONS and ensure the Poptin toolkit shows ACTIVE before executing any tools.
Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls (use {} if empty).
Reuse session_id for related workflow steps; generate a new session for separate workflows.
Handle pagination tokens from search results and GET_SCHEMA responses to fetch complete data.

Example use cases

Discover Poptin form-creation tool and execute it with schema-compliant arguments to deploy a new popup.
Check connection status, then export Poptin campaign metrics by invoking the reporting tool returned by search.
Run bulk updates across multiple Poptin campaigns using RUBE_REMOTE_WORKBENCH and run_composio_tool().
Automate onboarding: detect required auth steps with RUBE_MANAGE_CONNECTIONS and prompt user to complete authorization.
Build a multi-step workflow that searches tools, runs a create action, then fetches the created object schema for verification.

FAQ

What is the first call I must make when using this skill?

Always call RUBE_SEARCH_TOOLS to discover current tool slugs and input schemas before any other action.

What if the Poptin connection is not ACTIVE?

Call RUBE_MANAGE_CONNECTIONS for the toolkit, follow the returned auth link to complete setup, then confirm ACTIVE before proceeding.