Axonaut Automation

What This Skill Does

• This skill automates Axonaut operations using Composio's Axonaut toolkit through Rube MCP.
• It enables users to manage their business operations within Axonaut programmatically, such as CRM, invoicing, and project management.
• It is designed for business owners and managers who want to automate their Axonaut workflows.

When to Use

• Automate invoice creation and sending.
• Manage customer contacts and interactions.
• Track project progress and tasks.
• Generate financial reports.
• Sync Axonaut data with accounting software.
• Automate lead follow-up processes.

Key Features

• Uses Rube MCP for tool discovery and execution.
• Requires an active Axonaut connection via RUBE_MANAGE_CONNECTIONS.
• Employs RUBE_SEARCH_TOOLS to get current tool schemas.
• Follows a discover, connect, execute workflow pattern.
• Provides error handling and connection status checks.
• Ensures schema compliance for tool arguments.

Manual Installation

Axonaut Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/axonaut

Prerequisites

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

Step 2: Check Connection

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