Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Centralstationcrm Automation via Rube MCP

agent operations skill risk: medium

Centralstationcrm Automation via Rube MCP

Instructs the model to automate Centralstationcrm operations through Composio's toolkit via Rube MCP by first calling RUBE_SEARCH_TOOLS, managing connections with RUBE_MANAGE_CONNE…

  • External action: medium

SKILL 1 file

SKILL.md
---
name: centralstationcrm-automation
description: "Automate Centralstationcrm tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Centralstationcrm Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/centralstationcrm](https://composio.dev/toolkits/centralstationcrm)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Centralstationcrm connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Centralstationcrm 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 Centralstationcrm task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["centralstationcrm"]
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 Centralstationcrm-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `centralstationcrm` |
| 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` |

---
*Powered by [Composio](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active centralstationcrm connection

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit centralstationcrm
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Always discover available tools before executing workflows
  7. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  8. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  9. Use exact field names and types from the search results
  10. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  11. Reuse session IDs within a workflow
  12. Generate new session IDs for new workflows
  13. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always search tools first
  • verify active connection before execution
  • reuse session ids within workflow

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments from search results
  • Include memory parameter
  • Reuse sessions within workflow

FAILURE MODES

  • Hardcoding tool slugs without searching first
  • Executing tools without ACTIVE connection
  • Using incorrect field names from outdated schemas
  • Omitting memory parameter in execute calls
  • Not handling pagination

CAVEATS

Dependencies
  • RUBE_SEARCH_TOOLS available
  • Active Centralstationcrm connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target MCP client or programming environment
  • Example end-to-end task with concrete arguments
Ambiguities
  • Tool call examples use pseudo-syntax (e.g., 'RUBE_SEARCH_TOOLS queries: [...]') without defining exact parameter encoding or client language.
  • Placeholder 'your specific Centralstationcrm task' is left unspecified.

QUALITY

OVERALL
0.76
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.68
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Replace the generic placeholder with 2-3 concrete use-case examples including sample arguments.
  • Add an explicit 'Output format' section describing how tool results should be returned or logged.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT