Freshservice API

Activates a CSAT Survey by its ID in Freshservice. Use this tool to activate a Customer Satisfaction (CSAT) Survey in Freshservice by providing the survey's ID.

Add a new component to an existing asset. Use this tool to add a new component for a specific asset in Freshservice. It should be called when you need to track additional components associated with an asset.

Add a new note to a problem in Freshservice. Use this tool to create and add a new note to an existing problem in Freshservice, helping track updates or relevant information.

Create a new note on a release in Freshservice. Use this tool to add a note to a specific release in Freshservice. It should be called when you need to document or update information about a release.

Log a new time entry for a specific release in Freshservice. This tool is used to create a new time entry on a release within the Freshservice platform. It should be called when there's a need to record the time spent on a release. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Add a new note to a Freshservice ticket. Use this tool to post a new note on a specific Freshservice ticket by providing the ticket ID. This is useful for updating ticket information, providing status updates, or adding additional details related to the ticket. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Archive an existing project in Freshservice. Use this tool to archive a project within Freshservice. This is useful for organizing and managing completed or inactive projects.

Convert an agent to a requester in Freshservice. Use this tool to convert an agent, identified by their ID, into a requester in Freshservice. This action is typically used when an agent no longer needs agent-level access.

Convert a requester to an agent in Freshservice. Use this tool to convert a Freshservice requester into an occasional agent with the SD Agent role. This action removes any existing group memberships from the requester.

Create a new Agent Group in Freshservice. This tool allows you to create a new Agent Group in Freshservice. Use it to organize and manage agents within your Freshservice account. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new announcement in Freshservice. Use this tool to create a new announcement in Freshservice, ideal for disseminating information or updates within your service platform. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new asset type in Freshservice. Use this tool to create a new asset type in Freshservice when setting up or managing assets. It automates the process of defining asset categories in the system.

Create a new canned response folder in Freshservice. This tool creates a new canned response folder in Freshservice. Use it when you need to organize canned responses into a new folder within the Freshservice platform.

Create a new note on a change request in Freshservice. This tool creates a new note attached to a specific change request in Freshservice. It should be called when there's a need to append additional information or updates related to an ongoing change request.

Create a task on a change request in Freshservice. This tool creates a new task on a specified change request within Freshservice. It should be called when you need to add tasks to an ongoing change request to track specific actions or activities. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new child ticket on a Freshservice ticket. Use this tool to add a child ticket to an existing ticket in Freshservice. It is useful for managing ticket hierarchies and organizing support tasks. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new CSAT survey in Freshservice. This tool is used to create a new Customer Satisfaction (CSAT) survey in Freshservice. Call this tool when you need to set up a survey to gather customer feedback. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a custom ticket source in Freshservice. Use this tool to create a custom ticket source within the Freshservice platform. Ideal for when you need to define new ticket origin types beyond the defaults provided.

Create a new agent in Freshservice. This tool allows you to create a new agent in Freshservice. Use it when you need to add a team member to your Freshservice account. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new canned response in Freshservice. Use this tool to create a new canned response in a Freshservice account. It should be called when there is a need to automate the creation of standard replies to frequent inquiries. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new Change request in Freshservice. Use this tool to initiate a new Change request within the Freshservice platform. This is typically called when a user wants to propose a change that needs to be tracked and managed through Freshservice. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a time entry for a change request in Freshservice. Use this tool to log a new time entry associated with a specific change request in Freshservice. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new task on a problem in Freshservice. This tool creates a new task associated with a specific problem in the Freshservice system. Use it when you need to assign tasks to a problem for better issue management. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new project in Freshservice. Use this tool to create a new project within the Freshservice platform. This is useful for managing tasks, timelines, and resources efficiently in Freshservice. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new support ticket in Freshservice. Use this tool to generate a new support ticket in Freshservice, which is useful for tracking and managing customer support issues. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new asset in Freshservice. Use this tool to add a new asset to the Freshservice system. Ideal for tracking and managing assets efficiently. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new location in Freshservice. Use this tool to create a new location within the Freshservice platform. It should be called when there is a need to add a new geographical or organizational location to the service database.

Create a new problem in Freshservice. Use this tool to create a new problem in Freshservice when you need to log an issue or fault that may require investigation and resolution. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new product in the Freshservice catalog. Use this tool to add a new product to the Freshservice Product Catalog. It is called when a new product entry is needed in the inventory or catalog database.

