Automate Kommo CRM operations -- manage leads, pipelines, pipeline stages, tasks, and custom fields -- using natural language through the Composio MCP integration.
SKILL.md
Kommo Automation
Manage your Kommo CRM sales pipeline -- list and filter leads, navigate pipeline stages, create and update deals, assign tasks, and work with custom fields -- all through natural language commands.
Assign follow-up tasks linked to leads, contacts, or companies.
Tool:KOMMO_CREATE_TASK
Example prompt:
"Create a follow-up call task for lead 789 due tomorrow assigned to user 42"
Key parameters:
Task text/description
Entity type and ID (lead, contact, company)
Responsible user ID
Due date (Unix timestamp)
Task type
6. Discover Custom Fields
List all custom fields for leads, contacts, or companies to understand your CRM schema.
Tool:KOMMO_LIST_CUSTOM_FIELDS
Example prompt:
"What custom fields are available for leads in Kommo?"
Key parameters:
Entity type (leads, contacts, companies)
Known Pitfalls
Date filters use Unix timestamps: All date range filters (filter_created_at, filter_updated_at, filter_closed_at) require Unix timestamp format in {"from": <timestamp>, "to": <timestamp>} structure, not ISO8601 strings.
Pipeline and stage IDs are required: To filter leads by status, you need both pipeline_id and status_id. Always call KOMMO_LIST_LEADS_PIPELINES and KOMMO_LIST_PIPELINE_STAGES first to discover valid IDs.
Max 250 leads per page: The limit parameter caps at 250. For large datasets, implement pagination using the page parameter.
Custom field values format: Custom fields use a specific nested object format. Use KOMMO_LIST_CUSTOM_FIELDS to discover field IDs and expected value formats before setting values.
Status filter requires both IDs: The filter_status parameter requires both pipeline_id and status_id as a combined object -- you cannot filter by status alone.
Created_by 0 means robot: When setting created_by or updated_by to 0, the action is attributed to a robot/automation, not a human user.
