What do I need to start using blackbaud-automation?

A connected Rube MCP, an active Blackbaud toolkit connection, and the habit of always calling RUBE_SEARCH_TOOLS first.

Do I need API keys or separate credentials?

No. Add the MCP endpoint; authentication is handled via the workflow session and tool schemas. Ensure the Blackbaud connection status is ACTIVE.

How should I handle tool schema changes?

Always re-run RUBE_SEARCH_TOOLS to fetch current schemas before executing tools; avoid hardcoding tool slugs or field names.

blackbaud-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Blackbaud Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/blackbaud

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Blackbaud operations through Composio's Rube MCP toolkit. This skill emphasizes discovering current tool schemas first and securely managing Blackbaud connections before executing tools.

How This Skill Works

It fetches up-to-date tool schemas using RUBE_SEARCH_TOOLS, then ensures an ACTIVE Blackbaud connection via RUBE_MANAGE_CONNECTIONS, and finally runs the selected tool with RUBE_MULTI_EXECUTE_TOOL using the required memory payload. This flow prevents hardcoding and adapts to schema changes.

When to Use It

Automate a recurring Blackbaud workflow by discovering tools and running them in sequence.
When tool schemas change, fetch them via RUBE_SEARCH_TOOLS before execution.
Before any tool run, verify the Blackbaud connection is ACTIVE.
Chain multiple tools in a single session to complete a batch task.
Perform bulk operations using RUBE_REMOTE_WORKBENCH for large datasets.

Quick Start

Step 1: Add the Composio MCP endpoint https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Verify RUBE_SEARCH_TOOLS returns tool slugs and schemas for Blackbaud tasks.
Step 3: Manage the Blackbaud connection and execute a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool slugs and schemas.
Confirm the Blackbaud connection status is ACTIVE with RUBE_MANAGE_CONNECTIONS.
Use exact field names and types from the tool schemas; avoid hardcoding.
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call.
Reuse session IDs within a workflow and manage pagination tokens when present.

Example Use Cases

Automate a donor import by discovering the import tool, connecting, and executing with the required arguments.
Sync updated donor records by discovering the update tool and running it with mapped fields.
Export donor data in bulk using RUBE_REMOTE_WORKBENCH to run multiple tool calls.
Process a batch of records by reusing a session ID across multiple tools.
Diagnose and adapt to schema changes by re-searching tools before each run.

Frequently Asked Questions

Add this skill to your agents