Skip to content
Freshservice logoFreshdesk logo

Connect Freshservice to Freshdesk

Move data between Freshservice and Freshdesk the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Freshservice triggers
8
Freshservice actions
12
Freshdesk triggers
0
Freshdesk actions
6

Automation ideas

What you can build with Freshservice and Freshdesk

A few flows teams run between Freshservice and Freshdesk. Use one as a starting point, or build your own from scratch.

  • New Ticket in Freshservice creates Get Tickets in Freshdesk

    Triggers when a new ticket is created in Freshservice.

  • New Ticket in Freshservice creates Get Contact from ID in Freshdesk

    Triggers when a new ticket is created in Freshservice.

  • New Ticket in Freshservice creates Get Ticket Status in Freshdesk

    Triggers when a new ticket is created in Freshservice.

  • Updated Ticket in Freshservice creates Get Tickets in Freshdesk

    Triggers when an existing ticket is updated in Freshservice.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Freshservice and acts in Freshdesk, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.