Retently Automation

What This Skill Does

This skill automates operations within Retently using Composio's Retently toolkit via Rube MCP. It's designed for users who want to streamline customer feedback management and improve survey processes. The skill requires an active Retently connection and familiarity with Rube MCP.

When to Use

Automate sending customer surveysTrigger surveys based on eventsAnalyze survey response dataUpdate customer profiles based on feedbackMonitor survey completion ratesIntegrate survey data with other systems

Key Features

Discovers available Retently tools via Rube MCPChecks and manages Retently connection statusExecutes Retently tools with schema validationProvides a structured workflow patternOffers guidance on avoiding common pitfallsUses Rube MCP for tool discovery and execution

Manual Installation

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

Toolkit docs: composio.dev/toolkits/retently

Prerequisites

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

Step 2: Check Connection

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