Knit's Freshworks CRM MCP Server gives your AI agents instant, code-free access to every Freshworks CRM API endpoint-read, write, and automate without OAuth headaches or custom endpoints.
4.9/5 on G2·
Google for Startups Accelerator
All the power of AI-ready tools — serverless hosting, mix-and-match APIs, live updates, semantic search, and built-in auth — in a single, plug-and-play platform.
Spin up MCP Servers with zero infrastructure — Knit scales, patches, and monitors everything for you.
Deploy only the API tools you need from any app in a single lightweight server — no bloat, no duplication.
Expose custom endpoints as AI-ready tools alongside Knit's catalog, unifying proprietary logic and third-party apps in one place.
Natural-language search surfaces the right tools for each use case, shrinking token costs and boosting LLM accuracy.
Add or remove tools without downtime; your agents see new capabilities instantly — no server restarts required.
OAuth, SAML, service accounts — Knit manages credentials and refreshes so your team never wrestles with tokens.
Watch an agent automate workflows — all with Knit's plug-and-play MCP Servers.
Every action below is real and already live — not a roadmap item. Browse the full API reference →
The Get CRM Deal Stages API retrieves the stages of deals in a CRM system. It requires an 'accept' header specifying 'application/json'. The response includes a success flag and data containing an array of stages, each with a stageId, stageName, pipelineId, and pipelineName. In case of an error, an error message is provided.
The Update CRM Custom Objects Schema API allows users to update the schema of custom objects in the CRM system. The request requires headers specifying the content type as 'application/json'. The request body must include 'schemaId', 'title', 'titlePluralized', and 'description' as required fields. The response will indicate success with a boolean and may include data or an error message if unsuccessful.
The Create CRM Lead API allows users to create a new lead in the CRM system. The API requires a POST request to the specified endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body should include details about the lead such as first name, last name, job title, company, description, owner information, industry, number of employees, and address details. The response will indicate success or failure of the operation, with a success flag and optional data or error message.
The Update CRM Account API allows users to update details of an existing CRM account. The API requires a POST request to the specified endpoint with headers indicating the content type as application/json. The request body must include the accountId and owner details, and can optionally include other account details such as name, description, industry, website, number of employees, address, phone number, and custom fields. The response will indicate success or failure of the operation, with a success flag and optional data or error message.
The Create CRM Deal API allows users to create a new deal in the CRM system. The API requires a POST request to the endpoint https://api.getknit.dev/v1.0/crm.deal.create with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the 'name', 'owner', and 'stageId' fields, along with optional fields such as 'description', 'amount', 'currency', 'pipelineId', 'account', 'contact', and 'customFields'. The response will indicate success with a boolean and provide the ID of the created deal. In case of an error, a descriptive error message will be returned.
The Delete CRM Engagement API allows users to delete a specific engagement from the CRM system. The API requires a POST request to the endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include 'engagementId' and 'type' as required fields. On success, the API returns a response with 'success' set to true and 'data' as null. In case of an error, 'success' is false and an 'error' object with a descriptive message is returned.
This API endpoint allows the creation of a CRM custom object record. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'name', 'description', 'fields', and 'metadata'. The response will indicate success with a 'recordId' if successful, or an error message if not.
The List CRM Users API endpoint retrieves a list of users from the CRM system. It requires an 'accept' header specifying 'application/json'. The response includes a 'success' boolean indicating the request status, and if successful, a 'data' object containing an array of 'users', each with 'email' and 'id'. If unsuccessful, an 'error' object with a 'msg' is returned.
The Update CRM Contact API allows users to update the details of an existing contact in the CRM system. The API requires a POST request to the specified endpoint with headers indicating the content type as application/json. The request body must include the contactId of the contact to be updated, and can optionally include other fields such as firstName, lastName, email, industry, jobTitle, owner details, address, phoneNumber, account ID, and custom fields. The response will indicate success or failure of the operation, with a success flag and optional data or error message.
The Create CRM Contact API allows users to create a new contact in the CRM system. The API requires a POST request to the specified endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the contact's first name, last name, email, and owner information. Optional fields include industry, job title, address, phone number, account ID, and custom fields. The response will indicate success with the ID of the created contact or provide an error message if the operation fails.
The Create CRM Engagement API allows users to create a new engagement in the CRM system. The API requires a POST request to the endpoint with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include details such as the type of engagement (CALL, MEETING, EMAIL, etc.), subject, direction (INBOUND or OUTBOUND), content, owner details (id and email), start and end date-time, channel for communication, custom fields, and metadata. The response will indicate success with a boolean and may include data or an error message if the request fails.
The Create CRM Account API allows users to create a new account in the CRM system. It requires a POST request to the endpoint https://api.getknit.dev/v1.0/crm.account.create with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include the account's name and owner details, and can optionally include additional information such as description, industry, website, number of employees, address, phone number, and custom fields. The response will indicate success and provide the ID of the created account, or an error message if the request fails.
This API endpoint allows the creation of a custom object schema in the CRM system. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include the schemaId, title, titlePluralized, description, fields, and metadata. The response will indicate success with a boolean and return the schemaId if successful. In case of an error, a descriptive error message will be provided.
The Delete CRM Account API allows users to delete a CRM account by providing the account ID. The request is made using the POST method to the endpoint https://api.getknit.dev/v1.0/crm.account.delete. The request headers must include 'accept' and 'content-type' both set to 'application/json'. The request body must contain the 'accountId' of the account to be deleted. On success, the API returns a response with 'success' set to true and 'data' as null. If there is an error, 'success' is false and an 'error' object with a descriptive message is returned.
The Update CRM Deal API allows users to update the details of an existing deal in the CRM system. The API requires a POST request to the specified endpoint with headers indicating the content type as application/json. The request body must include the 'dealId' as a required field, along with optional fields such as 'name', 'description', 'amount', 'currency', 'owner', 'stageId', 'pipelineId', 'account', 'contact', and 'customFields'. The response will indicate success with a boolean value and may include additional data or an error message if the operation fails.
The List CRM Fields API allows users to retrieve a list of fields for a specified CRM object type. The API requires a query parameter 'object' to specify the CRM object type such as 'account', 'contact', 'deal', 'lead', or 'engagement'. An optional 'subType' parameter can be used for CRMs where the engagement object is made up of sub-objects. The response includes a success flag and data containing mapped and unmapped fields with their IDs and labels.
This API endpoint allows the creation of a custom object field in the CRM system. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'fieldId', 'title', and 'type' as required fields, with 'metadata' being optional. The response will indicate success with the 'success' field and return the 'schemaId' and 'fieldId' in the 'data' object. In case of an error, the 'success' field will be false, and an 'error' object will provide a descriptive message.
This API endpoint is used to delete a field from a custom object in the CRM. It requires a POST request to the specified URL with headers specifying 'accept' and 'content-type' as 'application/json'. The request body must include 'schemaId' and 'fieldId' to identify the field to be deleted. On success, it returns a response with 'success' set to true and 'data' as null. If there is an error, 'success' is false and an 'error' object with a descriptive message is returned.
This API endpoint deletes a record from a custom object in the CRM. It requires the schema ID and record ID as input in the request body. The response indicates whether the operation was successful. If successful, the response contains a success flag and null data. If unsuccessful, it contains an error message.
The Delete CRM Deal API allows users to delete a specific deal from the CRM system. The request requires the 'dealId' in the request body to identify which deal to delete. The request headers must include 'accept' and 'content-type' set to 'application/json'. A successful response will return a 'success' boolean set to true and 'data' as null. If the operation fails, 'success' will be false and an 'error' object with a descriptive message will be provided.
This API endpoint retrieves the fields of a custom object in a CRM system. It requires the schema ID as input in the request body. The response includes a success flag and a list of fields with details such as field ID, title, type, creation and update timestamps, description, and the IDs of the user who created and last updated the field. In case of an error, an error message is returned.
This API endpoint deletes a CRM custom object schema identified by the provided schemaId. It requires the schemaId to be specified in the request body. The request must include headers specifying 'accept' and 'content-type' as 'application/json'. On success, it returns a response with 'success' set to true and 'data' as null. If an error occurs, 'success' is false and an 'error' object with a descriptive message is returned.
The Delete CRM Contact API allows users to delete a contact from the CRM system. It requires a POST request to the endpoint with a JSON body containing the 'contactId' of the contact to be deleted. The request headers must include 'accept' and 'content-type' set to 'application/json'. On success, the API returns a JSON response with 'success' set to true and 'data' as null. If an error occurs, 'success' is false and an 'error' object with a descriptive message is returned.
This API endpoint allows updating fields of custom objects in a CRM system. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'fieldId', 'title', and 'type' to specify the field to be updated and its new attributes. The response will indicate success with a boolean 'success' field and may include additional data or error information.
The Update CRM Engagement API allows users to update details of an existing CRM engagement. The API requires a POST request to the specified endpoint with headers 'accept' and 'content-type' set to 'application/json'. The request body must include the 'engagementId' as a required field, along with optional fields such as 'type', 'subject', 'direction', 'content', 'owner', 'startDateTime', 'endDateTime', and 'channel'. The response will indicate success with a boolean 'success' field and may include an error message if the operation fails.
The Update CRM Lead API allows users to update the details of a lead in the CRM system. The API requires a POST request to the specified endpoint with headers indicating the content type as application/json. The request body must include the leadId, which is mandatory, and can optionally include other details such as firstName, lastName, jobTitle, company, description, owner information, industry, number of employees, and address details. The response will indicate success or failure of the operation, with a success flag and optional data or error message.
This API endpoint retrieves the schemas of custom objects in the CRM. It requires an 'accept' header with the value 'application/json'. The response includes a success flag and a data object containing an array of schema objects. Each schema object includes details such as schemaId, createdAt, updatedAt, title, titlePluralized, description, createdById, and updatedById. In case of an error, the response includes a success flag set to false and an error object with a descriptive message.
The Delete CRM Lead API allows users to delete a lead from the CRM system. It requires a POST request to the endpoint with the leadId in the request body. The request headers must include 'accept' and 'content-type' set to 'application/json'. On success, it returns a response with 'success' set to true and 'data' as null. If there is an error, 'success' is false and an 'error' object with a descriptive message is returned.
This API endpoint updates a CRM custom object record. It requires a POST request to the specified URL with headers 'accept' and 'content-type' set to 'application/json'. The request body must include 'schemaId', 'recordId', 'name', 'description', 'fields', and 'metadata'. The response will indicate success or failure, with an optional error message if the operation fails.
Our AI Agent builds it instantly.
Try NowSee how teams put Freshworks to work as part of a bigger workflow.
Deduplicate and cleanse leads, auto-assign leads based on enrichment fields.
Power AI-driven outreach with real-time CRM data and calendar integrations.
Knit gives you 100+ prebuilt CRM, ERP, and Ticketing connectors — so you can sell faster and onboard…
See how leading technology firms are scaling their operations
Amazing Product With Exceptional Support from the team. By using Knit we managed to speed up our development by orders of magnitude.
A brilliant tool to let you seamlessly integrate with many different systems. It is very easy to integrate with and customer support is next level.
Seamless integration experience. Well-documented, self-explanatory APIs, and excellent service and support.
Easy to integrate. Knit's dashboard is intuitive for setting up and testing integrations, and the sandbox is extremely useful during development.
Knit shipped a brand-new Timesheet API in a week and handed us a ready-to-use NetSuite sandbox. That velocity is priceless when you're running payroll in 40+ countries.
4.9 out of 5 stars on G2
Yes — the Freshworks MCP Server is live and already built, not a roadmap item. It exposes Freshworks's real actions as AI-ready tools your agent can call directly.
Yes. Its actions cover both reads and writes, so your agent can pull data from Freshworks and push updates back to it, not just query it.
Knit manages Freshworks's OAuth, credential storage, and refresh for you — there's no auth to configure yourself before your agent can start calling tools.
Knit absorbs it. We maintain and update the Freshworks connector on our end, so the MCP Server keeps working without you tracking Freshworks's changelog.
No. Knit acts as a stateless passthrough — data is processed on our application server and returned directly to your agent, without being stored on Knit's servers.
You choose the model that fits your business — pricing based on integrated accounts, or based on API call volume. Every plan includes a 30-day free trial before billing starts.
Yes — this MCP server exposes Freshworks's actions as tools your AI agent can call directly, the same underlying capability previously offered as a standalone LLM Tool integration. MCP is the protocol; the tool-calling access is the same.
Yes — any MCP-compatible client or agent framework can connect to this server and call its exposed actions, regardless of which underlying LLM is driving the agent.
Learn how to fetch open support tickets using the Freshworks API. Step-by-step guide covering authentication, endpoints, common pitfalls, FAQs, and best practices for production-ready integrations.
This directory is a live list of all CRM API integration guides we have written at Knit. Use it to quickly find the guide related to the specific CRM APP you want to learn more about.
Zendesk CRM API integration guide covering key features, endpoints, use cases, FAQs, and best practices to automate customer data, sales pipelines, and support workflows at scale.
