For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DeveloperAcademyCommunityStatus
  • Service Management
    • Overview
    • Concierge & Ticketing Capabilities Overview
    • Forms
    • Forms - Integration Specific Guides
    • Live Agent Chat / Handoff
    • Triage
    • Approval Mirroring
    • Ticket Interception
    • Generic Ticketing Integration: Ticket Gateway
  • Administration
    • MyMoveworks
    • Organization Information
    • Roles and Permissions
    • MyMoveworks SSO
  • Moveworks Setup
    • Accessing Moveworks Setup
    • First-Time Login via Magic Link
    • Moveworks Setup Modules
    • Moveworks Setup: Module How To Guides
    • Plugin Management
    • Monitor Alerts
    • Audit Logs
    • DSL Fields Defaults
    • Data Crawling View
    • API Playground
    • Setup Homepage
    • Troubleshooting Hub
    • Security and Privacy Settings
    • Configuration Delete
    • Advanced Config Editor
    • Identity configuration
    • Onboarding Stage
  • Security
    • Security
    • Hyperlink & Button Expiry
    • Attachment Handling
    • Moveworks Subprocessors
  • Provision Management
    • Overview
    • Access Software
    • Access Groups
    • Access Account
  • Access Requirements
    • Overview
    • Update Set Modules
    • Ticketing Systems & ITSMs Access
      • ServiceNow Access Requirements
      • ServiceNow for HR Access Requirements
      • Jira Service Desk Permission (On-Prem) Access Requirements
      • Moveworks Jira Application (for Jira Cloud)
      • Jira Service Management (Cloud) - Access Requirements
      • Zendesk Access Requirements
      • Freshservice Access Requirements
      • Freshdesk Access Requirements
      • Salesforce Access Requirements
      • BMC Remedy/Helix Access Requirements
      • BMC Remedyforce Access Requirements
      • Cherwell Access Requirements
      • Ivanti Service Manager Access Requirements
      • ManageEngine (Cloud) Access Requirements
      • ManageEngine (On-Prem) Access Requirements
      • SolarWinds Samange Access Requirements
      • Sysaid Access Requirements
    • Identity and Access Management Systems Access
    • Multi-Factor Authentication (MFA) Systems Access
    • Knowledge Access Requirements
    • Email Distribution List Systems Access
    • Facilities Management Access
    • Live Agent Chat Access
    • HR Information System Access
    • Expense Management Access
    • Calendar Management Access
  • Core Platform
    • User Identity
    • Moveworks On-Prem Agent
    • Approvals Engine
    • Entity Catalog
    • Configuration Languages
    • Moveworks Data Objects
    • SIEM
  • Employee Experience Insights
    • Overview
    • Breaking Down the Dashboard
    • Understanding Industry Benchmarks
    • Apps & Services
    • Impact Module
    • EXI Common Use Cases
    • Configure EXI
    • Ticket Backpolling
  • Knowledge Studio
    • Overview
    • Knowledge Studio Configuration
    • AI Powered Recommendations
    • Inspecting & Verifying Sources
    • Publishing Articles
    • Creating Knowledge Articles
    • Resolving IT Tickets Guidance
DeveloperAcademyCommunityStatus
On this page
  • Why do we need access to your Freshdesk Instance?
  • Access Needs
  • Permissions Overview
  • Setup Overview
  • Configure the Connector
Access RequirementsTicketing Systems & ITSMs Access

Freshdesk Access Requirements

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Salesforce Access Requirements

Next
Built with

Why do we need access to your Freshdesk Instance?

The service account created in your Freshdesk instance will perform create, update operations on behalf of end users as well as notify end users on ticket related updates.

The Moveworks Service interacts with your Freshdesk platform so that the bot can:

  • Monitor tickets for autonomous resolution
  • Identify end users/employees
  • Create tickets for issues that require an agent’s attention
  • Reach out to an employee when a Freshdesk ticket needs the employee’s attention (via ticket comments)

Access Needs

Moveworks needs the API key to authenticate with the Freshdesk instance which is tied to the service account

The API key does not have an expiry date and is immutable.

Permissions Overview

Ensure the service account has the following permissions so we are able to perform necessary operations with the bot

Tickets

  • Create and update tickets
  • Read tickets
  • Add notes
  • Scope : Global Access

User Administration

  • Read Requesters (Users)
    • Assume Requesters Identity
  • Read Assignee Groups

Setup Overview

After setup is complete, provide the following information to your Moveworks CS team:

  • API key
  • Freshdesk Domain (i.e. https://customer.freshdesk.com)

Configure the Connector

  • Go to the Connectors module in Moveworks Setup, by clicking on Manage Connectors under Core Platform, and then click on System Connectors. click on Create. We need to create the FreshDesk Connector.

  • Search for the FreshDesk System here

  • Add the Hostname and the API key which was generated here

  • Save the config to successfully create your connector.