Get the FREE Ultimate OpenClaw Setup Guide →

postgrid-verify-automation

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

Postgrid Verify Automation via Rube MCP

Automate Postgrid Verify operations through Composio's Postgrid Verify toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/postgrid_verify

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Postgrid Verify connection via RUBE_MANAGE_CONNECTIONS with toolkit postgrid_verify
  • 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 postgrid_verify
  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: "Postgrid Verify 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 Postgrid Verify task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["postgrid_verify"]
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 Postgrid Verify-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit postgrid_verify
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/postgrid-verify-automation/SKILL.mdView on GitHub

Overview

This skill automates Postgrid Verify operations via Composio's toolkit using Rube MCP. It relies on a connected Rube MCP, an active Postgrid Verify connection, and always discovering current tool schemas first to avoid stale slugs.

How This Skill Works

It uses Rube MCP to first discover available tools with RUBE_SEARCH_TOOLS to obtain up-to-date input schemas. Then it checks the Postgrid Verify connection with RUBE_MANAGE_CONNECTIONS and finally executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL, including a memory payload and a session_id for continuity.

When to Use It

  • Automate recurring Postgrid Verify tasks to save time
  • When tool schemas change and you need current slugs via RUBE_SEARCH_TOOLS
  • When establishing or validating the Postgrid Verify connection
  • When chaining multiple verify tools in a single workflow
  • When ensuring session continuity and handling pagination in tool results

Quick Start

  1. Step 1: Add Rube MCP endpoint https://rube.app/mcp
  2. Step 2: Run RUBE_SEARCH_TOOLS with use_case: Postgrid Verify operations to discover tools
  3. Step 3: Run RUBE_MANAGE_CONNECTIONS with toolkits: [postgrid_verify], then RUBE_MULTI_EXECUTE_TOOL with memory and a session_id

Best Practices

  • Always search tools first to fetch current schemas
  • Verify the connection shows ACTIVE before executing tools
  • Use exact field names and types from search results
  • Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  • Reuse session IDs within a workflow; generate new ones for new workflows

Example Use Cases

  • Nightly Postgrid Verify batch executed after discovering tools with RUBE_SEARCH_TOOLS
  • Onboarding new Postgrid Verify tools by re-fetching schemas and testing execution
  • Reconnecting after credential updates and verifying ACTIVE status
  • Executing multiple verify tools in a single RUBE_MULTI_EXECUTE_TOOL call
  • Using RUBE_GET_TOOL_SCHEMAS to compare current schemas against a baseline

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers