メニュー
Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/BEKO2210/Firstbrain --skill freshdesk-automationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SOC 職業分類に基づく
SKILL.md を表示中
| name | freshdesk-automation |
| description | Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes, and replies via Rube MCP (Composio). Always search tools first for current schemas. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | productivity |
| category | automation |
| risk | critical |
| source | community |
| tags | ["skill","productivity","automation","freshdesk"] |
Automate Freshdesk customer support workflows including ticket management, contact and company operations, notes, replies, and ticket search through Composio's Freshdesk toolkit.
RUBE_MANAGE_CONNECTIONS with toolkit freshdeskRUBE_SEARCH_TOOLS first to get current tool schemasGet 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.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit freshdeskWhen to use: User wants to create a new support ticket, update an existing ticket, or view ticket details.
Tool sequence:
FRESHDESK_SEARCH_CONTACTS - Find requester by email to get requester_id [Optional]FRESHDESK_LIST_TICKET_FIELDS - Check available custom fields and statuses [Optional]FRESHDESK_CREATE_TICKET - Create a new ticket with subject, description, requester info [Required]FRESHDESK_UPDATE_TICKET - Modify ticket status, priority, assignee, or other fields [Optional]FRESHDESK_VIEW_TICKET - Retrieve full ticket details by ID [Optional]Key parameters for FRESHDESK_CREATE_TICKET:
subject: Ticket subject (required)description: HTML content of the ticket (required)email: Requester email (at least one requester identifier required)requester_id: User ID of requester (alternative to email)status: 2=Open, 3=Pending, 4=Resolved, 5=Closed (default 2)priority: 1=Low, 2=Medium, 3=High, 4=Urgent (default 1)source: 1=Email, 2=Portal, 3=Phone, 7=Chat (default 2)responder_id: Agent ID to assign the ticket togroup_id: Group to assign the ticket totags: Array of tag stringscustom_fields: Object with cf_<field_name> keysPitfalls:
requester_id, email, phone, facebook_id, twitter_id, or unique_external_idphone is provided without email, then name becomes mandatorydescription supports HTML formattingattachments field expects multipart/form-data format, not file paths or URLscf_ (e.g., cf_reference_number)When to use: User wants to find tickets by status, priority, date range, agent, or custom fields.
Tool sequence:
FRESHDESK_GET_TICKETS - List tickets with simple filters (status, priority, agent) [Required]FRESHDESK_GET_SEARCH - Advanced ticket search with query syntax [Required]FRESHDESK_VIEW_TICKET - Get full details for specific tickets from results [Optional]FRESHDESK_LIST_TICKET_FIELDS - Check available fields for search queries [Optional]Key parameters for FRESHDESK_GET_TICKETS:
status: Filter by status integer (2=Open, 3=Pending, 4=Resolved, 5=Closed)priority: Filter by priority integer (1-4)agent_id: Filter by assigned agentrequester_id: Filter by requesteremail: Filter by requester emailcreated_since: ISO 8601 timestamppage / per_page: Pagination (default 30 per page)sort_by / sort_order: Sort field and directionKey parameters for FRESHDESK_GET_SEARCH:
query: Query string like "status:2 AND priority:3" or "(created_at:>'2024-01-01' AND tag:'urgent')"page: Page number (1-10, max 300 total results)Pitfalls:
FRESHDESK_GET_SEARCH query must be enclosed in double quotesnull keyword to find tickets with empty fields (e.g., "agent_id:null")FRESHDESK_LIST_ALL_TICKETS takes no parameters and returns all tickets (use GET_TICKETS for filtering)When to use: User wants to send a reply to a customer, add internal notes, or view conversation history.
Tool sequence:
FRESHDESK_VIEW_TICKET - Verify ticket exists and check current state [Prerequisite]FRESHDESK_REPLY_TO_TICKET - Send a public reply to the requester [Required]FRESHDESK_ADD_NOTE_TO_TICKET - Add a private or public note [Required]FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS - View all messages and notes on a ticket [Optional]FRESHDESK_UPDATE_CONVERSATIONS - Edit an existing note [Optional]Key parameters for FRESHDESK_REPLY_TO_TICKET:
ticket_id: Ticket ID (integer, required)body: Reply content, supports HTML (required)cc_emails / bcc_emails: Additional recipients (max 50 total across to/cc/bcc)from_email: Override sender email if multiple support emails configureduser_id: Agent ID to reply on behalf ofKey parameters for FRESHDESK_ADD_NOTE_TO_TICKET:
ticket_id: Ticket ID (integer, required)body: Note content, supports HTML (required)private: true for agent-only visibility, false for public (default true)notify_emails: Only accepts agent email addresses, not external contactsPitfalls:
FRESHDESK_REPLY_TO_TICKET (more features) and FRESHDESK_REPLY_TICKET (simpler); both workFRESHDESK_ADD_NOTE_TO_TICKET defaults to private (agent-only); set private: false for public notesnotify_emails in notes only accepts agent emails, not customer emailsFRESHDESK_UPDATE_CONVERSATIONS; incoming replies cannot be editedWhen to use: User wants to create, search, or manage customer contacts and company records.
Tool sequence:
FRESHDESK_SEARCH_CONTACTS - Search contacts by email, phone, or company [Required]FRESHDESK_GET_CONTACTS - List contacts with filters [Optional]FRESHDESK_IMPORT_CONTACT - Bulk import contacts from CSV [Optional]FRESHDESK_SEARCH_COMPANIES - Search companies by custom fields [Required]FRESHDESK_GET_COMPANIES - List all companies [Optional]FRESHDESK_CREATE_COMPANIES - Create a new company [Optional]FRESHDESK_UPDATE_COMPANIES - Update company details [Optional]FRESHDESK_LIST_COMPANY_FIELDS - Check available company fields [Optional]Key parameters for FRESHDESK_SEARCH_CONTACTS:
query: Search string like "email:'user@example.com'" (required)page: Pagination (1-10, max 30 per page)Key parameters for FRESHDESK_CREATE_COMPANIES:
name: Company name (required)domains: Array of domain strings for auto-association with contactshealth_score: "Happy", "Doing okay", or "At risk"account_tier: "Basic", "Premium", or "Enterprise"industry: Standard industry classificationPitfalls:
FRESHDESK_SEARCH_CONTACTS requires exact matches; partial/regex searches are not supportedFRESHDESK_SEARCH_COMPANIES cannot search by standard name field; use custom fields or created_atcf_ prefix (unlike ticket custom fields)domains on companies enables automatic contact-to-company association by email domainAlways resolve display values to IDs before operations:
FRESHDESK_SEARCH_CONTACTS with "email:'user@example.com'"FRESHDESK_GET_COMPANIES and match by name (search by name not supported)Freshdesk uses page-based pagination:
FRESHDESK_GET_TICKETS: page (starting at 1) and per_page (max 100)FRESHDESK_GET_SEARCH: page (1-10, 30 results per page, max 300 total)FRESHDESK_SEARCH_CONTACTS: page (1-10, 30 per page)FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS: page and per_page (max 100)cf_ prefix; company custom fields do NOTdescription in tickets supports HTML formattingFRESHDESK_LIST_ALL_TICKETS returns all tickets with no filter parameters| Task | Tool Slug | Key Params |
|---|---|---|
| Create ticket | FRESHDESK_CREATE_TICKET | subject, description, email, priority |
| Update ticket | FRESHDESK_UPDATE_TICKET | ticket_id, status, priority |
| View ticket | FRESHDESK_VIEW_TICKET | ticket_id |
| List tickets | FRESHDESK_GET_TICKETS | status, priority, page, per_page |
| List all tickets | FRESHDESK_LIST_ALL_TICKETS | (none) |
| Search tickets | FRESHDESK_GET_SEARCH | query, page |
| Reply to ticket | FRESHDESK_REPLY_TO_TICKET | ticket_id, body, cc_emails |
| Reply (simple) | FRESHDESK_REPLY_TICKET | ticket_id, body |
| Add note | FRESHDESK_ADD_NOTE_TO_TICKET | ticket_id, body, private |
| List conversations | FRESHDESK_LIST_ALL_TICKET_CONVERSATIONS | ticket_id, page |
| Update note | FRESHDESK_UPDATE_CONVERSATIONS | conversation_id, body |
| Search contacts | FRESHDESK_SEARCH_CONTACTS | query, page |
| List contacts | FRESHDESK_GET_CONTACTS | email, company_id, page |
| Import contacts | FRESHDESK_IMPORT_CONTACT | file, name_column_index, email_column_index |
| Create company | FRESHDESK_CREATE_COMPANIES | name, domains, industry |
| Update company | FRESHDESK_UPDATE_COMPANIES | company_id, name, domains |
| Search companies | FRESHDESK_SEARCH_COMPANIES | query, page |
| List companies | FRESHDESK_GET_COMPANIES | page |
| List ticket fields | FRESHDESK_LIST_TICKET_FIELDS | (none) |
| List company fields | FRESHDESK_LIST_COMPANY_FIELDS | (none) |
This skill is applicable to execute the workflow or actions described in the overview.