What is tapfiliate-automation?

A workflow that automates Tapfiliate tasks using the Rube MCP, Composio toolkit, and the RUBE toolchain.

What are the prerequisites?

Rube MCP connected (RUBE_SEARCH_TOOLS available), and an active Tapfiliate connection via RUBE_MANAGE_CONNECTIONS with toolkit 'tapfiliate'.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Fetching current tool slugs and arguments ensures compatibility and prevents errors.

tapfiliate-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Tapfiliate Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tapfiliate

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["tapfiliate"]
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 Tapfiliate-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `tapfiliate`
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/tapfiliate-automation/SKILL.mdView on GitHub

Overview

Tapfiliate Automation via Rube MCP orchestrates Tapfiliate operations using Composio's toolkit. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas before every workflow, and requires an active Tapfiliate connection. The setup ensures you never hardcode tool slugs or args and always validate connectivity.

How This Skill Works

Start by discovering available tools with RUBE_SEARCH_TOOLS using a Tapfiliate use_case, then verify the connection with RUBE_MANAGE_CONNECTIONS. Finally execute a tool via RUBE_MULTI_EXECUTE_TOOL, passing the discovered args and a memory payload; ensure the session ID is reused within a workflow and that memory is included in every call.

When to Use It

Automating recurring Tapfiliate operations (e.g., weekly reports or campaigns)
When tool schemas are likely to change and you must fetch current slugs and arguments
When you need to validate an authenticated Tapfiliate connection before executing tasks
For batch/bulk operations using RUBE_REMOTE_WORKBENCH or multi-tool execution
When you want to reuse session IDs across related workflows to maintain continuity

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds and discover Tapfiliate tool schemas
Step 3: Connect to Tapfiliate with RUBE_MANAGE_CONNECTIONS and execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas; never hardcode slugs or args
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results; avoid guesswork
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

Discover a Tapfiliate tool for creating a new referral campaign and run it with the provided args
Connect to Tapfiliate via RUBE_MANAGE_CONNECTIONS and perform a bulk update of affiliate commissions
Validate the connection, fetch a referral report, and export results using RUBE_MULTI_EXECUTE_TOOL
Batch multiple Tapfiliate tools via RUBE_REMOTE_WORKBENCH run_composio_tool() for quarterly ops
Handle pagination tokens when listing campaigns or reports until all results are retrieved

Frequently Asked Questions

Add this skill to your agents