detrack-automation

Automate Detrack tasks via Rube MCP (Composio). Always search tools first for current schemas.

Install

Hot:19

Download and extract to your skills directory

Copy command and send to OpenClaw for auto-install:

Download and install this skill https://openskills.cc/api/download?slug=composiohq-composio-skills-detrack-automation&locale=en&source=copy

Detrack Automation - Enable Logistics Delivery Automation with Rube MCP

Skill Overview


Detrack Automation is a Claude skill that automates the Detrack logistics delivery system via Composio Rube MCP. It supports features such as creating delivery tasks, querying statuses, and performing batch operations. You can integrate the Detrack API without writing code.

Use Cases

1. Auto-Delivery for E-commerce Orders


After receiving an order, e-commerce sellers need to automatically push order information to the Detrack system to create delivery tasks. With this skill, you can connect e-commerce platforms (e.g., Shopify, WooCommerce) with Detrack to enable automatic order synchronization and delivery task creation. This reduces manual data entry errors and improves order fulfillment efficiency.

2. ERP System Integration


Enterprises that already have an ERP or warehouse management system need to automatically send outbound orders to Detrack for delivery arrangement. By connecting through Rube MCP, you can exchange data between the ERP and Detrack without changing your existing system architecture. It also supports batch order processing and real-time status synchronization.

3. Optimizing Batch Delivery Operations


Logistics companies or delivery teams need to create, modify, or query large numbers of delivery tasks in batches. This skill provides batch operation capabilities, allowing you to process hundreds of delivery tasks in one go. Combined with Detrack’s smart dispatching and driver assignment features, it significantly improves daily productivity for the delivery team.

Core Features

1. Intelligent Tool Discovery and Execution


Using RUBE_SEARCH_TOOLS, the skill automatically discovers Detrack’s latest available API tools and parameter structures, eliminating the need to manually maintain API documentation. It returns the current list of usable tools, input modes, recommended execution approaches, and known issues, ensuring you always call the API correctly.

2. Connection Management and Status Monitoring


Use RUBE_MANAGE_CONNECTIONS to manage the connection status of your Detrak account. You can monitor whether a connection is active in real time. If a connection is disconnected or unauthorized, the system will return an authentication link to complete setup, ensuring the automation workflow runs reliably.

3. Batch Task Execution


Use RUBE_MULTI_EXECUTE_TOOL to perform multiple Detrack operations in one request. It supports batch creation of delivery tasks, batch status queries, batch updates of information, and more. With memory parameters and session reuse mechanisms, you can complete complex delivery business logic within a single workflow.

FAQs

What is Rube MCP, and how do I get it?


Rube MCP is a Model Context Protocol service provided by Composio. You can use it without an API key. Just add https://rube.app/mcp as the MCP server address in your client configuration. After that, you can use tools like RUBE_SEARCH_TOOLS to discover and call various third-party APIs, including Detrack.

How do I confirm the Detrack connection is successful?


Call RUBE_MANAGE_CONNECTIONS and set the toolkit to detrack. If the returned connection status is ACTIVE, the connection is working properly. If the status is not ACTIVE, the system will provide an authentication link. Click it to complete authorization. It’s recommended to check connection status before running any automation workflow.

Why do I need to call SEARCH_TOOLS every time?


Detrack’s API tools and parameter structures may change over time. Hard-coding tool names and parameters can easily cause call failures. RUBE_SEARCH_TOOLS returns the latest tool architecture, recommended execution plans, and known pitfalls, ensuring your automation workflow always uses the correct API. This is best practice when using Rube MCP.