humanitix-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/humanitix-automation --openclawHumanitix Automation via Rube MCP
Automate Humanitix operations through Composio's Humanitix toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/humanitix
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Humanitix connection via
RUBE_MANAGE_CONNECTIONSwith toolkithumanitix - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkithumanitix - 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: "Humanitix 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 Humanitix task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["humanitix"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Humanitix-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit humanitix |
| 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/humanitix-automation/SKILL.mdView on GitHub Overview
This skill automates Humanitix operations using Composio's Rube MCP toolkit. It emphasizes discovering tool schemas first via RUBE_SEARCH_TOOLS and managing connections with RUBE_MANAGE_CONNECTIONS before executing any workflows, ensuring you always operate with current schemas.
How This Skill Works
Connect to the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS responds, and manage your Humanitix connection with RUBE_MANAGE_CONNECTIONS. Discover available tools for your task, then execute the chosen tool with a schema-compliant argument set using RUBE_MULTI_EXECUTE_TOOL, including a memory object and a session_id. Do not hardcode tool slugs; rely on the discovered schemas and pagination handling if you fetch results in pages.
When to Use It
- Automating a repetitive Humanitix task (e.g., creating events or updating attendees) after confirming current tool schemas.
- When you need to fetch the latest tool schemas before taking action to avoid broken integrations.
- Before any workflow to verify that the Humanitix connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
- For bulk or batch operations using RUBE_REMOTE_WORKBENCH or multiple tool executions in a single session.
- When results are paginated from tool discovery and you need to continue fetching until complete.
Quick Start
- Step 1: Add the MCP server at https://rube.app/mcp to your client configuration.
- Step 2: Run RUBE_SEARCH_TOOLS with a Humanitix use_case to fetch current tool schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS for toolkit 'humanitix', then execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL using a memory payload and the required session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
- Use exact field names and types from the discovered schemas; avoid hardcoding.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and reuse or gracefully close sessions for new workflows.
Example Use Cases
- Discover a Humanitix tool to create an event, connect via RUBE_MANAGE_CONNECTIONS, and execute the tool with the event details using RUBE_MULTI_EXECUTE_TOOL.
- Fetch the latest attendee-update tool, validate the ACTIVE connection, and run the tool to batch-update attendees with a schema-compliant payload.
- Perform a bulk import of attendees through a discovered tool using RUBE_REMOTE_WORKBENCH for scalable execution, ensuring memory parameters are provided.
- List events with pagination by discovering the appropriate tool, handling next-page tokens until all events are retrieved.
- Run a scheduled workflow that checks connection status first, then executes a sequence of tools for end-to-end event management.
