Do I need API keys to use postgrid-automation?

No API keys are required. Add https://rube.app/mcp as an MCP server and use RUBE_SEARCH_TOOLS to discover tool schemas.

What happens if tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing tools to obtain current slugs and argument schemas.

What should I pass in memory for execution?

Pass an empty object {} if there is no memory state to preserve.

postgrid-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Postgrid Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/postgrid

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Postgrid operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas first and validating the Postgrid connection before executing any workflows.

How This Skill Works

Connect Rube MCP to Postgrid and fetch current tool schemas with RUBE_SEARCH_TOOLS. Then select a tool, confirm the connection is ACTIVE with RUBE_MANAGE_CONNECTIONS, and execute the tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug and proper memory payload.

When to Use It

When starting an automated Postgrid workflow and you need up-to-date tool schemas.
When setting up a new Postgrid connection and validating it before running tasks.
When orchestrating multiple Postgrid tasks in a single session.
When troubleshooting failures due to changing tool schemas.
When reusing a workflow across different runs and sessions, ensuring proper session management.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server and verify connectivity with RUBE_SEARCH_TOOLS.
Step 2: Call RUBE_MANAGE_CONNECTIONS for toolkit postgrid and ensure status ACTIVE.
Step 3: Discover a tool slug with RUBE_SEARCH_TOOLS and execute it with RUBE_MULTI_EXECUTE_TOOL including memory and session_id.

Best Practices

Always run RUBE_SEARCH_TOOLS before selecting a tool slug.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution.
Use exact field names and types as returned by the tool schemas.
Always include memory in RUBE_MULTI_EXECUTE_TOOL, even if empty.
Reuse a session_id for the same workflow and handle pagination tokens.

Example Use Cases

Example: Discover tools for 'Postgrid operations' and run a scheduled update.
Example: Connect to Postgrid, validate, then execute a single tool with proper arguments.
Example: Run a sequence of Postgrid tasks in one session using multiple tool slugs.
Example: Bulk post updates using RUBE_REMOTE_WORKBENCH and run_composio_tool.
Example: Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to reference exact fields.

Frequently Asked Questions

Add this skill to your agents