sap-successfactors-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/sap-successfactors-automation --openclawSAP SuccessFactors Automation via Rube MCP
Automate SAP SuccessFactors operations through Composio's SAP SuccessFactors toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/sap_successfactors
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active SAP SuccessFactors connection via
RUBE_MANAGE_CONNECTIONSwith toolkitsap_successfactors - 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 toolkitsap_successfactors - 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: "SAP SuccessFactors 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 SAP SuccessFactors task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["sap_successfactors"]
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 SAP SuccessFactors-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit sap_successfactors |
| 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/sap-successfactors-automation/SKILL.mdView on GitHub Overview
Automate SAP SuccessFactors operations through Composio's SAP SuccessFactors toolkit via Rube MCP. This skill emphasizes always searching for current tool schemas before execution to ensure accuracy. It orchestrates discovery, connection management, and tool execution to streamline HR workflows.
How This Skill Works
The workflow begins by calling RUBE_SEARCH_TOOLS to fetch current SAP SuccessFactors tool slugs and input schemas. It then uses RUBE_MANAGE_CONNECTIONS to ensure an ACTIVE connection for the sap_successfactors toolkit. Finally, it executes the chosen tools with RUBE_MULTI_EXECUTE_TOOL, including a memory object, and reuses session IDs as needed while honoring up-to-date schemas.
When to Use It
- To perform recurring SAP SuccessFactors operations (via SF toolkit) without manual steps
- When tool schemas or slugs change and you must fetch the latest definitions
- During initial setup of a SAP SuccessFactors automation workflow
- When validating a connection status before running workflows
- When executing multiple SF tasks in a single session using memory context
Quick Start
- Step 1: Get Rube MCP ready by adding https://rube.app/mcp as an MCP server in your client configuration
- Step 2: Run RUBE_SEARCH_TOOLS for SAP SuccessFactors to fetch current tool slugs and schemas
- Step 3: Use RUBE_MANAGE_CONNECTIONS to activate the sap_successfactors toolkit, then execute tools with RUBE_MULTI_EXECUTE_TOOL including memory and a session_id
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas
- Verify RUBE_MANAGE_CONNECTIONS returns ACTIVE before executing tools
- Use exact field names/types from search results; do not hardcode slugs
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
- Reuse session IDs within a workflow and handle pagination when needed
Example Use Cases
- Automate creating a new employee record in SAP SuccessFactors using a discovered tool slug and its schema
- Update an employee's job data (title, department) via an available SF tool after schema discovery
- Sync onboarding tasks for a batch of hires by executing multiple SF operations in sequence
- Bulk update payroll or compensation data by chaining tools with a shared session
- Periodically verify and refresh the SAP SF connection status within an automated workflow