Analyze any CRM module with statistical breakdown by field values. Perfect for generating reports, understanding data distribution, and identifying patterns.

Workflow: First use crm_get_all_modules to discover available modules, then get_custom_module_records to explore data, finally analyze_custom_module for insights

Perform statistical analysis on any field in any module

Add a comment to a credit note

Apply a credit note to an invoice

Approve a purchase order

Export bills in bulk

Export credit notes in bulk

Export purchase orders in bulk

Print bills in bulk

Print credit notes in bulk

Print purchase orders in bulk

Cancel a purchase order

Convert a credit note to open status

Convert a Books estimate to an invoice

Create a new bill in Books

Create a new credit note in Books

Create a new customer in Books

Create a new estimate in Books

Create a new invoice in Books for billing customers. KEY FINANCIAL OPERATION in the Books workflow.\n\nPrerequisites:\n→ Use books_get_customers first to find target customer\n→ Use books_get_items to discover available products/services for line items\n→ Have valid customer_id from customer discovery\n\nNext Steps:\n→ Use books_create_payment to record payment against the invoice\n→ Use books_get_invoice to verify invoice creation\n→ Use invoice_id for payment tracking and reporting\n\nComplete Billing Workflow: books_get_customers → books_get_items → books_create_invoice → books_create_payment\n\nError Recovery: If creation fails, verify customer_id exists and line_items are properly formatted

Create a new product or service item in Books inventory. Use for adding products to sell, services to offer, or items to include in invoices.

Example: Create service item {"name": "Consulting Services", "description": "Business consulting", "rate": 150, "unit": "hrs", "item_type": "sales"}

Create a payment in Books to apply against specific invoices. First use books_get_invoices to find invoice IDs and amounts, then create payment to apply against those invoices.

Example workflow:

1. books_get_invoices({customer_id: "123"}) // Find unpaid invoices

2. books_create_payment({customer_id: "123", amount: 1000, invoices: [{invoice_id: "inv-456", amount_applied: 1000}]})

Create a new purchase order in Books

Delete a bill from Books

Delete a credit note from Books

Delete a customer from Books

Delete an invoice from Books

Delete an item from Books

Delete a purchase order from Books

Email a credit note

Email a purchase order

Get a specific bill from Books by ID

Get payments for a bill

Get all bills from Books

Get a specific credit note from Books by ID

Get comments for a credit note

Get refunds for a credit note

Get all credit notes from Books

Get detailed information for a specific customer from Books by ID. Returns complete customer profile including contact details, billing/shipping addresses, and account status.

Related tools: books_get_customers (to find IDs), books_create_invoice (to bill customer), books_create_payment (to record payments)

Get customer list from Books with filtering and pagination. WORKFLOW STARTER for Books financial operations.\n\nPrerequisites: Books access with customer management permissions\n\nNext Steps:\n→ Use books_get_customer for detailed customer information\n→ Use customer_id in books_create_invoice for billing\n→ Use customer_id in books_create_payment for payment processing\n\nCommon Financial Workflow: books_get_customers → books_get_customer → books_create_invoice → books_create_payment\n\nExample: Find customers by name\n{"search_text": "John", "per_page": 10}\n\nError Recovery: If no customers found, verify search filters and Books access permissions

Get all estimates from Books

Get a specific invoice from Books by ID

Get an invoice as PDF

Get invoices from Books with filtering and pagination. Use to find invoices for payments, get invoice details, or browse invoice history.

Related tools: books_create_invoice (to create), books_create_payment (to pay), books_get_customer (customer details)

Get a specific item from Books by ID

Get all items from Books including products and services available for billing. ESSENTIAL for invoice line items.\n\nPrerequisites: Books access with inventory management permissions\n\nNext Steps:\n→ Use item_id and details for books_create_invoice line items\n→ Use books_get_item for detailed item information\n→ Use books_create_item to add new products/services\n\nInventory to Billing Workflow: books_get_items → books_create_invoice (with line items) → books_create_payment\n\nError Recovery: If no items found, verify Books inventory setup and permissions

Get all payments from Books

Get a specific purchase order from Books by ID

Get all purchase orders from Books

