rippling-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/rippling-automation --openclawRippling Automation via Rube MCP
Automate Rippling operations through Composio's Rippling toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/rippling
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Rippling connection via
RUBE_MANAGE_CONNECTIONSwith toolkitrippling - 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 toolkitrippling - 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: "Rippling 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 Rippling task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["rippling"]
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 Rippling-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit rippling |
| 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/rippling-automation/SKILL.mdView on GitHub Overview
Automate Rippling operations through Composio's Rippling toolkit via Rube MCP. It relies on live tool schemas discovered with RUBE_SEARCH_TOOLS to keep automations up to date. Prerequisites include an active Rube MCP connection and a Rippling connection configured for the rippling toolkit.
How This Skill Works
Discover available Rippling tools with RUBE_SEARCH_TOOLS, then verify and manage the connection with RUBE_MANAGE_CONNECTIONS. When ready, execute a tool using RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and schema-compliant arguments, always including a memory object and a session_id for continuity.
When to Use It
- Automating common Rippling tasks such as employee provisioning, attribute updates, or terminations.
- When tool schemas change and you need up-to-date input schemas (instead of hardcoding slugs or fields).
- Coordinating multiple Rippling actions within a single workflow using a shared session.
- Before performing any Rippling operation to verify the connection is ACTIVE.
- Executing bulk Rippling updates across many employees using multi-tool or remote bench workflows.
Quick Start
- Step 1: Get Rube MCP set up and verify RUBE_SEARCH_TOOLS responds.
- Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit 'rippling' and ensure ACTIVE.
- Step 3: Discover a tool with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always search first for current tool schemas; never hardcode tool slugs or arguments.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results to ensure schema compliance.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
- Reuse session IDs within a workflow and generate new ones for new workflows.
Example Use Cases
- Create a new Rippling employee with required fields pulled from the current schema.
- Update an employee's department, title, or manager using the discovered tool.
- Add or modify health benefits for a user based on the latest Rippling tool input.
- Terminate an employee in Rippling and log the action within the same session.
- Perform a bulk update (e.g., policy or status changes) across multiple employees.
