Affinity Automation
This skill automates Affinity operations using the Composio Affinity toolkit via Rube MCP. It allows users to discover tools, manage connections, and execute...
Install
npx promptshop add affinity-automationDetails
What This Skill Does
This skill automates Affinity operations using the Composio Affinity toolkit via Rube MCP. It allows users to discover tools, manage connections, and execute tasks within Affinity. This is helpful for those looking to streamline relationship intelligence and CRM processes.
When to Use
- Discover available Affinity tools.
- Check the status of the Affinity connection.
- Execute specific Affinity tools.
- Update contact information in Affinity.
- Automate relationship tracking workflows.
- Verify schema compliance for tool arguments.
Key Features
- Automates Affinity tasks through Rube MCP.
- Uses RUBE_SEARCH_TOOLS to find available tools.
- Manages Affinity connections via RUBE_MANAGE_CONNECTIONS.
- Executes tools with RUBE_MULTI_EXECUTE_TOOL.
- Requires an active Affinity connection.
- Ensures schema compliance for tool arguments.
Automate Affinity operations through Composio's Affinity toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/affinity
Prerequisites
Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Affinity connection via RUBE_MANAGE_CONNECTIONS with toolkit affinity 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 affinity 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: "Affinity 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 Affinity task"}] session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS toolkits: ["affinity"] 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 Affinity-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit affinity |
| 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 |
| 's Affinity toolkit via Rube MCP. |
Toolkit docs: composio.dev/toolkits/affinity