Freshdesk and Gmail: what syncs, what doesn't, and how to set it up
Freshdesk turns mail in a connected Gmail mailbox into tickets and sends agent replies through Gmail. It moves email only: the Primary folder converts, and the docs list no contact or label sync.
- Connector
- Native email channel built by Freshdesk (Freshworks), set up in Admin settings; an optional Freshdesk Gmail Gadget is listed on the Google Workspace Marketplace
- Sync direction
- Two-way for email: Gmail → Freshdesk creates tickets, Freshdesk → Gmail sends replies
- Setup time
- A few steps for an admin; the docs give no time estimate
- Availability
- Freshdesk Growth, Pro and Enterprise (docs conflict on the Free program); the docs state no Google plan requirement
- Our rating
- 4 out of 5. Two-way ticket email through a connected Gmail mailbox on paid plans; only the Primary folder converts and nothing beyond email is documented.
| What | Direction | Detail |
|---|---|---|
| Incoming support email | Gmail → Freshdesk | Each email to the connected address becomes a ticket. Only mail in the Primary folder of the support mailbox converts. |
| Agent replies and outbound email | Freshdesk → Gmail | With a Gmail address such as help@gmail.com, the outgoing server defaults to Gmail. You can set incoming only, outgoing only, or both. |
| Customer replies on a ticket | Gmail → Freshdesk | Freshdesk checks the ticket ID, message ID or another identifier to thread a reply onto an existing ticket. Advanced settings add a ticket ID prefix. |
| Routing by mailbox | Derived | Each connected address can assign tickets to a group and link to a product, so mail to billing@ and support@ lands in different queues. |
| Read state and deletion of fetched mail | Freshdesk → Gmail | Two optional settings: mark fetched emails as read, or delete them from the server after fetching. Freshdesk recommends against deleting. |
| Forwarded mail from agent inboxes | Gmail → Freshdesk | Agents forward messages by hand to the support address. One setting makes the original sender the requester when a verified agent forwards. |
| Ticket and requester view inside Gmail | Two-way | The Freshdesk Gmail Gadget shows requester details and recent tickets next to an email and lets agents send replies from Gmail. |
Setting it up
- Log in to Freshdesk as an administrator. Go to Admin > Channels > Support Email > New Support Email.
- Choose the setup: incoming only, outgoing only, or incoming and outgoing.
- Select Gmail, sign in, and authorize Freshdesk to read, compose, send and delete mail. Without that permission, SMTP authentication fails.
- If you are signed in to a personal Gmail account through SSO, complete the sign-in in an incognito or guest window, or Freshdesk authenticates the personal account.
- Open the mailbox from the email list and edit it. Under General Settings, set the group, the product link and the read/delete options.
- Send a test email from a different address. Freshdesk creates no ticket when sender and recipient are the same.
- Optional: an administrator of both Freshdesk and the Google account installs the Freshdesk Gmail Gadget from the Marketplace.
Where the integration stops
- Only the Primary folder converts. Mail outside the Primary folder does not become a ticket, so check where Gmail files customer mail before go-live.
- Email is the whole connector. The pages I read describe no sync of Gmail contacts, labels or calendar. You need another route for those.
- Priority sync does not cover Gmail. The Sync priorities setting supports Outlook and Apple Mail, so a Gmail message's importance flag does not set ticket priority.
- Expired credentials stop the connection. Freshdesk shows a reauthorization banner to all users if one mailbox is unauthorized. An admin must sign in again.
- Some mail never becomes a ticket. Freshdesk skips emails where sender and recipient match, emails from blocked contacts, and emails with more than 50 To and CC addresses.
- The gadget's status is unclear. Its Marketplace listing carries old pricing and product names, and the Freshdesk help pages I read do not mention it. Test it before you plan around it.
Freshdesk connects to a Gmail mailbox and turns incoming mail into tickets. Agent replies go out through the same account. It suits support teams that already run help@ or support@ on Gmail and want to keep that address.
The connector moves email and nothing else. The Freshdesk pages I read describe no sync of Gmail contacts, labels or calendar. Only mail in the Primary folder converts, which surprises teams whose Gmail files some customer mail outside Primary. See Freshdesk for the helpdesk itself and Gmail for the mail side.
Email becomes tickets, and replies go back through Gmail
An administrator adds Gmail under Admin > Channels > Support Email and picks one of three modes. Incoming only fetches mail. Outgoing only sends through Gmail while the Freshworks mail server receives. The third mode does both.
With a public address such as help@gmail.com, the outgoing server defaults to Gmail. With a company-domain address in incoming-only mode, Freshdesk assigns its own mail server for outgoing mail. Pick the mode that matches the address the customer should see.
On setup, Freshdesk's article says the last day of Inbox mail, read and unread, becomes tickets. Expect up to a day of existing mail to become tickets.
Plan access: the docs disagree about the Free program
The setup article marks Growth, Pro and Enterprise as supported and marks Free with a cross. A note in the same article says Free accounts can add one email through custom servers. A second article says you can add multiple support emails from the Growth plan, and Free allows one.
The docs do not settle whether Free can connect Gmail. Confirm in a trial account before you plan around it. See Freshdesk pricing for current plan names. On Freshdesk's earlier plans, the same article lists Garden, Estate and Forest as supported, and Sprout and Blossom as not.
Connections expire, and one bad mailbox warns everyone
If a Gmail password expires or changes, Freshdesk shows a reauthorization banner. An admin re-enters the credentials or signs in again from the edit icon. The docs say emails sent during the disconnection are resent after reauthorization.
On accounts with several support addresses, one unauthorized mailbox shows the banner to every user. Freshdesk's fix for a stuck primary address is to set it to non-primary, reauthorize it, then set it back.
What the docs leave open
The pages say nothing about Gmail labels, contact sync or calendar events. They also do not say whether the Gmail Gadget works with current Freshdesk plans. Where a Freshdesk rule matters, such as threading or blocked senders, test it with a real Gmail address.