Freshdesk + Freshservice
Connect Freshdesk and Freshservice to Unify Customer Support and IT Operations
Automate ticket routing, asset data sharing, and cross-team escalations between your customer-facing helpdesk and internal IT service management platform.
Why integrate Freshdesk and Freshservice?
Freshdesk and Freshservice are two platforms from the Freshworks ecosystem — one handles external customer support, the other manages internal IT services. They serve different audiences, but the data inside them is tightly linked: a customer-reported software bug becomes an IT incident, a hardware failure triggers a flood of support tickets, an outage update needs to reach agents and end users at the same time. Integrating Freshdesk with Freshservice on tray.ai removes the silos between your support and IT teams so information moves in both directions without manual handoffs or duplicated effort.
Automate & integrate Freshdesk & Freshservice
Use case
Bi-Directional Ticket Escalation Between Support and IT
When a Freshdesk customer ticket needs IT intervention — a system outage, network issue, or software defect — automatically create a linked incident in Freshservice and keep both records in sync. Status updates, comments, and resolution notes flow between the two platforms so neither team is working blind.
Use case
Proactive Customer Notifications During IT Incidents
When an IT incident is logged or updated in Freshservice, automatically identify all affected Freshdesk customers and send proactive status notifications. Customers stay informed without support agents having to manually scan for related tickets and write individual responses.
Use case
Asset and Configuration Data Enrichment for Support Tickets
When a new ticket arrives in Freshdesk, automatically query Freshservice's CMDB to pull the customer's associated assets, software licenses, and configuration items, then attach that context directly to the ticket. Agents have the full picture before they even respond.
Use case
Surge Detection and Automatic Incident Creation
Monitor Freshdesk ticket volume in real time and automatically trigger an IT incident in Freshservice when tickets sharing a common tag, category, or keyword cross a defined threshold. IT teams can investigate and respond before a minor issue becomes a major outage.
Use case
Change Management Communication to Support Teams
When an approved change request or planned maintenance is scheduled in Freshservice, automatically create a Freshdesk knowledge base article or internal note alerting support staff. Agents are always prepared to handle incoming questions about upcoming changes or downtime windows.
Use case
Unified SLA Monitoring Across Both Platforms
Aggregate SLA status data from both Freshdesk and Freshservice into a single workflow that monitors breach risks and triggers cross-team alerts. When a ticket in either system is approaching an SLA deadline, the relevant team gets notified and the ticket escalates automatically if no action is taken.
Use case
Employee Offboarding Coordination Between IT and HR Support
When an employee offboarding request arrives via Freshdesk (typically through HR), automatically trigger the appropriate Freshservice IT tasks — asset recovery, account deprovisioning, and license reclamation — so nothing falls through the cracks and audit trails are maintained in both systems.
Get started with Freshdesk & Freshservice integration today
Freshdesk & Freshservice Challenges
What challenges are there when working with Freshdesk & Freshservice and how will using Tray.ai help?
Challenge
Mapping Ticket Fields and Priority Levels Across Two Different Data Models
Freshdesk and Freshservice use overlapping but not identical field structures. Ticket types, priority labels, status values, and custom fields often have no direct equivalent between platforms, which leads to data loss or mismatched records when syncing manually.
How Tray.ai Can Help:
Tray.ai's visual data mapper lets you define explicit field transformations between Freshdesk and Freshservice schemas, translating priority levels, status values, and custom fields precisely. You can build conditional logic to handle edge cases — for example, mapping a Freshdesk 'Low' priority to a Freshservice 'Medium' when the ticket type is a billing issue — without writing custom code.
Challenge
Avoiding Infinite Sync Loops Between Bi-Directionally Connected Tickets
When Freshdesk and Freshservice are synced bi-directionally, a status update in one system can trigger an update in the other, which then triggers another update back — creating an infinite loop of API calls that inflates usage costs and corrupts ticket records.
How Tray.ai Can Help:
Tray.ai workflows support loop-prevention logic using conditional checks — for example, only triggering an update if the source of the last change wasn't the integration itself. Custom field flags or timestamp comparisons ensure each sync event is processed exactly once without cascading back.
Challenge
Handling Authentication and API Rate Limits for High-Volume Environments
Organizations with large support volumes can hit Freshdesk or Freshservice API rate limits when processing thousands of ticket events simultaneously, causing sync failures, lost updates, and incomplete data flows between the two platforms.
How Tray.ai Can Help:
Tray.ai's built-in rate limit handling and retry logic automatically queues and retries API calls when limits are reached, so no events are dropped. You can configure throttling parameters and use tray.ai's asynchronous processing to spread high-volume operations over time without overwhelming either platform's API.
Challenge
Keeping Historical Ticket References Intact During Long-Running Incidents
Major IT incidents can span hours or days, with dozens of Freshdesk tickets accumulating and needing to stay linked to an evolving Freshservice incident record. Keeping accurate cross-references as ticket counts grow and incident details change is genuinely hard to manage by hand.
How Tray.ai Can Help:
Tray.ai lets you store and update cross-reference IDs persistently within workflow state or custom fields on both platforms. As new Freshdesk tickets are identified as related to an ongoing Freshservice incident, the workflow automatically appends them to a tracked list and applies consistent internal notes and links, keeping the full ticket-to-incident relationship map accurate.
Challenge
Ensuring Data Privacy and Access Control Across Different Team Audiences
Freshdesk tickets often contain sensitive customer PII, while Freshservice incidents are visible to internal IT staff who may not be authorized to see that customer data. Syncing full ticket content between systems without controls can create real compliance and data governance risks.
How Tray.ai Can Help:
Tray.ai workflows can be configured to selectively map only non-sensitive fields when creating records in Freshservice — stripping PII, limiting customer details to a reference ID, or replacing personal data with anonymized tokens. Your integration respects data access boundaries and supports GDPR, CCPA, and internal data governance policies without custom middleware.
Start using our pre-built Freshdesk & Freshservice templates today
Start from scratch or use one of our pre-built Freshdesk & Freshservice templates to quickly solve your most common use cases.
Freshdesk & Freshservice Templates
Find pre-built Freshdesk & Freshservice solutions for common use cases
Template
Escalate Freshdesk Ticket to Freshservice Incident
Automatically creates a new Freshservice incident when a Freshdesk ticket is tagged for IT escalation or hits a critical priority, then links the two records and syncs status updates bi-directionally until both are resolved.
Steps:
- Trigger when a Freshdesk ticket is updated with a specific tag (e.g., 'IT-escalate') or priority level changes to 'Urgent'
- Create a corresponding incident in Freshservice with mapped fields including subject, description, requester, and priority
- Store the Freshservice incident ID on the Freshdesk ticket as a custom field for cross-reference
- Poll Freshservice for status updates and sync them back to the linked Freshdesk ticket as private notes
- Close the Freshdesk ticket automatically when the Freshservice incident is marked as resolved
Connectors Used: Freshdesk, FreshService
Template
Freshservice Incident Alert to Freshdesk Customers
When a major incident is raised or updated in Freshservice, identifies all Freshdesk tickets sharing a related keyword, tag, or affected service, and sends a templated status update reply to each affected customer automatically.
Steps:
- Trigger when a Freshservice incident is created or its status is updated
- Search Freshdesk for open tickets matching the incident's affected service tag or keyword
- Compose a personalized status message using the Freshservice incident details
- Post the message as a public reply on each matching Freshdesk ticket
- Add an internal note on each Freshdesk ticket linking to the Freshservice incident record
Connectors Used: FreshService, Freshdesk
Template
Enrich Freshdesk Tickets with Freshservice Asset Data
On new Freshdesk ticket creation, queries the Freshservice CMDB for assets associated with the requester's email or organization, then appends asset details to the ticket as a structured internal note for agent context.
Steps:
- Trigger when a new ticket is created in Freshdesk
- Extract the requester's email address from the ticket payload
- Query Freshservice CMDB API to retrieve associated assets and configuration items
- Format the asset data into a structured summary note
- Post the summary as a private internal note on the Freshdesk ticket before the agent first views it
Connectors Used: Freshdesk, FreshService
Template
Auto-Create Freshservice Incident from Freshdesk Ticket Surge
Monitors Freshdesk ticket creation in real time and automatically raises a Freshservice incident when a volume threshold is breached for tickets sharing a common tag, subject keyword, or product category within a rolling time window.
Steps:
- Trigger on each new Freshdesk ticket creation event
- Increment a rolling counter for tickets matching a defined tag or keyword within a configurable time window
- Check if the counter has crossed the defined surge threshold (e.g., 10 tickets in 30 minutes)
- If threshold is met, create a new P1 incident in Freshservice with aggregated ticket details and links
- Notify the on-call IT team via the Freshservice incident and add a bulk internal note to all related Freshdesk tickets
Connectors Used: Freshdesk, FreshService
Template
Sync Freshservice Change Requests to Freshdesk Knowledge Base
When a change request is approved in Freshservice, automatically drafts and publishes a corresponding Freshdesk knowledge base article or agent-facing note so support staff know about upcoming changes and can answer customer questions accurately.
Steps:
- Trigger when a change request in Freshservice is moved to 'Approved' status
- Extract change title, description, scheduled date, and impact details from the Freshservice record
- Generate a customer-friendly or agent-facing article draft using the change details
- Create or update the article in the appropriate Freshdesk knowledge base category
- Optionally post an internal announcement note on relevant Freshdesk tickets referencing the affected service
Connectors Used: FreshService, Freshdesk
Template
Employee Offboarding: Freshdesk Request to Freshservice IT Tasks
Converts an employee offboarding request received in Freshdesk into a structured Freshservice service request with all required IT sub-tasks — account deactivation, asset retrieval, and license reclamation — and syncs completion status back to the original Freshdesk ticket.
Steps:
- Trigger when a Freshdesk ticket is created or tagged with an offboarding category
- Extract employee details (name, email, department, manager) from the ticket description or custom fields
- Create a Freshservice service request with pre-defined offboarding task checklist items
- Monitor Freshservice for task completion events and update the Freshdesk ticket with progress
- Close the Freshdesk ticket and notify the HR requester once all Freshservice tasks are marked complete
Connectors Used: Freshdesk, FreshService