peopledatalabs-automation
npx machina-cli add skill ComposioHQ/awesome-claude-skills/peopledatalabs-automation --openclawPeopledatalabs Automation via Rube MCP
Automate Peopledatalabs operations through Composio's Peopledatalabs toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/peopledatalabs
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Peopledatalabs connection via
RUBE_MANAGE_CONNECTIONSwith toolkitpeopledatalabs - 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 toolkitpeopledatalabs - 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: "Peopledatalabs 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 Peopledatalabs task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["peopledatalabs"]
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 Peopledatalabs-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit peopledatalabs |
| 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/peopledatalabs-automation/SKILL.mdView on GitHub Overview
Automate Peopledatalabs operations using Composio's toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS and validating an active connection before running workflows.
How This Skill Works
The workflow starts by confirming RUBE_SEARCH_TOOLS availability, then connects to the Peopledatalabs toolkit via RUBE_MANAGE_CONNECTIONS. You then execute discovered tools with RUBE_MULTI_EXECUTE_TOOL, using the exact input schema and a memory payload; never hardcode tool slugs.
When to Use It
- Starting a new Peopledatalabs workflow where tool schemas may have changed
- Adding a Peopledatalabs task to an existing automation pipeline
- Validating that the Peopledatalabs connection is ACTIVE before execution
- Running bulk or chained operations using RUBE_MULTI_EXECUTE_TOOL
- Troubleshooting failures by re-fetching schemas and re-establishing connections
Quick Start
- Step 1: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas
- Step 2: Manage the Peopledatalabs connection via RUBE_MANAGE_CONNECTIONS with toolkits: ["peopledatalabs"]
- Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and memory
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
- Verify the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools
- Use exact field names and types from the discovered schemas; do not hardcode slugs
- Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
- Reuse session IDs within a workflow and handle pagination when present
Example Use Cases
- Automate lead enrichment by discovering the tool and running the enrichment step with the current schema
- Enrich a batch of contacts in a single session using multiple Peopledatalabs tools
- Re-run a failed workflow after re-discovering tools and rechecking the connection
- Schedule a daily Peopledatalabs task with connection validation
- Migrate workflows when RUBE_SEARCH_TOOLS updates tool slugs