Datagma Automation
This skill automates operations within Datagma using Composio's toolkit via Rube MCP.
Install
npx promptshop add datagma-automationDetails
What This Skill Does
- This skill automates operations within Datagma using Composio's toolkit via Rube MCP.
- It allows users to streamline tasks related to data enrichment and lead generation.
- This is useful for sales and marketing teams that use Datagma to find and qualify leads.
When to Use
- Enrich lead data
- Find contact information
- Generate lead lists
- Verify email addresses
- Discover company details
- Automate lead scoring
Key Features
- Uses Rube MCP for automation
- Requires an active Datagma connection
- Discovers available tools via RUBE_SEARCH_TOOLSChecks connection status before execution
- Executes tools using RUBE_MULTI_EXECUTE_TOOLProvides toolkit documentation for reference
Manual Installation
- Manual installation
- View Full Skill Content
- The complete markdown content that gets installed
- Datagma Automation via Rube MCP
Automate Datagma operations through Composio's Datagma toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/datagma
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Datagma connection via RUBE_MANAGE_CONNECTIONS with toolkit datagma 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 datagma 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: "Datagma 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 Datagma task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["datagma"] 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 Datagma-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit datagma |
| 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
- Datagma Automation via Rube MCP
Automate Datagma operations through Composio's Datagma toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/datagma
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Datagma connection via RUBE_MANAGE_CONNECTIONS with toolkit datagma Always call RUBE_SEARCH_TOOLS first to get current tool schemas
- 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 datagma If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS queries: [{use_case: "Datagma operations", known_fields: ""}] session: {generate_id: true}
This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.
RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Datagma task"}] session: {id: "existing_session_id"}
RUBE_MANAGE_CONNECTIONS toolkits: ["datagma"] session_id: "your_session_id"
RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"
- 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Datagma-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit datagma |
| 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