Detrack Automation

What This Skill Does

This skill automates Detrack operations using the Composio Detrack toolkit via Rube MCP. It enables users to streamline delivery management and tracking workflows. It is designed for those who want to integrate Detrack with other systems.

When to Use

• Automate delivery tracking
• Generate delivery reports
• Manage delivery routes
• Sync Detrack data with other tools
• Create custom Detrack workflows
• Monitor driver performance

Key Features

Manual Installation

• Manual installation
• View Full Skill Content
• The complete markdown content that gets installed
• Detrack Automation via Rube MCP

Automate Detrack operations through Composio's Detrack toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/detrack

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Detrack connection via RUBE_MANAGE_CONNECTIONS with toolkit detrack 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 detrack 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: "Detrack 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 Detrack task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["detrack"] 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

• Powered by Composio
• Detrack Automation via Rube MCP

Automate Detrack operations through Composio's Detrack toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/detrack

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Detrack connection via RUBE_MANAGE_CONNECTIONS with toolkit detrack 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 detrack 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: "Detrack 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 Detrack task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["detrack"] 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