Create a new requester in Freshservice. Use this tool to add a new requester to Freshservice whenever you need to register someone in the system. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Creates a new vendor in the Freshservice system. Use this tool to create a new vendor in Freshservice. Call this tool when you need to add a vendor to your vendor list, providing necessary details to complete the registration.

Create a new onboarding request in Freshservice. Use this tool to initiate a new employee onboarding process in Freshservice. It should be called when a new hire needs to be onboarded, capturing all necessary details and confirming the creation of the request. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new time entry for a problem in Freshservice. This tool creates a new time entry on a specified problem in Freshservice. It should be called when you need to log time spent on a problem within the service. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new project task in Freshservice. Use this tool to create a new project task within Freshservice. It should be called when you need to add a task to an existing project. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new Purchase Order in Freshservice. This tool is used to create a new Purchase Order in Freshservice. It should be called when a new order needs to be generated and recorded within the Freshservice system. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Initiate a new release request in Freshservice. This tool is used to create a new release request in Freshservice. It should be called when a user wants to start tracking or managing a release process within the Freshservice platform. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new task on a Freshservice release. Use this tool to add a new task to a specific release in Freshservice, enabling detailed release management and tracking. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new solution article in Freshservice. Use this tool to add a new solution article to Freshservice. Call this tool when you need to document solutions or FAQs within the Freshservice platform. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new solution category in Freshservice. This tool is used to create a new solution category in Freshservice. It should be called when you need to organize solutions by adding a new category in the Freshservice platform.

Create a new solution folder in Freshservice. Use this tool to create a new solution folder in Freshservice, helping organize solutions efficiently. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new task for a ticket in Freshservice. Use this tool to add a new task to an existing ticket in Freshservice. It should be called when a new task needs to be organized or managed within a specific ticket. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Create a new time entry on a Freshservice ticket. Use this tool to log a new time entry for a specific ticket in Freshservice. Useful for tracking time spent on ticket resolution or management. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Deactivate a CSAT survey in Freshservice using its ID. Use this tool to deactivate a Customer Satisfaction (CSAT) survey in Freshservice by providing the survey's ID. This is helpful when a survey is no longer needed or should not be sent to customers.

Permanently delete an agent and their requested tickets. Use this tool to permanently delete an agent from the system along with any tickets they have requested.

Deletes an Agent Group in Freshservice by ID. Use this tool to delete an existing agent group in Freshservice by providing its ID. This is useful when you need to manage or reorganize agent groups by removing those that are no longer required.

Delete a specific component from an asset in Freshservice. Use this tool to delete a specific component from an asset using Freshservice. It requires the asset's display ID and the component ID to successfully process the deletion request.

Delete an existing asset type from Freshservice. This tool is used to delete an asset type in Freshservice. It should be called when an asset type is no longer needed and needs to be removed from the system.

Delete a Canned Response from Freshservice. Use this tool to delete a specific Canned Response in Freshservice by providing its ID. Ideal for managing and cleaning up unused or outdated responses.

Deletes a specified Canned Response Folder in Freshservice. This tool deletes a Canned Response Folder from Freshservice using the provided folder ID. Use it when you need to remove a specific folder.

Delete a note from a Change request by ID in Freshservice. Use this tool to delete a specific note from a Change request in Freshservice by providing the change ID and note ID.

Delete a change request by ID from Freshservice. Use this tool to delete a specific change request from Freshservice by providing the change ID. It confirms the deletion of the request.

Delete a task from a Freshservice change request. This tool deletes a specified task from a change request in Freshservice using the change and task IDs.

Deletes a specific time entry from a change request in Freshservice. Use this tool to delete a time entry associated with a specific change request in Freshservice. It requires the IDs of the change request and the time entry to process the deletion.

Delete a department or company in Freshservice by ID. Use this tool to delete a specific department or company (in MSP Mode) from Freshservice by providing the department ID. It should be called when needing to remove a department permanently.

Delete an announcement from Freshservice by ID. Use this tool to delete a specific announcement in Freshservice by providing the announcement ID. It confirms the successful deletion of the announcement.

Delete a problem by ID from Freshservice. Use this tool to delete a specific problem from Freshservice using its ID. This operation is useful when you need to remove a resolved or irrelevant problem from the system.

Delete a specific note from a problem in Freshservice. Use this tool to delete a specific note from a problem in Freshservice by providing the problem ID and note ID.

Delete a specific time entry from a Freshservice problem. Use this tool to delete a specific time entry associated with a problem in Freshservice by providing the problem and time entry IDs.

