Raisely Automation

What This Skill Does

• This skill automates Raisely operations using Composio's Raisely toolkit via Rube MCP.
• It allows users to streamline tasks within Raisely by discovering available tools, managing connections, and executing workflows.
• It's designed for those who want to automate Raisely tasks.

When to Use

• Automate user creation in Raisely.
• Update donation records automatically.
• Sync Raisely data with other systems.
• Trigger actions based on Raisely events.
• Generate reports from Raisely data.
• Manage Raisely campaigns programmatically.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Raisely connection.
• Provides tools for various Raisely operations.
• Emphasizes the importance of checking connection status.
• Uses RUBE_SEARCH_TOOLS to find available tools.
• Requires schema-compliant arguments for tool execution.

Manual Installation

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

Toolkit docs: composio.dev/toolkits/raisely

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["raisely"] 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