PromptShop

Peopledatalabs Automation

This skill automates Peopledatalabs operations through Composio using Rube MCP. It is designed for developers and data professionals who need to integrate pe...

Install

npx promptshop add peopledatalabs-automation

Details

What This Skill Does

This skill automates Peopledatalabs operations through Composio using Rube MCP. It is designed for developers and data professionals who need to integrate people data into their workflows. The skill provides tools for discovering available Peopledatalabs tools, managing connections, and executing specific data-related tasks.

When to Use

Key Features

Automates Peopledatalabs operations via Rube MCP. Uses Composio's Peopledatalabs toolkit. Discovers tools dynamically using RUBE_SEARCH_TOOLS. Manages connections using RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL. Provides documentation for setup and usage.

Manual Installation

  • Manual installation
  • View Full Skill Content
  • The complete markdown content that gets installed
  • Peopledatalabs 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_CONNECTIONS with toolkit peopledatalabs Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit peopledatalabs 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", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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 Peopledatalabs-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit peopledatalabs
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
  • Peopledatalabs 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_CONNECTIONS with toolkit peopledatalabs Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit peopledatalabs 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", }] memory: {} session_id: "your_session_id"

Known Pitfalls

Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools 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 Peopledatalabs-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit peopledatalabs
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