Skip to content

Guide4 min read

Freshdesk tickets for new Shopify orders

How to create a Freshdesk ticket for a new Shopify order

On this page

Some shops want a support ticket waiting for each order. A made-to-order business might check each one by hand, a shop with tricky delivery might track each parcel as a ticket, and a support team might prefer to have the order on file before the customer writes in. This guide covers how to open that ticket automatically. Thrum does it with a starter on the client's own Shopify store and Freshdesk helpdesk. Freshdesk's own Shopify app and Zapier are described first, from their own pages.

Freshdesk's Shopify app

Freshdesk's help centre describes a Shopify app that brings a customer's order information into the helpdesk. Once installed, a Shopify panel appears on the ticket details page, and on each contact's page, showing the customer's current and past orders with payment and shipping details. Agents can use Shopify placeholders in canned responses, and with the right settings they can issue refunds and cancel orders from the panel. Connecting a store means creating a custom app in Shopify, and Freshdesk's article notes that from 1 January 2026 new custom apps are created and managed in the Shopify Dev Dashboard.

That app puts order details beside tickets that already exist. It is the right tool when tickets start from customers' emails. When the goal is a new ticket for each order, it needs something else to create the ticket.

Zapier

Zapier's Freshdesk and Shopify page lists a Freshdesk action that creates a ticket "for your domain", and Shopify events that fire when an order is created or when an order is paid, among many others. Its Freshdesk side also has events for new tickets and notes, and an action to update a ticket.

The Thrum starter

The starter is "Open a ticket in Freshdesk when a new order comes in in Shopify". It has nothing to fill in apart from the two connections.

  1. Install into the client. Templates → Library, open the starter, choose the client and install. It is switched off until the two accounts are connected.
  1. Connect Shopify. This works for a store that already has a custom app made by its admin. In the Shopify admin, go to Apps → Develop apps, open that app and check its Admin API scopes (the permissions it holds) include read_orders and write_customers. Copy the token from the app's settings. Shopify shows it once when it is created, so if it is gone, generate a new one.

  2. Connect Freshdesk. Thrum asks for two values. The helpdesk subdomain is the first part of the client's Freshdesk address, so northside for northside.freshdesk.com. The key is under the agent's profile picture, then Profile settings, then View API key (the agent's personal access key).

  1. Look at the ticket it opens. Every order becomes a new ticket, open and at low priority. Its subject starts "A new order comes in:" and ends with the shop's order number, such as #1001, and the order's email address is set as the requester. The body repeats the order number and email and adds the total, its currency and whether it is paid. Two edits are worth making once it is installed. Put the customer's first and last name, which the order step provides, into the requester name. If delivery questions come through these tickets, add the fulfilment status to the body as well.
  1. Switch it on. Thrum checks the store every 5 minutes and opens one ticket for each order placed since the previous check, oldest first. Orders placed before the workflow went live are skipped.

Tickets for paid orders

If the team should only see orders whose payment went through, install "Open a ticket in Freshdesk when an order is paid in Shopify" in its place. It checks every 5 minutes, opens one ticket per order however often the order changes afterwards, and its subject begins "An order is paid:".

No duplicate tickets

Thrum takes care that one order opens one ticket. Each order has an identity, so overlapping checks start nothing new. A busy or failing Freshdesk is retried at waits that begin at 5 seconds and double, up to 3 attempts. If the connection breaks after Freshdesk received the request, Thrum does not send it again on its own, since the ticket may already exist, and the run tells you to check before retrying.

Closing the loop

Freshdesk has a second step in Thrum, "Update a ticket", which moves a ticket to a status such as Pending or Resolved, and can change its priority or agent, found by the ticket's id. Freshdesk can also start workflows, when a ticket is opened and when one is resolved or closed, with Thrum looking for both every 5 minutes. A workflow started that way can reach back into Shopify with "Create a customer" or "Update a customer". The Freshdesk and Shopify page lists all the combinations.

Checked on 14 November 2026.

Sources

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.