Get all sales orders from Books with filtering and pagination\n\nPrerequisites: Books access with sales order read permissions\nNext Steps: Use books_create_invoice to convert sales orders to invoices\nWorkflow: Sales order management → invoice conversion → payment tracking\nError Recovery: If no sales orders found, verify Books access and search filters

Mark a bill as open

Mark a bill as paid

Mark a purchase order as billed

Mark a purchase order as open

Record a payment for a bill

Create a refund for a credit note

Send an invoice via email

Submit a purchase order for approval

Update an existing bill in Books

Update an existing credit note in Books

Update an existing customer in Books

Update an existing invoice in Books

Update an existing item in Books

Update an existing purchase order in Books

Void a bill

Void a credit note

Add a new environment

Add a new profile to the current environment

Export current configuration to .env format

Get current configuration status

List all available environments

List all profiles in the current environment

Remove an environment

Remove a profile from the current environment

Switch to a different environment

Switch to a different profile within the current environment

Update an existing profile

Create a Books invoice from a CRM deal. Automatically transfers deal information, products, and pricing to create a professional invoice.

Workflow: CRM deal → Books invoice → books_send_invoice_email → books_create_payment (when paid)

Analyze activity patterns and trends in CRM data - business intelligence for user behavior\n\nPrerequisites: Use crm_search_by_timeline to identify activity periods\nNext Steps: Generate insights reports → Optimize workflows → User performance analysis\nBusiness Value: Team productivity analysis, workflow optimization, trend identification\nError Recovery: If insufficient data, try broader date range or different grouping

Analyze module permissions and accessibility

Analyze picklist dependencies and relationships in a module. Identifies field dependencies, picklist chains, and relationship patterns.

Create a new event in CRM

Create a new note for a CRM record

Create a new profile

Create a new role

Create a task in CRM linked to accounts, contacts, or deals. Tasks can have due dates, priorities, and reminders for follow-up activities.

Example: Create follow-up task {"Subject": "Follow up on proposal", "Due_Date": "2024-12-31", "Priority": "High", "What_Id": "deal-123", "Who_Id": "contact-456"}

Create a new user

Delete a role

Extract complete picklist hierarchy with dependencies in one optimized call - reduces multiple API calls to single request

Get all currencies

Get all CRM modules with metadata\n\nWORKFLOW STARTER for CRM module discovery\n\nNext Steps: Use crm_get_fields for field discovery → crm_validate_criteria → crm_search_records\nPagination: Use page and per_page to limit response size and avoid token limits\nError Recovery: If response too large, use smaller per_page values (try 10-20)

Get all profiles in the organization

Prerequisites: None - this is a discovery tool for organizational structure Next Steps: Use crm_get_user_details for users associated with specific profiles → crm_get_all_roles to understand role hierarchy → crm_update_profile for permission modifications Common Pattern: Profile discovery → User-profile analysis → Permission management workflow Error Recovery: If API fails, verify organization access permissions and try crm_get_organization_details first

Get all roles in the organization

Prerequisites: Use crm_get_all_profiles first to understand profile-role relationships Next Steps: Use crm_get_role_details for specific role analysis → crm_get_all_users to see role assignments → crm_update_role for modifications Common Pattern: Role discovery → Role detail analysis → User assignment review → Role management Error Recovery: If role list is empty, check organization setup with crm_get_organization_details → verify user permissions

Get all territories

Get all users in the organization with optional type filtering (AllUsers, AdminUsers, etc.)

Prerequisites: Use crm_get_all_profiles and crm_get_all_roles first for context Next Steps: Use crm_get_user_details for specific user analysis → crm_get_organization_details for user limits → crm_create_user for new users Common Pattern: User discovery → Individual user analysis → Role/profile assignment → User management operations Error Recovery: If user list incomplete, try different type filters → check organization user limits → verify API permissions

Get assignment rules

Get attachments for a CRM record

Get blueprint metadata

Get complete disposition data including all Global Set values and dependent fields

Get complete module configuration including fields, layouts, custom views, and related lists

Get detailed metadata for a specific custom view including criteria, fields, and sorting

