How does Appsflyer automation via Rube MCP work?

It uses RUBE_SEARCH_TOOLS to discover tool slugs and schemas, then RUBE_MANAGE_CONNECTIONS to ensure a valid Appsflyer connection, and finally RUBE_MULTI_EXECUTE_TOOL to run tools with schema-aligned arguments.

Do I always need an ACTIVE Appsflyer connection?

Yes. You must have an ACTIVE connection established via RUBE_MANAGE_CONNECTIONS with the toolkit set to appsflyer before executing any tools.

What should I do if tool schemas change?

Always search for tools first to fetch the current slugs and input shapes; do not hardcode slugs or argument names.

appsflyer-automation

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

Files (1)

SKILL.md

2.9 KB

Appsflyer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/appsflyer

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Appsflyer operations through Composio's Appsflyer toolkit via Rube MCP. This enables discovering current tool schemas, managing connections, and securely executing AppsFlyer tasks in automated workflows.

How This Skill Works

The workflow starts by discovering available Appsflyer tools with RUBE_SEARCH_TOOLS, then verifying and activating the Appsflyer connection using RUBE_MANAGE_CONNECTIONS, and finally executing the chosen tool via RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and schema-aligned arguments.

When to Use It

When you need to automate a recurring Appsflyer task (reports, exports) using tool schemas.
When onboarding a new AppsFlyer workflow and you must fetch current tool slugs first.
When validating the Appsflyer connection is ACTIVE before execution.
When performing bulk Appsflyer operations in a single workflow using multiple tools.
When iterating through paginated tool schemas to ensure full coverage.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and run RUBE_SEARCH_TOOLS to verify tool schemas.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["appsflyer"] and ensure the Appsflyer connection is ACTIVE.
Step 3: Execute the desired tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and arguments, including memory: {}.

Best Practices

Always search for tool schemas before execution to get current slugs and arguments.
Check that the Appsflyer connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
Use exact field names and types from the search results; avoid hardcoding.
Include the memory parameter in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow to optimize performance and avoid unnecessary restarts.

Example Use Cases

Discover the Appsflyer operation tool with RUBE_SEARCH_TOOLS, then run it with RUBE_MULTI_EXECUTE_TOOL using the returned slug and required arguments.
Establish an ACTIVE Appsflyer connection via RUBE_MANAGE_CONNECTIONS before executing any tools in a workflow.
Perform a bulk operation by chaining multiple tool executions in a single workflow using RUBE_MULTI_EXECUTE_TOOL.
After updating tool schemas, re-run RUBE_SEARCH_TOOLS to fetch current slugs and input shapes for subsequent runs.
Reuse an existing session_id across steps in a single automation to improve efficiency.

Frequently Asked Questions

Add this skill to your agents