home / skills / composiohq / awesome-claude-skills / payhip-automation
/payhip-automation
This skill automates Payhip tasks via Composio's Rube MCP toolkit, discovering current tool schemas before execution to ensure accurate workflow automation.
npx playbooks add skill composiohq/awesome-claude-skills --skill payhip-automationReview the files below or copy the command above to add this skill to your agents.
---
name: payhip-automation
description: "Automate Payhip tasks via Rube MCP (Composio). Always search tools first for current schemas."
requires:
mcp: [rube]
---
# Payhip Automation via Rube MCP
Automate Payhip operations through Composio's Payhip toolkit via Rube MCP.
**Toolkit docs**: [composio.dev/toolkits/payhip](https://composio.dev/toolkits/payhip)
## Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Payhip connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `payhip`
- 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 `payhip`
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: "Payhip 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 Payhip task"}]
session: {id: "existing_session_id"}
```
### Step 2: Check Connection
```
RUBE_MANAGE_CONNECTIONS
toolkits: ["payhip"]
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 Payhip-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `payhip` |
| 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)*
This skill automates Payhip tasks by orchestrating Composio's Payhip toolkit via a Rube MCP (Composio) connection. It guides discovery of current tool schemas, manages Payhip connections, and executes Payhip operations reliably using RUBE_* calls. The skill enforces schema compliance, session reuse, and safe execution patterns for production automation.
The skill always begins by calling RUBE_SEARCH_TOOLS to discover available Payhip tool slugs, input schemas, and recommended execution plans. It verifies or establishes an active Payhip connection via RUBE_MANAGE_CONNECTIONS, then runs actions using RUBE_MULTI_EXECUTE_TOOL (including the required memory field) or RUBE_REMOTE_WORKBENCH for bulk jobs. It handles pagination, session IDs, and schema-driven arguments to avoid runtime errors.
Do I need API keys to use Rube MCP?
No API keys are required; add the MCP endpoint (https://rube.app/mcp) in your client configuration and use the RUBE_* calls.
What if tool schemas change mid-workflow?
Always call RUBE_SEARCH_TOOLS before each workflow or whenever you resume; adjust arguments to exactly match the latest schema returned.