nango-automation

Automate Nango integration tasks through Rube MCP toolkits and workflows.

74.2k|8.5k|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill nango-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nango-automation
Source: https://github.com/ComposioHQ/awesome-claude-skills/tree/main/composio-skills/nango-automation
Command: npx skills add https://github.com/ComposioHQ/awesome-claude-skills --skill nango-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the complexity of managing Nango integrations by providing a standardized, automated workflow for tool discovery, connection management, and execution via the Rube MCP gateway.

Core Features & Use Cases

  • Automated Tool Discovery: Dynamically fetch current Nango tool schemas and execution plans to ensure compatibility.
  • Connection Management: Programmatically verify and manage active Nango connections to prevent authentication errors during workflows.
  • Use Case: A developer needs to sync data across multiple SaaS platforms; this skill automates the discovery of Nango tools and executes multi-step operations without manual API configuration.

Quick Start

Use the nango-automation skill to discover available tools and execute a connection check for your current session.

Frequently Asked Questions about nango-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover available Nango tools?

Call the RUBE_SEARCH_TOOLS function with a Nango-specific use case query to retrieve current tool slugs, input schemas, and execution plans.

How to verify if my Nango connection is active?

Use the RUBE_MANAGE_CONNECTIONS tool with the 'nango' toolkit parameter to check the current connection status and follow the provided auth link if inactive.

Can I execute multiple Nango tools in one workflow?

Yes, use the RUBE_MULTI_EXECUTE_TOOL function to run a sequence of discovered tools by passing the appropriate slugs and schema-compliant arguments.

Why should I always search for tools before execution?

Tool schemas and available endpoints change frequently; searching first ensures you use the most current arguments and prevents execution errors.

What should I do if a tool execution fails?

Verify your connection status using RUBE_MANAGE_CONNECTIONS, ensure your arguments match the schema returned by RUBE_SEARCH_TOOLS, and check for pagination tokens in the response.