What is required to run veriphone-automation?

Rube MCP must be connected, a Veriphone connection must be ACTIVE via RUBE_MANAGE_CONNECTIONS, and you must call RUBE_SEARCH_TOOLS first to obtain current tool schemas.

How do I discover available Veriphone tools?

Use RUBE_SEARCH_TOOLS with a use_case like Veriphone operations to return tool slugs, input schemas, and recommended execution plans.

What should I include when executing tools?

Include the discovered tool_slug, the exact schema-compliant arguments, memory (even if empty), and a valid session_id in RUBE_MULTI_EXECUTE_TOOL.

veriphone-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/veriphone-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Veriphone Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/veriphone

Prerequisites

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

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit veriphone
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: "Veriphone 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 Veriphone task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["veriphone"]
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 Veriphone-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `veriphone`
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/veriphone-automation/SKILL.mdView on GitHub

Overview

Automate Veriphone operations through Composio's Veriphone toolkit via Rube MCP. This skill emphasizes always searching for current tool schemas first to avoid stale slugs or arguments and ensures a reliable, repeatable workflow.

How This Skill Works

Use RUBE_SEARCH_TOOLS to fetch available Veriphone tool slugs and schemas, then ensure an ACTIVE Veriphone connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload and session_id, reusing sessions across related tasks when appropriate.

When to Use It

You need to automate Veriphone tasks end-to-end using MCP.
Tool schemas may change, so you must fetch current slugs and schemas before running.
You must verify the Veriphone connection is ACTIVE before executing workflows.
Running multiple Veriphone actions in a single, connected session.
Performing bulk or bulk-like Veriphone operations via RUBE_REMOTE_WORKBENCH or run_composio_tool.

Quick Start

Step 1: Verify Rube MCP is available by calling RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["veriphone"] and ensure the status is ACTIVE.
Step 3: Discover tools and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas.
Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools.
Follow 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 but generate new ones for separate workflows.

Example Use Cases

Discover available Veriphone tools with RUBE_SEARCH_TOOLS and execute a tool slug from the results using RUBE_MULTI_EXECUTE_TOOL.
Before a workflow run, verify the Veriphone connection is ACTIVE via RUBE_MANAGE_CONNECTIONS.
When tool schemas change, re-run RUBE_SEARCH_TOOLS to fetch updated slugs and schemas before executing.
Execute a sequence of Veriphone tasks in a single session to leverage session reuse.
Perform bulk Veriphone operations using RUBE_REMOTE_WORKBENCH and run_composio_tool.

Frequently Asked Questions

Add this skill to your agents