Zylvie Automation

What This Skill Does

The Zylvie Automation skill allows users to automate Zylvie operations through the Composio's Zylvie toolkit via Rube MCP. It is designed for developers and automation engineers who need to integrate Zylvie services into their workflows. The skill streamlines the process of discovering, connecting to, and executing Zylvie tools.

When to Use

• Automate data extraction from Zylvie.
• Trigger Zylvie workflows based on external events.
• Integrate Zylvie with other business systems.
• Schedule routine Zylvie tasks.
• Monitor Zylvie performance metrics.
• Respond to Zylvie alerts automatically.

Key Features

• Automates Zylvie operations via Rube MCP.
• Uses Composio's Zylvie toolkit.
• Discovers available tools and their schemas.
• Manages Zylvie connections.
• Executes Zylvie tools with schema-compliant arguments.
• Provides a structured workflow pattern for Zylvie automation.

Manual Installation

Zylvie Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/zylvie

Prerequisites

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

Step 2: Check Connection

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

Zylvie Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/zylvie

Step 1: Discover Available Tools

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

Step 2: Check Connection

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