Prerequisites: Use crm_get_custom_views to identify target custom_view_id Next Steps: Use crm_search_records with view criteria → crm_get_fields for field analysis → crm_update_custom_view for modifications Common Pattern: View identification → View configuration analysis → Record retrieval with view → View optimization Error Recovery: If view_id not found, refresh with crm_get_custom_views → verify view still exists → check view permissions

Get all custom views for a module including system and user-defined views

Prerequisites: Use crm_get_all_modules to verify module_name exists and is accessible Next Steps: Use crm_get_custom_view_details for specific view analysis → crm_search_records with view filters → crm_create_custom_view for new views Common Pattern: Module discovery → View listing → View analysis → Record filtering with views → View management Error Recovery: If no views found, verify module_name spelling → check module permissions → try crm_get_module_metadata first

Get fields that depend on a specific field in a module. Useful for understanding field relationships and dependencies.

Get calendar events from CRM with filtering and pagination. Use for viewing meetings, appointments, and scheduled activities.

Related tools: crm_create_event (to schedule), crm_create_task (for follow-ups), crm_get_notes (meeting notes)

Track field change history for records - detailed audit of specific field modifications\n\nPrerequisites: Use crm_search_records or crm_search_by_timeline to find target records\nNext Steps: Use crm_analyze_activity_patterns for trend analysis → Generate change reports\nBusiness Value: Compliance tracking, change audit, data quality monitoring\nError Recovery: If no changes found, verify field names and date range

Get detailed metadata for a specific field including data type, validation rules, picklist values, and dependencies.\n\nPrerequisites:\n→ Use crm_get_fields or crm_get_module_fields first to discover available field names\n→ Have valid module_name and field_name from field discovery\n\nNext Steps:\n→ Use field details for crm_validate_criteria to ensure correct operators\n→ Use crm_get_dependent_fields to understand field relationships\n→ Use field information in crm_search_records criteria\n\nCommon Pattern: crm_get_fields → crm_get_field_details → crm_validate_criteria → crm_search_records\n\nError Recovery: If "Field not found" error, verify field_name with crm_get_fields

Get all field relationships and dependencies in a module. Provides comprehensive analysis of field connections.

Get global fields across all modules (global picklists and lookups)

Get Global Set values by name - specifically for extracting complete disposition data

Get detailed metadata for a specific layout including sections, fields, and display rules.\n\nPrerequisites:\n→ Use crm_get_layouts first to discover available layout IDs\n→ Have valid layout_id from layout discovery\n\nNext Steps:\n→ Use layout details for UI customization analysis\n→ Use crm_update_layout to modify layout configuration\n→ Use section information for field organization workflows\n\nCommon Pattern: crm_get_layouts → crm_get_layout_details → crm_update_layout\n\nError Recovery: If "Layout not found" error, verify layout_id with crm_get_layouts

Get all layouts for modules including page layouts, related lists, and section configurations.\n\nPrerequisites: Use crm_get_all_modules first to discover available modules\n\nNext Steps:\n→ Use crm_get_layout_details for specific layout configuration analysis\n→ Use layout information for UI customization workflows\n→ Use crm_update_layout if modifications are needed\n\nCommon Pattern: crm_get_all_modules → crm_get_layouts → crm_get_layout_details → crm_update_layout\n\nError Recovery: If no layouts found, check module permissions and layout availability

Get comprehensive metadata summary for the entire CRM

Get detailed metadata for a specific module

Get fields for a module with pagination and filtering to avoid large responses

Get notes for a specific CRM record

Get organization details and settings including configuration, limits, and administrative info

Prerequisites: None - foundational tool for understanding organizational context Next Steps: Use crm_get_organization_features for feature analysis → crm_get_all_users for user management → crm_get_all_modules for system scope Common Pattern: Organization discovery → Feature assessment → User/module analysis → Configuration management Error Recovery: If details unavailable, verify API credentials → check admin permissions → try crm_get_organization_features as alternative

Get organization features and limits including API limits, storage, user counts, and enabled features

