Do I need API keys or credentials?

No API keys are needed — just add the Rube MCP endpoint (https://rube.app/mcp) and connect via RUBE_MANAGE_CONNECTIONS.

How do I ensure I have the latest tool schemas?

Always call RUBE_SEARCH_TOOLS before executing workflows to fetch current tool slugs and input schemas.

What if a tool schema changes or a tool slug is missing?

Re-run RUBE_SEARCH_TOOLS to refresh the available tools and update your workflow accordingly.

poptin-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/poptin-automation --openclaw

Files (1)

SKILL.md

2.8 KB

Poptin Automation via Rube MCP

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

Toolkit docs: 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit poptin
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/poptin-automation/SKILL.mdView on GitHub

Overview

This skill automates Poptin operations through Composio's Poptin toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch up-to-date tool schemas and requires an active Poptin connection. By discovering tools first, it avoids broken slugs and ensures reliable automation workflows.

How This Skill Works

It discovers available Poptin tools and their input schemas using RUBE_SEARCH_TOOLS, then verifies the connection with RUBE_MANAGE_CONNECTIONS. Once active, it executes chosen tools via RUBE_MULTI_EXECUTE_TOOL, always including a memory object and a session_id for continuity.

When to Use It

You want to automate a Poptin task end-to-end using Composio tooling.
Tool schemas change, so you fetch current slugs before running.
You need to verify the Poptin connection is ACTIVE before execution.
You want to run multiple Poptin tools in a single workflow (bulk ops).
You want to reuse a session ID to maintain flow continuity across steps.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify RUBE_SEARCH_TOOLS responds.
Step 2: Discover tools with RUBE_SEARCH_TOOLS using a Poptin use_case to obtain tool slugs and schemas.
Step 3: Execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, providing memory, session_id, and ensuring the connection is ACTIVE.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Use exact field names and types from the tool schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow to maintain continuity.

Example Use Cases

Automatically deploy a Poptin popup when a user triggers a web event.
Discover tools, select a slug, and execute a Poptin optimization task across sites.
Validate updated tool schemas and run a test execution with a sample payload.
Bulk-configure several Poptin widgets across multiple sites via bulk ops.
Reconnect and retry after an ACTIVE check fails, then resume workflow.

Frequently Asked Questions

Add this skill to your agents