Heyzine Automation

What This Skill Does

• This skill automates Heyzine operations using the Composio Heyzine toolkit via Rube MCP.
• It allows users to discover available tools, check connections, and execute specific tasks within the Heyzine platform.
• This is useful for marketers and designers who need to automate the creation and management of digital publications.

When to Use

• Automate digital publication creation.
• Manage Heyzine connections.
• Discover available Heyzine tools.
• Execute specific Heyzine tasks.
• Search for available tools.
• Check Heyzine connection status.

Key Features

• Automates Heyzine operations via Rube MCP.
• Uses Composio's Heyzine toolkit.
• Discovers tools using RUBE_SEARCH_TOOLS.
• Manages connections with RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Provides setup and usage instructions.

Manual Installation

• Manual installation.
• View Full Skill Content.
• The complete markdown content that gets installed.
• Heyzine Automation via Rube MCP.

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

Toolkit docs: composio.dev/toolkits/heyzine

Prerequisites

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

Step 2: Check Connection

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

Powered by Composio. Heyzine Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/heyzine

Prerequisites

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

Step 2: Check Connection

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

Powered by Composio