deadline-funnel-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/deadline-funnel-automation --openclawDeadline Funnel Automation via Rube MCP
Automate Deadline Funnel operations through Composio's Deadline Funnel toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/deadline_funnel
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Deadline Funnel connection via
RUBE_MANAGE_CONNECTIONSwith toolkitdeadline_funnel - 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 toolkitdeadline_funnel - 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: "Deadline Funnel 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 Deadline Funnel task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["deadline_funnel"]
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 Deadline Funnel-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit deadline_funnel |
| 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/deadline-funnel-automation/SKILL.mdView on GitHub Overview
Deadline Funnel Automation via Rube MCP lets you orchestrate Deadline Funnel tasks through Composio's toolkit. It emphasizes discovering current tool schemas before execution to stay aligned with updates. This approach reduces breakage and speeds up reliable funnel automation.
How This Skill Works
It uses RUBE_SEARCH_TOOLS to fetch live tool schemas and recommended execution plans, then RUBE_MANAGE_CONNECTIONS to ensure an active connection to the deadline_funnel toolkit. Finally, it runs the chosen tool with RUBE_MULTI_EXECUTE_TOOL, passing exact field names from the schemas and including a memory payload and session management.
When to Use It
- Automating creation or update of Deadline Funnel deadlines across multiple funnels
- Performing bulk or batch operations on deadlines or campaigns
- Onboarding or reestablishing a Deadline Funnel integration after credential changes
- Validating tool schemas before running workflows to avoid broken arguments
- Running multiple tools in a single session to maintain state
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed.
- Step 2: Verify RUBE_SEARCH_TOOLS responds and configure the Deadline Funnel connection with RUBE_MANAGE_CONNECTIONS using the deadline_funnel toolkit.
- Step 3: Discover available tools with RUBE_SEARCH_TOOLS and run a simple tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to fetch current schemas
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
- Use exact field names and types from the search results and avoid hardcoding slugs
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
- Reuse session IDs within a workflow and handle pagination when listed in responses
Example Use Cases
- Auto-create a new deadline for a new signup using the discovered tool slug
- Bulk-update expiration dates for a cohort of leads across funnels weekly
- Run a connectivity check and generate a status report for the deadline_funnel integration
- Discover tool schemas and migrate an existing workflow to a new schema version
- Execute a sequence of tools in one session to prepare a funnel, trigger a deadline, and log results
