zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
What this skill does
# Zoho CRM Automation via Rube MCP Automate Zoho CRM operations through Composio's Zoho toolkit via Rube MCP. ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Zoho CRM connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zoho` - 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 `zoho` 3. If connection is not ACTIVE, follow the returned auth link to complete Zoho OAuth 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. Search and Retrieve Records **When to use**: User wants to find specific CRM records by criteria **Tool sequence**: 1. `ZOHO_LIST_MODULES` - List available CRM modules [Prerequisite] 2. `ZOHO_GET_MODULE_FIELDS` - Get field definitions for a module [Optional] 3. `ZOHO_SEARCH_ZOHO_RECORDS` - Search records by criteria [Required] 4. `ZOHO_GET_ZOHO_RECORDS` - Get records from a module [Alternative] **Key parameters**: - `module`: Module name (e.g., 'Leads', 'Contacts', 'Deals', 'Accounts') - `criteria`: Search criteria string (e.g., 'Email:equals:[email protected]') - `fields`: Comma-separated list of fields to return - `per_page`: Number of records per page - `page`: Page number for pagination **Pitfalls**: - Module names are case-sensitive (e.g., 'Leads' not 'leads') - Search criteria uses specific syntax: 'Field:operator:value' - Supported operators: equals, starts_with, contains, not_equal, greater_than, less_than - Complex criteria use parentheses and AND/OR: '(Email:equals:[email protected])AND(Last_Name:equals:Doe)' - GET_ZOHO_RECORDS returns all records with optional filtering; SEARCH is for targeted lookups ### 2. Create Records **When to use**: User wants to add new leads, contacts, deals, or other CRM records **Tool sequence**: 1. `ZOHO_GET_MODULE_FIELDS` - Get required fields for the module [Prerequisite] 2. `ZOHO_CREATE_ZOHO_RECORD` - Create a new record [Required] **Key parameters**: - `module`: Target module name (e.g., 'Leads', 'Contacts') - `data`: Record data object with field-value pairs - Required fields vary by module (e.g., Last_Name for Contacts) **Pitfalls**: - Each module has mandatory fields; use GET_MODULE_FIELDS to identify them - Field names use underscores (e.g., 'Last_Name', 'Email', 'Phone') - Lookup fields require the related record ID, not the name - Date fields must use 'yyyy-MM-dd' format - Creating duplicates is allowed unless duplicate check rules are configured ### 3. Update Records **When to use**: User wants to modify existing CRM records **Tool sequence**: 1. `ZOHO_SEARCH_ZOHO_RECORDS` - Find the record to update [Prerequisite] 2. `ZOHO_UPDATE_ZOHO_RECORD` - Update the record [Required] **Key parameters**: - `module`: Module name - `record_id`: ID of the record to update - `data`: Object with fields to update (only changed fields needed) **Pitfalls**: - record_id must be the Zoho record ID (numeric string) - Only provide fields that need to change; other fields are preserved - Read-only and system fields cannot be updated - Lookup field updates require the related record ID ### 4. Convert Leads **When to use**: User wants to convert a lead into a contact, account, and/or deal **Tool sequence**: 1. `ZOHO_SEARCH_ZOHO_RECORDS` - Find the lead to convert [Prerequisite] 2. `ZOHO_CONVERT_ZOHO_LEAD` - Convert the lead [Required] **Key parameters**: - `lead_id`: ID of the lead to convert - `deal`: Deal details if creating a deal during conversion - `account`: Account details for the conversion - `contact`: Contact details for the conversion **Pitfalls**: - Lead conversion is irreversible; the lead record is removed from the Leads module - Conversion can create up to three records: Contact, Account, and Deal - Existing account matching may occur based on company name - Custom field mappings between Lead and Contact/Account/Deal modules affect the outcome ### 5. Manage Tags and Related Records **When to use**: User wants to tag records or manage relationships between records **Tool sequence**: 1. `ZOHO_CREATE_ZOHO_TAG` - Create a new tag [Optional] 2. `ZOHO_UPDATE_RELATED_RECORDS` - Update related/linked records [Optional] **Key parameters**: - `module`: Module for the tag - `tag_name`: Name of the tag - `record_id`: Parent record ID (for related records) - `related_module`: Module of the related record - `data`: Related record data to update **Pitfalls**: - Tags are module-specific; a tag created for Leads is not available in Contacts - Related records require both the parent record ID and the related module - Tag names must be unique within a module - Bulk tag operations may hit rate limits ## Common Patterns ### Module and Field Discovery ``` 1. Call ZOHO_LIST_MODULES to get all available modules 2. Call ZOHO_GET_MODULE_FIELDS with module name 3. Identify required fields, field types, and picklist values 4. Use field API names (not display labels) in data objects ``` ### Search Criteria Syntax **Simple search**: ``` criteria: '(Email:equals:[email protected])' ``` **Combined criteria**: ``` criteria: '((Last_Name:equals:Doe)AND(Email:contains:example.com))' ``` **Supported operators**: - `equals`, `not_equal` - `starts_with`, `contains` - `greater_than`, `less_than`, `greater_equal`, `less_equal` - `between` (for dates/numbers) ### Pagination - Set `per_page` (max 200) and `page` starting at 1 - Check response `info.more_records` flag - Increment page until more_records is false - Total count available in response info ## Known Pitfalls **Field Names**: - Use API names, not display labels (e.g., 'Last_Name' not 'Last Name') - Custom fields have API names like 'Custom_Field1' or user-defined names - Picklist values must match exactly (case-sensitive) **Rate Limits**: - API call limits depend on your Zoho CRM plan - Free plan: 5000 API calls/day; Enterprise: 25000+/day - Implement delays between bulk operations - Monitor 429 responses and respect rate limit headers **Data Formats**: - Dates: 'yyyy-MM-dd' format - DateTime: 'yyyy-MM-ddTHH:mm:ss+HH:mm' format - Currency: Numeric values without formatting - Phone: String values (no specific format enforced) **Module Access**: - Access depends on user role and profile permissions - Some modules may be hidden or restricted in your CRM setup - Custom modules have custom API names ## Quick Reference | Task | Tool Slug | Key Params | |------|-----------|------------| | List modules | ZOHO_LIST_MODULES | (none) | | Get module fields | ZOHO_GET_MODULE_FIELDS | module | | Search records | ZOHO_SEARCH_ZOHO_RECORDS | module, criteria | | Get records | ZOHO_GET_ZOHO_RECORDS | module, fields, per_page, page | | Create record | ZOHO_CREATE_ZOHO_RECORD | module, data | | Update record | ZOHO_UPDATE_ZOHO_RECORD | module, record_id, data | | Convert lead | ZOHO_CONVERT_ZOHO_LEAD | lead_id, deal, account, contact | | Create tag | ZOHO_CREATE_ZOHO_TAG | module, tag_name | | Update related records | ZOHO_UPDATE_RELATED_RECORDS | module, record_id, related_module, data | ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.