home / skills / composiohq / awesome-claude-skills / rippling-automation

rippling-automation skill

safe

/rippling-automation

This skill helps automate Rippling tasks by discovering current tool schemas via Rube MCP before executing workflows, ensuring correct inputs.

npx playbooks add skill composiohq/awesome-claude-skills --skill rippling-automation

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.9 KB

---
name: rippling-automation
description: "Automate Rippling tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
  mcp: [rube]
---

# Rippling Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/rippling](https://composio.dev/toolkits/rippling)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Rippling connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `rippling`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `rippling`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. 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_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 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](https://composio.dev)*

Overview

This skill automates Rippling tasks by orchestrating Composio's Rippling toolkit through a Rube MCP server. It provides a repeatable workflow pattern: discover tools, validate connections, and execute operations using the current tool schemas. The skill emphasizes safety by always searching tools first and reusing session context for multi-step workflows.

How this skill works

Before any action, the skill calls RUBE_SEARCH_TOOLS to fetch available tool slugs, input schemas, recommended plans, and pagination tokens. It then validates an active Rippling connection via RUBE_MANAGE_CONNECTIONS. Executions run through RUBE_MULTI_EXECUTE_TOOL (or RUBE_REMOTE_WORKBENCH for bulk jobs) using schema-compliant arguments and an explicit memory object. Session IDs are created once per workflow and reused for related calls.

When to use it

Automating employee onboarding, offboarding, or profile updates in Rippling
Running bulk HR or payroll changes that require Composio tool orchestration
Integrating Rippling tasks into larger agent-driven workflows
When tool schemas may change frequently and you need the latest contract
Executing multi-step automations that must preserve context across calls

Best practices

Always call RUBE_SEARCH_TOOLS first to retrieve current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE for the rippling toolkit before executing
Use exact field names and types from returned schemas; do not hardcode arguments
Include a memory object (can be {}) on RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow; generate new session IDs for new workflows
Handle pagination tokens returned by searches to fetch all results

Example use cases

Onboard a new hire: discover the onboarding tool, confirm connection, then execute steps to create employee profile and assign payroll
Bulk update employee custom fields using RUBE_REMOTE_WORKBENCH to run composio tools across many records
Automate termination flows by locating termination-related tools and executing them in sequence with session context
Fetch full tool schemas via RUBE_GET_TOOL_SCHEMAS before building a UI or external integration
Recover from partial failures by reusing the same session ID and replaying remaining steps

FAQ

Do I need API keys to use Rube MCP?

No. Add https://rube.app/mcp as an MCP server in your client configuration; no API keys are required.

What if a tool schema changed since my last run?

Call RUBE_SEARCH_TOOLS at the start of the workflow to retrieve the latest schema and adjust arguments before execution.