Baselinker Automation

What This Skill Does

This skill automates Baselinker operations using Composio's Baselinker toolkit via Rube MCP. It's designed for users who want to streamline e-commerce tasks within Baselinker through automated workflows. The skill requires an active Baselinker connection and Rube MCP setup.

When to Use

Automate order processing in Baselinker. Sync product data between Baselinker and other platforms. Manage inventory levels automatically. Generate shipping labels programmatically. Update order statuses in real-time. Process returns and refunds automatically.

Key Features

Uses Rube MCP to manage Baselinker connections. Discovers available tools dynamically using RUBE_SEARCH_TOOLS. Enables multi-tool execution with RUBE_MULTI_EXECUTE_TOOL. Requires schema compliance for tool arguments. Provides a structured workflow pattern for automation. Offers documentation for the Baselinker toolkit.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedBaselinker Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/baselinker

Prerequisites

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

Step 2: Check Connection

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

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

Toolkit docs: composio.dev/toolkits/baselinker