persistiq-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/persistiq-automation --openclawPersistiq Automation via Rube MCP
Automate Persistiq operations through Composio's Persistiq toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/persistiq
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Persistiq connection via
RUBE_MANAGE_CONNECTIONSwith toolkitpersistiq - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitpersistiq - 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: "Persistiq 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 Persistiq task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["persistiq"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Persistiq-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit persistiq |
| 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/persistiq-automation/SKILL.mdView on GitHub Overview
Automate Persistiq operations through Composio's Persistiq toolkit via Rube MCP. It guides you to discover current tool schemas first, verify an active Persistiq connection, and execute the appropriate tool with memory and session management. This keeps workflows resilient to schema changes and connection issues.
How This Skill Works
You first call RUBE_SEARCH_TOOLS to fetch available Persistiq tool slugs and schemas. Next, verify the Persistiq connection with RUBE_MANAGE_CONNECTIONS and ensure it is ACTIVE. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered slug, passing memory as required and reusing a session ID when appropriate.
When to Use It
- Scenario 1: First-time setup — connect to Persistiq with RUBE_MANAGE_CONNECTIONS, verify ACTIVE, and run initial tool discovery with RUBE_SEARCH_TOOLS.
- Scenario 2: Scheduling recurring tasks — discover tools, reuse a session, and automate executions on a schedule.
- Scenario 3: Bulk operations — perform multiple Persistiq tasks in a single run using RUBE_REMOTE_WORKBENCH with run_composio_tool.
- Scenario 4: Debugging schemas — when tools change, re-run RUBE_SEARCH_TOOLS to fetch current slugs and arguments.
- Scenario 5: Version migration — update to the latest Persistiq toolkit by refreshing tool schemas and avoiding hardcoded slugs.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS queries: [{use_case: Persistiq operations, known_fields: empty}]
- Step 2: RUBE_MANAGE_CONNECTIONS using the persistiq toolkit and your session_id
- Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and its arguments, memory: {}, session_id: your_session_id
Best Practices
- Always search first to get current tool schemas; never hardcode slugs or arguments.
- Verify the connection shows ACTIVE before executing tools.
- Use exact field names and types from the search results for arguments.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and generate new ones only for new workflows.
Example Use Cases
- Example: Schedule a nightly Persistiq campaign send by discovering the send_campaign tool slug, validating an active connection, and executing with memory to track run state.
- Example: Bulk update Persistiq tasks across multiple campaigns using a bulk execution path via RUBE_REMOTE_WORKBENCH.
- Example: Automatically reconnect to Persistiq when the authentication token expires and resume the workflow.
- Example: Migrate to latest Persistiq tool schemas by re-running RUBE_SEARCH_TOOLS and updating tool slugs.
- Example: Reuse a session for a multi-step Persistiq workflow to minimize setup overhead.