Delete an existing project in Freshservice. Use this tool to delete a specified project by its ID in the Freshservice platform. Ideal for managing and removing outdated or unnecessary projects.

Delete a release from Freshservice by its ID. Use this tool to delete a specific release in Freshservice when you have the release ID available. This is useful for managing and cleaning up outdated or erroneous releases in the system.

Deletes an existing location by ID. Use this tool to delete a specified location by providing its ID in the Freshservice system.

Delete a specific task from a problem in Freshservice. Use this tool to delete a task associated with a specific problem in Freshservice by providing the problem and task IDs.

Delete a product from the catalog. Use this tool to remove an existing product from the Freshservice Product Catalog. Useful for managing inventory or updating product listings by deleting outdated or irrelevant entries.

Delete a project task in Freshservice. This tool deletes an existing project task in Freshservice. Use it when you need to remove a specific task from a project by providing the project and task identifiers.

Delete a purchase order in Freshservice by ID. Use this tool to delete a specific purchase order from Freshservice by providing its ID. This is useful when a purchase order needs to be permanently removed from the system.

Deletes a specific release note in Freshservice. Use this tool to delete a note associated with a release in Freshservice by specifying the release and note IDs.

Delete a specific task from a release in Freshservice. Use this tool to delete a task from a specific release in Freshservice by providing the release ID and task ID.

Delete a specific time entry from a release in Freshservice. Use this tool to delete a specific time entry associated with a release in Freshservice by providing the release ID and time entry ID.

Delete a requester from Freshservice by ID. Use this tool to remove a requester from Freshservice using their unique ID. It should be called when a requester needs to be permanently deleted from the system.

Permanently delete a requester and their tickets in Freshservice. This tool is used to permanently remove a requester and all of their associated tickets from Freshservice. It should be called when you need to completely erase a requester's data, including all their ticket history.

Delete a specific solution article from Freshservice. Use this tool to delete a solution article in Freshservice by providing its ID. This can be useful for managing outdated or incorrect articles within the service.

Delete a solution category in Freshservice by ID. Use this tool to delete a specific solution category from Freshservice using the category ID. This is useful when you need to remove outdated or incorrect categories from your knowledge base.

Delete a solution folder from Freshservice. Use this tool to delete a solution folder by its ID in Freshservice when cleanup or reorganization is needed.

Delete a survey and its responses from Freshservice. Use this tool to delete a specific survey from Freshservice by providing the survey ID. This action will remove the survey along with all its underlying responses.

Deletes a task from a Freshservice ticket. This tool deletes a specific task associated with a ticket in Freshservice, identified by the ticket and task ID. Use this to manage and update tasks on tickets efficiently.

Delete a time entry from a Freshservice ticket. Use this tool to delete a specific time entry from a ticket in Freshservice when it is no longer needed or was added incorrectly.

Delete an existing vendor in Freshservice. This tool deletes a specified vendor in Freshservice. It should be called when a user needs to remove a vendor from the system using the vendor's unique ID.

Edit a Freshservice ticket efficiently. This tool is used to update the details of an existing ticket in Freshservice. It should be called when modifications or updates to a ticket's information are needed, such as changing the status, priority, or other relevant ticket details. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Edit a conversation in a Freshservice ticket. Use this tool to edit the conversation on an existing Freshservice ticket. It is useful for updating information, correcting errors, or adding new details to a specific conversation within a ticket. Note: Understanding the request schema is necessary to properly create the stringified JSON input object for execution. This operation also requires path parameters. Modes: - GET_REQUEST_SCHEMA: Returns the schema. Only call if you don't already have it. Do NOT call repeatedly if you already received the schema. - EXECUTE: Performs the operation with the provided request body JSON. Note: You must also provide the required path parameters when executing. If you need the schema, call with mode='get_request_schema' ONCE, then execute.

Retrieve all agent fields in Freshservice. Use this tool to get a complete list of agent fields from Freshservice. This could be useful for understanding the available fields when managing agents.

Retrieve a specific onboarding request by ID. Use this tool to get details about a specific onboarding request from Freshservice by providing the request ID.

Retrieve tickets for specific onboarding requests. This tool fetches details of FreshService Tickets linked to a particular Onboarding Request. Use it to access related ticket information based on the onboarding request ID.

Retrieve requester details using their ID from Freshservice. Use this tool to get detailed information about a requester by providing their ID through Freshservice's API.

