Skip to content
Kustomer logoFreshservice logo

Connect Kustomer to Freshservice

Move data between Kustomer and Freshservice 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.

Kustomer triggers
0
Kustomer actions
6
Freshservice triggers
8
Freshservice actions
12

Automation ideas

What you can build with Kustomer and Freshservice

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

  • New Ticket in Freshservice creates Create Customer in Kustomer

    Triggers when a new ticket is created in Freshservice.

  • New Ticket in Freshservice creates Create Conversation in Kustomer

    Triggers when a new ticket is created in Freshservice.

  • New Ticket in Freshservice creates Update Conversation in Kustomer

    Triggers when a new ticket is created in Freshservice.

  • Updated Ticket in Freshservice creates Create Customer in Kustomer

    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 Kustomer and acts in Freshservice, 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.