Appsflyer Automation

What This Skill Does

The Appsflyer Automation skill allows users to automate operations within Appsflyer through Composio's Appsflyer toolkit, utilizing Rube MCP. It streamlines tasks related to mobile attribution and marketing analytics. This skill is designed for marketers and developers who want to automate Appsflyer workflows.

When to Use

• Discover available Appsflyer tools.
• Check the status of the Appsflyer connection.
• Execute specific Appsflyer tools.
• Automate campaign performance analysis.
• Manage attribution settings programmatically.
• Retrieve and process Appsflyer data.

Key Features

• Automates Appsflyer tasks via Rube MCP.
• Uses Composio's Appsflyer toolkit.
• Requires an active Appsflyer connection.
• Discovers tools dynamically using RUBE_SEARCH_TOOLS.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

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

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

Toolkit docs: composio.dev/toolkits/appsflyer

Quick Reference