Customjs Automation

What This Skill Does

This skill automates interactions with Custom JavaScript code using the Composio Rube MCP. It is designed for users who want to programmatically execute custom JavaScript functions. The skill handles tool discovery, connection management, and execution of specific JavaScript tasks.

When to Use

• Execute custom JavaScript code.
• Automate data transformations.
• Integrate JavaScript with other systems.
• Run complex calculations.
• Validate data using JavaScript.
• Create dynamic web content.

Key Features

• Automates Customjs operations.
• Uses Composio's Rube MCP for integration.
• Discovers available tools dynamically.
• Manages API connections.
• Executes tools with schema validation.
• Provides error handling and connection checks.

Manual Installation

Customjs Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/customjs

Prerequisites

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

Step 2: Check Connection

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