Prerequisites: Use crm_get_organization_details first for general context Next Steps: Use crm_get_all_users to verify user count against limits → crm_get_all_modules to check feature availability → plan capacity management Common Pattern: Organization assessment → Feature availability check → Capacity planning → Usage optimization Error Recovery: If features not accessible, verify admin permissions → try crm_get_organization_details → check API rate limits

Get only picklist fields for a specific module - optimized for finding disposition/status fields

Get picklist values for a specific field in a module including active, inactive values and display labels.\n\nPrerequisites:\n→ Use crm_get_fields first to identify picklist fields\n→ Have valid module_name and field_name from field discovery\n\nNext Steps:\n→ Use picklist values for crm_validate_criteria with exact value matching\n→ Use values in crm_search_records criteria for filtering\n→ Use for data validation and form building workflows\n\nCommon Pattern: crm_get_fields (identify picklists) → crm_get_picklist_values → crm_search_records (with values)\n\nData Validation: Essential for ensuring accurate search criteria and data entry\nError Recovery: If "Field not found" or "Not a picklist", verify field details with crm_get_fields

Get pipeline metadata

Get all related lists for a module showing relationships with other modules\n\nPrerequisites: Use crm_get_all_modules to verify module_name and understand module relationships\nNext Steps: Use crm_get_module_metadata for related modules → crm_get_records with related data → crm_get_fields for relationship fields\nCommon Pattern: Module relationship discovery → Related module analysis → Cross-module record retrieval → Relationship management\nError Recovery: If no related lists found, verify module_name → check if module supports relationships → try crm_get_module_metadata

Get detailed metadata for a specific role including permissions and hierarchy

Prerequisites: Use crm_get_all_roles to identify target role_id Next Steps: Use crm_get_all_users with role filter → crm_get_all_profiles to see profile associations → crm_update_role for permission changes Common Pattern: Role identification → Detailed role analysis → User impact assessment → Role modification workflow Error Recovery: If role_id not found, refresh with crm_get_all_roles → verify role still exists → check access permissions

Get all tasks from CRM

Get timeline history for a CRM record showing all field changes, activities, and audit trail\n\nPrerequisites: Use crm_search_records to find target record_id\nNext Steps: Use crm_analyze_activity_patterns for trend analysis → crm_get_field_changes for specific field tracking\nComplete Workflow: crm_search_records → crm_get_timeline → analysis\nError Recovery: If timeline empty, verify record_id exists and has activity history

Get detailed metadata for a specific user including roles, profiles, and permissions

Prerequisites: Use crm_get_all_users to identify target user_id Next Steps: Use crm_get_role_details for user's role analysis → crm_get_all_profiles for profile permissions → crm_update_user for modifications Common Pattern: User identification → Detailed user analysis → Permission audit → User configuration changes Error Recovery: If user_id not found, refresh with crm_get_all_users → verify user still active → check access to user data

Search records by timeline events - find records modified within date ranges\n\nPrerequisites: None - timeline-based discovery tool\nNext Steps: Use crm_get_timeline for detailed analysis → crm_get_field_changes for specific tracking\nUse Cases: Recent activity analysis, audit trails, change tracking\nError Recovery: If no results, try broader date range or different action types

Search fields by name pattern - use to find specific fields like "disposition" or "status"

Semantic field search - find fields related to a concept (e.g., "disposition", "status", "reason")

Send email for a CRM record

Smart field discovery - finds fields based on intent with optimized response format to reduce tokens and iterations

Update layout configuration

Update profile permissions

Update role details

Get all departments in Zoho Desk with supported entity types and configuration\n\nPrerequisites: Zoho Desk access with department read permissions\nNext Steps: Use desk_get_entity_fields for entity analysis → desk_search_entities for records\nWorkflow: Department discovery → entity field analysis → ticket/contact operations\nError Recovery: If departments not accessible, verify Desk product access and permissions

Get field metadata for a specific entity type in a Desk department\n\nPrerequisites: Department ID from desk_get_all_departments\nNext Steps: Use field details for desk_search_entities criteria and filtering\nCommon Entities: tickets, contacts, accounts, agents, products\nError Recovery: If fields not found, verify department and entity type are valid

