Slackbot Automation

What This Skill Does

• This skill automates Slackbot operations using Composio's Slackbot toolkit via Rube MCP.
• It allows users to programmatically interact with Slack, such as sending messages, managing channels, and automating workflows.
• This is useful for developers and automation engineers.

When to Use

• Send automated notifications to a Slack channel.
• Create a new Slack channel for a project.
• Invite users to a specific Slack channel.
• Post daily reports to a designated channel.
• Trigger workflows based on Slack events.
• Manage Slackbot connections.

Key Features

Manual Installation

Slackbot Automation via Rube MCP

Prerequisites

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

Step 2: Check Connection

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