Connect Freshdesk and Shopify
Start a client’s workflow in Freshdesk and act in Shopify, or the other way round, on the client’s own accounts.
Step by step, with the other ways to do it: How to create a Freshdesk ticket for a new Shopify order
Each app by itself: Freshdesk integration and Shopify integration, with how to connect it, its scopes and its limits.
What Freshdesk and Shopify do together
Shops that answer customers in Freshdesk can open a ticket for each order, so the support team has a record to work from before the customer writes in about delivery, a change or a refund.
Both starters begin in Shopify, with “A new order comes in” or “An order is paid”, and end with Freshdesk’s “Open a ticket”, which makes an open ticket at low priority. Freshdesk’s own triggers, a ticket that is opened and a ticket that is resolved or closed (each checked every 5 minutes), can drive Shopify’s “Create a customer” or “Update a customer” steps in a workflow you build.
What the pair is used for
- Freshdesk’s “Update a ticket” can move an order’s ticket to Pending or Resolved and change its priority or agent, found by the ticket’s id.
- A Freshdesk ticket reaching Resolved or Closed fires once per ticket and status, so a workflow that writes the outcome into the Shopify customer’s note with “Update a customer” runs once per resolution.
Every way Freshdesk and Shopify join
A workflow starts from a trigger in one app and runs a step in the other, on the client’s accounts. Where the library has a starter for it, it installs that pairing into a client switched off; any other pairing is two steps on the canvas.
From Freshdesk to Shopify
| When this happens in Freshdesk | This runs in Shopify | How fast | Starter |
|---|---|---|---|
| A ticket is opened | Create a customer | Within 5 minutes | Two steps on the canvas |
| A ticket is opened | Update a customer | Within 5 minutes | Two steps on the canvas |
| A ticket is resolved (or closed) | Create a customer | Within 5 minutes | Two steps on the canvas |
| A ticket is resolved (or closed) | Update a customer | Within 5 minutes | Two steps on the canvas |
From Shopify to Freshdesk
| When this happens in Shopify | This runs in Freshdesk | How fast | Starter |
|---|---|---|---|
| A new order comes in | Open a ticket | Within 5 minutes | Install the starter |
| A new order comes in | Update a ticket | Within 5 minutes | Two steps on the canvas |
| An order is paid | Open a ticket | Within 5 minutes | Install the starter |
| An order is paid | Update a ticket | Within 5 minutes | Two steps on the canvas |
Set up the starter
Open a ticket in Freshdesk when a new order comes in to Shopify
The common combination is Shopify’s “A new order comes in” to Freshdesk’s “Open a ticket”. It has no fields to fill in. You connect the client’s Shopify store and their Freshdesk, which asks for the helpdesk subdomain and an agent’s API key, and the store is checked every 5 minutes.
The ticket’s subject reads “A new order comes in:” followed by the order number, the requester is the order’s email address, and the description lists the order number, the email, the total, the currency and the payment status. After installing, set the requester name to the customer’s first and last name, and add the fulfilment status to the description if the team handles delivery questions in these tickets.
- 1Install the starter into the client from Templates → Library. It lands switched off.
- 2Connect the client’s Shopify, for “A new order comes in”
- 3Connect the client’s Freshdesk, for “Open a ticket”
- 4Switch it on. Within 5 minutes: Shopify is checked every 5 minutes.
What it produces
The Freshdesk step as it runs for an example client, Lakeview Consulting, when Emma Collins asks for a consultation: each value the starter fills in.
- Name
- #1042
- Description
- A new order comes in in Shopify. Order number (#1001): #1042 Their email: emma.collins@example.com Total: 500.00 Currency: USD Payment status (PAID…): new
- emma.collins@example.com
- Subject
- A new order comes in: #1042
Setup notes for this pair
- Shopify’s “Create a customer” refuses an email it already has and the run fails naming it, so use “Update a customer” for returning buyers.
- “Update a customer” leaves tags alone, because Shopify would replace them all.
Field mapping, starter by starter
Each value a starter’s step is given, and where it comes from. Words in brackets are filled in when it runs; change any of it after installing.
Open a ticket for new orders
Open a ticket in Freshdesk when a new order comes in to Shopify
| Freshdesk value | Filled from |
|---|---|
| Name | [the order number, from Shopify] |
| Description | A new order comes in in Shopify. Order number (#1001): [the order number, from Shopify] Their email: [the order’s email, from Shopify] Total: [the order’s amount, from Shopify] Currency: [the order’s currency code, from Shopify] Payment status (PAID…): [the order’s display financial status, from Shopify] |
| [the order’s email, from Shopify] | |
| Subject | A new order comes in: [the order number, from Shopify] |
Open a ticket for paid orders
Open a ticket in Freshdesk when an order is paid in Shopify
| Freshdesk value | Filled from |
|---|---|
| Name | [the order number, from Shopify] |
| Description | An order is paid in Shopify. Order number (#1001): [the order number, from Shopify] Their email: [the order’s email, from Shopify] Total: [the order’s amount, from Shopify] Currency: [the order’s currency code, from Shopify] Payment status (PAID…): [the order’s display financial status, from Shopify] |
| [the order’s email, from Shopify] | |
| Subject | An order is paid: [the order number, from Shopify] |
Freshdesk and Shopify and their logos are trademarks of their owners, used here only to say what Thrum works with; no endorsement is implied.
Thrum is cooking.
Get early access and you’ll be among the first in. Early members get a launch perk.