Do I need API keys to use Raisely automation?

No API keys are needed. Add the Rube MCP endpoint (https://rube.app/mcp) as a server and ensure the Raisely connection is ACTIVE; RUBE_SEARCH_TOOLS fetches latest tool schemas.

Why must I always call RUBE_SEARCH_TOOLS first?

Tool schemas change over time. Discovering them prevents hardcoding slugs or arguments and keeps workflows up to date.

What if tool schemas change during a workflow?

Re-run discovery to obtain updated tool slugs and argument shapes, then adjust the execute step accordingly and continue with a new session or same session as appropriate.

raisely-automation

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

Files (1)

SKILL.md

2.9 KB

Raisely Automation via Rube MCP

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

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Raisely-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `raisely`
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/raisely-automation/SKILL.mdView on GitHub

Overview

Automates Raisely operations through Composio's Raisely toolkit via Rube MCP. Begin by discovering current tool schemas with RUBE_SEARCH_TOOLS, then connect and execute using the discovered tool slugs for repeatable Raisely tasks.

How This Skill Works

The workflow starts by discovering available Raisely tools and their input schemas with RUBE_SEARCH_TOOLS, then validates the Raisely connection using RUBE_MANAGE_CONNECTIONS. Finally, it executes the chosen tool with RUBE_MULTI_EXECUTE_TOOL using a session_id and memory payload, adhering to the exact field names and types returned by the tool schemas.

When to Use It

Automate Raisely operations (campaign updates, donor sync, and other tasks) without manual UI steps.
When tool schemas change—pull the latest schemas via RUBE_SEARCH_TOOLS before running workflows.
Before any Raisely workflow, verify the connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS.
Build repeatable Raisely data workflows that reuse session IDs for related tasks.
Handle large datasets or paginated results by continuing fetches until completion and following pagination tokens.

Quick Start

Step 1: RUBE_SEARCH_TOOLS with a Raisely use_case to discover tool_slugs and input schemas.
Step 2: RUBE_MANAGE_CONNECTIONS for toolkits: ["raisely"] and confirm ACTIVE status.
Step 3: RUBE_MULTI_EXECUTE_TOOL using a discovered tool_slug, the required arguments, memory: {}, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types as provided by the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs where appropriate and manage pagination tokens when they appear.

Example Use Cases

Discover a Raisely tool for updating a campaign's target and execute it with the required arguments from the schema.
Sync donor records from an external system into Raisely using a discovered import tool and verified arguments.
Retrieve campaign performance metrics by calling a tool discovered via RUBE_SEARCH_TOOLS and parsing the results.
Bulk add subscribers to a Raisely list using a discovered tool slug and provided input schema.
Run a multi-step Raisely workflow within a single active session to ensure continuity and reuse.

Frequently Asked Questions

Add this skill to your agents