Nango Automation
Automate nango operations.
Install
npx promptshop add nango-automationDetails
What This Skill Does
The Nango Automation skill allows users to automate operations within the Nango platform through Composio's Nango toolkit, utilizing Rube MCP. It is designed for developers and automation engineers who need to manage and interact with Nango connections programmatically. This skill streamlines workflows by providing tools for discovering, connecting to, and executing Nango functionalities.
When to Use
- Sync data between different platforms.
- Automate user provisioning tasks.
- Manage OAuth connections programmatically.
- Trigger workflows based on Nango events.
- Monitor connection health and status.
- Build custom integrations using Nango.
Key Features
- Automates Nango operations via Rube MCP.
- Uses Composio's Nango toolkit.
- Discovers available tools dynamically.
- Manages Nango connections programmatically.
- Executes schema-compliant Nango tools.
- Provides error handling and connection verification.
Manual Installation
Automate Nango operations through Composio's Nango toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/nango
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Nango connection via RUBE_MANAGE_CONNECTIONS with toolkit nango 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 nango 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: "Nango 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 Nango task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["nango"] 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
| Operation | Approach |
|---|---|
| Find tools | RUBE_SEARCH_TOOLS with Nango-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit nango |
| Execute | RUBE_MULTI_EXECUTE_TOOL with discovered tool slugs |
| Bulk ops | RUBE_REMOTE_WORKBENCH with run_composio_tool() |
| Full schema | RUBE_GET_TOOL_SCHEMAS for tools with schemaRef |
Automate Nango operations through Composio's Nango toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/nango