Drip Jobs Automation
This skill automates Drip Jobs operations using Composio's Drip Jobs toolkit via Rube MCP. It's designed for users who need to streamline and automate tasks .
Install
npx promptshop add drip-jobs-automationDetails
What This Skill Does
This skill automates Drip Jobs operations using Composio's Drip Jobs toolkit via Rube MCP. It's designed for users who need to streamline and automate tasks within the Drip Jobs platform. The skill ensures proper setup and connection before executing any workflows.
When to Use
- Automate campaign creation in Drip Jobs.
- Manage user subscriptions via Drip Jobs.
- Trigger automated email sequences.
- Update subscriber data in Drip Jobs.
- Analyze campaign performance.
- Create drip campaigns.
Key Features
- Uses Rube MCP to interact with Drip Jobs.
- Requires an active Drip Jobs connection.
- Employs RUBE_SEARCH_TOOLS for tool discovery.
- Provides a core workflow pattern for execution.
- Offers guidance on handling known pitfalls.
- Uses schema-compliant arguments.
Manual Installation
Drip Jobs Automation via Rube MCP
Automate Drip Jobs operations through Composio's Drip Jobs toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/drip_jobs
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Drip Jobs connection via RUBE_MANAGE_CONNECTIONS with toolkit drip_jobs 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 drip_jobs 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: "Drip Jobs 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 Drip Jobs task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["drip_jobs"] 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 Drip Jobs-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit drip_jobs |
| 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 |
Drip Jobs Automation via Rube MCP
Automate Drip Jobs operations through Composio's Drip Jobs toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/drip_jobs
Step 1: Discover Available Tools
RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Drip Jobs task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["drip_jobs"] 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 Drip Jobs-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit drip_jobs |
| 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 |