Retrieve details of a specific location by ID. This tool retrieves detailed information about a specific location using its ID. It should be used when needing to fetch data related to a particular location in Freshservice.

Retrieve a specific time entry for a ticket in Freshservice. This tool is used to fetch details of a specific time entry associated with a ticket in Freshservice by providing the ticket and time entry IDs.

Retrieve a list of all agent groups from Freshservice. Use this tool to obtain a list of all the agent groups configured in your Freshservice account. It is useful for managing groups and understanding team structures within the system.

Retrieve a list of all requesters in Freshservice. Call this tool to get a comprehensive list of all requesters from the Freshservice platform.

Retrieve licenses for a specified software application. Use this tool to get a list of all licenses linked to a particular software application within Freshservice.

Retrieve contracts linked to a specific asset. Use this tool to obtain all contracts associated with a particular asset identified by its display ID. Ideal for managing asset-related agreements and tracking contract details.

Retrieve requests linked to a specific asset. Use this tool to get a list of all requests associated with a specific asset by its display ID.

Retrieve asset fields from Freshservice. Fetches asset fields for a specific asset type from Freshservice, including default and specific fields, in their UI display order.

Retrieve the Business Hours configuration from Freshservice. This tool retrieves the Business Hours configuration using the provided ID from Freshservice. It should be called when detailed information about specific business hours settings is required.

Retrieve all business hours configurations from Freshservice. This tool retrieves the entire list of business hours configurations from Freshservice. It should be called when you need to understand or display the business hours settings configured in the Freshservice system.

Retrieve details of a Freshservice canned response by ID. Use this tool to obtain the details of a specific canned response from Freshservice, given its unique ID.

Retrieve a specific canned response folder from Freshservice. Use this tool to fetch the details of a specific canned response folder by its ID from Freshservice. It is helpful for accessing pre-defined response templates for customer support or information retrieval.

Retrieve all canned response folders from Freshservice. This tool retrieves a list of all canned response folders available in Freshservice. It should be called when you need to access or manage pre-written responses for different scenarios or queries in Freshservice.

Retrieve fields for the Change Object in Freshservice. Use this tool to obtain a list of all fields that make up the Change Object in Freshservice. Ideal for understanding the structure or schema of change forms.

Retrieve a specific change request by ID from Freshservice. Use this tool to access information about a specific change request in Freshservice by providing its unique ID.

Retrieve notes from a Freshservice change request. Use this tool to get all notes associated with a specific change request ID in Freshservice.

Retrieve tasks for a specific Change request from Freshservice. Use this tool to get all tasks associated with a specific Change request using its ID in Freshservice. Ideal for managing or reviewing change tasks.

Retrieve time entries for a specific Change request. Use this tool to get all time entries associated with a specific Change request in Freshservice by providing the Change ID.

Retrieve a list of all CSAT Surveys in Freshservice.

Retrieve department fields from Freshservice. Use this tool to get the Department Fields or Company Fields (in MSP Mode) from Freshservice, displayed in the order found on the UI.

Retrieve department details from Freshservice using an ID. Use this tool to obtain detailed information about a department or company (in MSP Mode) from Freshservice by providing the specific department ID.

Retrieve all components of a specific device. This tool retrieves a list of all components associated with a specified device by its display ID. Use this to gain detailed insights into the individual parts of a device.

Retrieve details of a Freshservice agent by ID. Use this tool to obtain information about a specific agent in Freshservice by providing the agent's ID. It can be called when detailed agent information is needed for administration or support purposes.

Retrieve a specific announcement from Freshservice. Call this tool to get details of an announcement using its ID from Freshservice.

Retrieve a list of all announcements from Freshservice. Use this tool to get all current announcements in Freshservice. Call this when you need to display or access information about company or service announcements.

Retrieve a list of all changes in Freshservice. Use this tool to get a comprehensive list of changes in Freshservice. It can be called when you need to access or review all changes recorded in the Freshservice system.

Retrieve a list of departments from Freshservice. Use this tool to get a list of all departments or companies (in MSP Mode) available in Freshservice.

Retrieve all problems from Freshservice. This tool fetches a list of all problems recorded in Freshservice. It should be called when there is a need to access or review issues tracked in the system.

Retrieve release details from Freshservice by ID. Call this tool to obtain specific release details from Freshservice using a provided release ID.

Retrieve a list of all Releases in Freshservice. Use this tool to obtain a complete list of all Releases within the Freshservice platform. Useful for tracking, managing, and reviewing release information.