Canny Automation

What This Skill Does

This skill automates Canny operations using Composio's Canny toolkit via Rube MCP. It allows users to streamline and manage their feedback management processes through automated workflows. This is ideal for those who need to regularly manage and respond to user feedback in Canny.

When to Use

• Automate Canny tasks.
• Schedule regular feedback reviews.
• Integrate Canny into existing workflows.
• Verify Canny connection status.
• Discover available Canny tools.
• Execute specific Canny tools.

Key Features

• Uses Rube MCP to automate Canny.
• Requires an active Canny connection.
• Discovers available tools via RUBE_SEARCH_TOOLS.
• Checks connection status via RUBE_MANAGE_CONNECTIONS.
• Executes tools via RUBE_MULTI_EXECUTE_TOOL.
• Provides setup instructions and prerequisites.

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

Toolkit docs: composio.dev/toolkits/canny

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Canny connection via RUBE_MANAGE_CONNECTIONS with toolkit canny Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add 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 canny 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: "Canny 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

queries: [{use_case: "your specific Canny task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["canny"] 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: {}

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

Powered by Composio Canny Automation via Rube MCP