Get timeline/activity history for a specific Desk entity record\n\nPrerequisites: Department ID, entity type, and record ID from desk_search_entities\nNext Steps: Analyze timeline for support patterns, escalations, and resolution tracking\nUse Cases: Ticket lifecycle analysis, customer interaction history, agent performance\nError Recovery: If timeline empty, verify record exists and has activity history

Search entities in a Desk department with flexible filtering and pagination\n\nPrerequisites: Department ID and entity type, optional field details for targeted searches\nNext Steps: Use desk_get_entity_timeline for record activity history\nCommon Patterns: Ticket management, contact lookup, account discovery\nError Recovery: If no results, broaden search criteria or check entity permissions

Get records from any custom module with flexible filtering

Get all available smart query builders across Zoho products. Smart queries are pre-built, business-focused workflows that combine multiple tools to solve common business scenarios.\n\nCategories Available: sales, marketing, finance, hr, support, analytics\n\nProducts Covered: CRM (sales intelligence), Books (financial analysis), People (HR insights), Desk (support optimization)\n\nExample: Get all sales-focused queries\n{"category": "sales"}

Get detailed execution plan for a specific smart query. Shows the complete tool sequence, parameters, and expected outcomes for business intelligence workflows.\n\nPrerequisites: Use get_smart_queries first to discover available query names\n\nNext Steps: Execute the returned tool sequence manually or use as guidance for complex analysis workflows\n\nExample: Get plan for "Hot Leads Pipeline Analysis"\n{"query_name": "Hot Leads Pipeline Analysis"}

List all available tool categories. Use this to understand the organization of tools and find the right category for your task.

List common business scenarios and their recommended smart query solutions. Perfect for discovering workflow automation opportunities.\n\nBusiness Areas: Sales forecasting, Customer retention, Cash flow optimization, Employee performance, Support efficiency\n\nOutput: Curated list of business scenarios with matching smart queries and expected ROI\n\nExample: {}

Get organized list of all tool categories with descriptions. Perfect starting point for LLMs to understand available functionality.

List all available tools grouped by category. Use this to discover tools for specific tasks like customer management, invoice processing, or CRM activities.

Example: List all customer management tools {"category": "Books - Customer Management"}

Get all available Zoho People modules (Employees, Departments, Attendance, etc.)\n\nPrerequisites: Zoho People access with module read permissions\nNext Steps: Use people_get_fields for module field discovery → people_search_records for data retrieval\nWorkflow: Module discovery → field analysis → record operations\nError Recovery: If modules not accessible, verify People product access and API permissions

Get field metadata for a specific People module with detailed schema information\n\nPrerequisites: Module name from people_get_all_modules\nNext Steps: Use field api_name values in people_search_records operations\nCommon Pattern: Module discovery → field analysis → targeted searches\nError Recovery: If fields not found, verify module exists and check field access permissions

Get timeline/activity history for a People record including status changes and updates\n\nPrerequisites: Record ID from people_search_records\nNext Steps: Use timeline data for audit trails and activity analysis\nUse Cases: Employee activity tracking, change auditing, compliance monitoring\nError Recovery: If timeline empty, verify record has activity history and timeline permissions

Search records in a People module with flexible text-based criteria\n\nPrerequisites: Module name from people_get_all_modules, optional field details from people_get_fields\nNext Steps: Use people_get_timeline for record activity analysis\nUse Cases: Employee lookup, department searches, attendance tracking\nError Recovery: If no results, try broader search terms or verify module permissions

Search across CRM and Books records using flexible criteria. Use for finding specific records by name, email, phone, or other fields.

Example: Search for contacts {"module": "contacts", "criteria": "john@example.com", "fields": ["id", "Full_Name", "Email"]}

Sync CRM accounts to Books customers (CRM → Books direction). Creates or updates customer records in Books based on account data from CRM.

Example: Sync 50 accounts {"source_module": "accounts", "target_module": "customers", "filters": {"limit": 50}}

Sync CRM contacts to Books customers (CRM → Books direction). Creates or updates customer records in Books based on contact data from CRM.

Workflow: Typically run after CRM data updates. Follow with books_get_customers to verify sync results

Sync Books customers to CRM contacts (Books → CRM direction). Creates or updates contact records in CRM based on customer data from Books.