Rube MCP is Composio's MCP framework that lets you discover, manage, and execute tools for connected services like Connecteam.

Do I need API keys to use Connecteam automation?

No API keys are required. You add the MCP endpoint and rely on RUBE_SEARCH_TOOLS and the integrated tool schemas.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and input schemas; avoid hardcoding slugs or arguments and adapt workflows to the latest schema.

connecteam-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Connecteam Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/connecteam

Prerequisites

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

Step 2: Check Connection

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

Overview

Connecteam Automation via Rube MCP lets you orchestrate Connecteam tasks through Composio's toolkit. It relies on dynamic tool discovery, connection management, and safe execution within Rube MCP. Always fetch current tool schemas before running automation to avoid hardcoding slugs or args.

How This Skill Works

The workflow starts by calling RUBE_SEARCH_TOOLS to fetch available Connecteam tool slugs and input schemas. Next, it checks the connection status with RUBE_MANAGE_CONNECTIONS and ensures the toolkit connection is ACTIVE. Finally, it executes the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the discovered slug, memory, and session_id; this keeps executions schema-compliant and resumable.

When to Use It

Automating routine Connecteam operations with up-to-date tool schemas.
Integrating Connecteam tasks into larger Composio workflows using Rube MCP.
Verifying an ACTIVE connection before executing tools to avoid failures.
Onboarding a new Connecteam automation that requires fresh tool discovery.
Processing bulk or multi-step Connecteam operations within a controlled session.

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) to your client configuration and verify RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_SEARCH_TOOLS with a Connecteam use_case to discover tool slugs and schemas.
Step 3: Execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug, memory, and a valid session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current schemas.
Check RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results; avoid hardcoding.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow and handle pagination tokens if present.

Example Use Cases

Auto-create new Connecteam employees when a new hire is added in the HR system, using a discovered tool slug and mapped fields.
Submit daily timesheet approvals for a team by discovering the appropriate tool and executing with the latest schema.
Update an employee profile in Connecteam from an external data source, ensuring field names match the tool schema.
Retrieve department shift schedules and push updates to a dashboard or notification feed.
Run bulk Connecteam operations via RUBE_REMOTE_WORKBENCH to process multiple tasks in one workflow.

Frequently Asked Questions

Add this skill to your agents