Get the FREE Ultimate OpenClaw Setup Guide →

payhip-automation

npx machina-cli add skill ComposioHQ/awesome-claude-skills/payhip-automation --openclaw
Files (1)
SKILL.md
2.8 KB

Payhip Automation via Rube MCP

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

Toolkit docs: 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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Payhip-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit payhip
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/payhip-automation/SKILL.mdView on GitHub

Overview

Automates Payhip operations through Composio's Payhip toolkit via Rube MCP. It guides you to discover current tool schemas with RUBE_SEARCH_TOOLS and verify an ACTIVE Payhip connection with RUBE_MANAGE_CONNECTIONS before running workflows.

How This Skill Works

First discover available Payhip tools using RUBE_SEARCH_TOOLS. Then verify the Payhip connection with RUBE_MANAGE_CONNECTIONS, and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload as required. Tool schemas are dynamic, so never hardcode slugs or arguments.

When to Use It

  • When you need end-to-end automation of Payhip operations via MCP
  • When tool schemas change, requiring up-to-date discovery before execution
  • When coordinating multiple Payhip workflows across sessions
  • When validating the Payhip connection is ACTIVE before actions
  • When performing bulk Payhip operations with automated execution plans

Quick Start

  1. Step 1: Ensure Rube MCP is available by running RUBE_SEARCH_TOOLS
  2. Step 2: Run RUBE_MANAGE_CONNECTIONS for toolkit 'payhip' and authenticate if prompted
  3. Step 3: Discover tools with RUBE_SEARCH_TOOLS, then use RUBE_MULTI_EXECUTE_TOOL with memory and a valid session_id

Best Practices

  • Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
  • Check RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools
  • Use exact field names and types from search results
  • Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
  • Reuse session IDs for related tasks; start new ones for new workflows

Example Use Cases

  • Automate publishing a new Payhip product using discovered tool and dynamic schema
  • Update Payhip product prices by discovering the price tool and executing with memory
  • Bulk create discount codes via a Payhip tool
  • Fetch Payhip sales reports and export to a dashboard
  • Synchronize Payhip orders with an external CRM using the multi-execute pattern

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers