Connect Shopify to Freshdesk

Freshdesk can put Shopify order details beside a support ticket so an agent can answer without repeatedly switching tabs. Its Marketplace listing describes recent orders, payment and shipping information, and optional cancellation and refund actions. The important setup detail is that Freshworks updated its instructions for new connections in 2026: a merchant creates a custom app in Shopify's Dev Dashboard, then authenticates that app in Freshdesk.

This guide is a preparation and verification companion to the current Freshworks installation instructions, not a replacement for the vendor's live screens. Installation controls and permission wording can change. Use a store owner and Freshdesk administrator who understand the access being granted.

1. Decide what Freshdesk should be allowed to do

Start with the contact types that need Shopify context. For WISMO, an agent may need order and shipping data only. For returns, they may also need to start a cancellation or refund. Separate these needs before installing because the Freshworks guide lists read_customers, read_orders and write_orders scopes for its current custom-app setup. A broad order-write scope deserves an internal permission policy even when only a subset of agents should act.

Document the store, Freshdesk account, administrator, integration owner and support escalation contact. Confirm whether you have one storefront or several, and whether separate stores share customer email addresses or order number formats. Check your privacy process for staff access to customer and order data. Never send the app secret through an ordinary support ticket or save it in a shared macro.

2. Create the Shopify-side app

Freshworks says that from January 2026, new custom apps must be created in the Shopify Dev Dashboard; existing store connections are unaffected. Its current guide asks for store-owner access or granted app-development permission. In Shopify, enter app development, create a new app, create a version, set the required access scopes and install it on the intended store. The guide specifies customer read and order read/write scopes, then instructs the administrator to retrieve the client ID and secret.

Before you approve the installation, verify the app name, exact store and scopes. This is a security decision, not an SEO or support-copy step. Keep credentials in the approved secret-management location and restrict who can view or rotate them. If the Shopify dashboard differs from the article, stop and use current vendor support rather than guessing which scope is equivalent.

3. Authenticate in Freshdesk

Freshworks directs a Freshdesk administrator to its app marketplace, locate Shopify, install the app, enter the store URL and custom-app credentials, authenticate, then save changes. The store should appear under connected stores. If it does not, check the store URL, app installation state, credentials and requested scopes. Do not keep re-entering a secret in unrelated fields or create several duplicate apps as a workaround.

For an additional store, Freshworks documents installing the custom app on that store and then adding it in the Freshdesk app settings. Verify the second store independently. A successful connection message is only the first test; it does not prove the right order will appear for every ticket.

4. Test the ticket widget with representative orders

Open a test ticket from a customer with a single order and inspect the Shopify widget. Freshworks says it can show order number, purchase date, paid or unfulfilled status, purchased products, shipping details and past orders. Confirm the “View in Shopify” route opens the same order. Repeat with a guest order, two orders under one email address, an order from another connected store and a different contact email.

Do not assume an email match is identity verification. If the widget finds several orders, the agent should choose the correct one and apply the store's approved checks before discussing private details. For tracking, compare the displayed carrier and status against Shopify and the carrier's own page. If a shipment was not fulfilled, Freshworks notes that shipping details may be absent rather than broken.

5. Enable financial actions only after a controlled test

The Marketplace app offers a setting to allow cancellations and refunds from Freshdesk. Leave it off until the owner has specified which roles may use it and how approval is recorded. Use non-production or tightly controlled test orders to check full and partial refunds, quantities, shipping, taxes, restocking and customer notifications. Freshworks documents conditions under which cancellation is unavailable once an order has shipped. Agents should see an unavailable option as a rule, not try to force a store-side workaround.

Confirm in Shopify that a successful action occurred once, and that the ticket records the outcome. If the app reports an error, inspect the Shopify order before retrying; otherwise two agents could create a duplicate action. Our returns workflow provides the wider ownership and handoff pattern.

6. Maintain and recheck the connection

Assign an integration owner. Recheck it after Shopify permission changes, staff-role changes, a Freshdesk app update, a new storefront or a carrier/fulfilment change. Audit a sample of live tickets monthly for wrong-order matches, stale data and unexpected action visibility. When access is no longer needed, remove it through the supported vendor process and confirm the old credentials are no longer usable.

Freshdesk is worth choosing when its general ticketing and reporting fit the team as well as its Shopify widget. If ecommerce-specific order workflows dominate, compare it with Gorgias and Zendesk using the same test orders rather than relying on integration labels.

Sources

• Freshworks current Shopify integration setup
• Freshworks Marketplace Shopify app listing

Setup details and capabilities come from Freshworks documentation. Security checks and product-fit advice are Support Sorted's editorial judgement.