Fidel API Automation

What This Skill Does

This skill automates Fidel API operations using Composio's Fidel API toolkit through Rube MCP. It's designed for developers and businesses that need to programmatically interact with the Fidel API to manage card-linked programs and data. The skill handles connection management, tool discovery, and execution.

When to Use

• Automate card linking with Fidel API.
• Retrieve transaction data via Fidel.
• Manage Fidel API programs.
• Create automated Fidel reports.
• Sync Fidel data with internal systems.
• Process Fidel API webhooks.

Key Features

• Connects to Fidel API via Rube MCP.
• Discovers available Fidel API tools dynamically.
• Enforces schema compliance for tool arguments.
• Manages Fidel API connection status.
• Provides a structured workflow pattern.
• Offers guidance on avoiding common errors.

Manual Installation

Fidel API Automation via Rube MCP

Automate Fidel API operations through Composio's Fidel API toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/fidel_api

Prerequisites

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

Step 2: Check Connection

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