Turn every new review into a Zendesk ticket, then reply from Zendesk and have it post straight back to the review platform. Setup takes about five minutes: connect Zendesk with one click through its own sign-in, pick which reviews should open tickets, and you're done. From then on, reviews arrive as tickets and your agents work them like any other ticket.

What you'll need

A Reviewflowz account, signed in at app.reviewflowz.com.
A Zendesk account, and the ability to authorize an app for it (a Zendesk admin, or an agent allowed to grant app access).
That's it. There's no subdomain, email, or API token to find and paste. You authorize through Zendesk's own sign-in screen.

If your Zendesk installs are gated by an admin, this is exactly the article to forward. The FAQ below answers the questions they'll ask.

Step 1: Start the connection

In Reviewflowz, open Integrations in the sidebar, then the Help desk area. Help-desk connections also show up when you build a flow, so you can start from either place.

Click Create help desk integration. If you haven't connected one yet, you'll see an empty state:

Title: No help desk integrations yet
Description: "Open a ticket in Zendesk, Intercom, Front and more for every new review."

In the destination row, open the help-desk dropdown (it reads "Choose a help desk") and pick Zendesk. Then click Connect Zendesk.

The Reviewflowz help desk flow builder with Zendesk selected and the Connect Zendesk option

Reviewflowz supports Zoho Desk, Intercom, Front, LiveAgent, Freshdesk, Help Scout, and Gorgias as help desks too. This article covers Zendesk.

Step 2: Authorize with Zendesk

A connection window opens. Sign in to Zendesk and approve access. This is Zendesk's standard OAuth authorization, the same "sign in and allow" screen you get with any Zendesk app, so you're not typing credentials into Reviewflowz.

After you approve, Reviewflowz finishes linking (a brief connecting screen) and confirms with Successfully connected to Zendesk!. It then drops you into the flow that decides which reviews become tickets (the next step).

The connection window is provided by Truto, our integrations provider, which manages the Zendesk authorization. That's why the popup carries Truto branding. Reviewflowz never sees or stores your Zendesk password or token. There's more on this below.

If it doesn't connect, you'll see Failed to find connected account after 30 seconds. Please try again. or Connection Failed with the reason. Just retry (see Troubleshooting).

Step 3: Choose which reviews open tickets

The flow builder works like the alerts builder. Pick your options:

Which reviews feed it. Use the Review profiles panel (labeled Locations on location-based plans). Pick one, several, or all. This is also how you scope by platform: choose only the profiles you want. You can filter by review language per profile too.
Rating filter (the Send row): send All reviews, or set a star threshold (5, 4, 3, 2, or 1 stars) with and more, exactly, or or less. For example, "Send 2 stars or less reviews" to ticket only your unhappy customers.
Require content. Turn this on to only ticket reviews that actually contain text.
Translation (the Translate to row): keep Don't translate, or pick a language. When it's on, the ticket is created in the review's original language and the translation is added as a private note (more below).

Give the flow a title, make sure it's turned on, and save.

Zendesk flows run in real time, so a ticket opens as each qualifying review arrives. There's no reply toggle to set: replying from Zendesk works automatically (see below). To route different profiles to different flows, just build more than one.

What a review looks like as a Zendesk ticket

When a qualifying review arrives, Reviewflowz opens a ticket. Here's how to read it.

Subject: the reviewer's name and the review id, plus the rating, like Jane Doe [Review #12345] | New 5-star review (Anonymous when there's no name).
Description (the first comment): the review in its original language, then a details block. When available it includes the review title, the review text, and Pros and Cons, then a divider, then Rating (n/5), Platform, Profile, Date, and Reviewer. For Trustpilot it also shows the customer email and reference id when present. Two links close it out: Read in Reviewflowz and Read on [platform], which opens the review on its source site.
Priority, set automatically from the rating. Your unhappiest customers rise to the top on their own: 0 to 2 stars open as High, 3 stars as Normal, 4 to 5 stars as Low.
Status: opens as Open.
Requester: review tickets come in under a Reviewflowz contact ([email protected]), not the reviewer. So they're easy to spot, and they never email your customer by accident.
Tags: a set of reviewflowz tags is applied (more below).

What happens as the review changes

Everything after ticket creation threads onto the same original ticket, so there's one ticket per review and it stays up to date. A solved ticket is reopened so the new note gets seen. A ticket that's been permanently closed in Zendesk is left untouched.

Tags that carry over

Every review ticket is tagged, so you can build Zendesk views, triggers, and automations on top of them. Tags are always prefixed reviewflowz and cleaned to Zendesk-safe text (lowercase, underscores). You get:

reviewflowz on every review ticket
reviewflowz_[language], the review's language, like reviewflowz_en
reviewflowz_[platform], like reviewflowz_google_maps
reviewflowz_[sentiment]_review, where sentiment is positive (4 to 5 stars), negative (1 to 2), or neutral (3)
one reviewflowz_[yourtag] for each tag you've applied to the review in Reviewflowz

Lifecycle tags are added as events happen: reviewflowz_updated, reviewflowz_deleted, reviewflowz_reply_posted, and reviewflowz_reply_failed (the failed tag clears once a reply succeeds).

Translations as private notes

If translation is on, the ticket body stays in the original language and the translation is added as a private note headed Translated review: with the translated title, text, and Pros and Cons. Only your agents see it, and it never reaches a customer.

Review updated or edited

If the reviewer edits their review, Reviewflowz doesn't open a new ticket. It adds a private note headed Updated review (n/5): with the new text, tags the ticket reviewflowz_updated, and reopens it if it was solved.

Review removed or deleted at the source

If the review is taken down on the platform, Reviewflowz adds a private note reading This review has been deleted. (plus "It was last seen on YYYY-MM-DD." when known) and tags the ticket reviewflowz_deleted. The ticket isn't force-closed, so your team decides what to do with it.

Replies posted from Reviewflowz or elsewhere

If a reply is published from Reviewflowz or another connected channel, the ticket gets a private note headed Reply posted: with the reply text, tagged reviewflowz_reply_posted. If a reply fails to post, you get a private note instead: "The reply could not be posted to the review platform. Please try again, or contact [email protected] for support." with the tag reviewflowz_reply_failed.

Notice the pattern: translations, updates, removals, and reply outcomes all arrive as internal notes. The ticket thread stays clean, and nothing accidentally reaches a customer.

Replying to a review from inside Zendesk

This is the two-way part. To answer a review, your agent writes a public reply on the ticket, exactly like replying to any Zendesk ticket. Reviewflowz picks it up and posts it back to the review platform as your official response.

A few things to know:

Only public replies from an agent post back. Internal notes never post back, so your team can discuss privately without anything going public.
Reviewflowz strips Zendesk signatures, footers, and email boilerplate before posting, so only your actual reply text reaches the platform.
The reply is attributed to the agent who wrote it, visible in Reviewflowz history.

Not every platform accepts replies through the API, so here's where a Zendesk reply posts back and where you reply on the source site instead:

Reply from Zendesk (posts back)	Reply via the ticket's Read on link
Google Maps, App Store, Play Store, Trustpilot, Facebook	Every other platform

Each platform on the left needs its connection set up in Reviewflowz first (App Store and Play Store need the store integration). For anything on the right, open the Read on [platform] link in the ticket and reply on the site. If an agent does post a public reply for an unsupported platform, Reviewflowz adds the "could not be posted" internal note, so nothing is lost silently.

How the integration works

Here's the short version, for anyone who wants to know what's happening under the hood.

The connection uses standard Zendesk OAuth 2.0. You authorize through Zendesk's own consent screen, and the access grant is held by Truto, our integrations provider, on your behalf. Reviewflowz stores no Zendesk password, email, subdomain, or API token.

What Reviewflowz keeps is minimal and encrypted at rest: an opaque handle to the connected account (via Truto) and a per-connection webhook secret. Nothing that can sign in to your Zendesk directly.

Tickets are created and updated through a ticketing API, and the integration only works with the review tickets it opens: creating and updating them, adding their public and private comments, and tagging them. It isn't a broad Zendesk admin integration.

Inbound is one narrowly-scoped webhook. Reviewflowz subscribes to a single Zendesk event, new ticket comments (ticket.comment_added), under a webhook named "ReviewFlowz Ticket Updates". It doesn't touch any webhooks you created. Every inbound call is verified: each delivery carries a per-connection secret that Reviewflowz checks with a constant-time comparison before acting, and anything without the right secret is rejected.

Every call Reviewflowz makes on your behalf (create a ticket, add a note, add or remove a tag, manage the webhook) is written to an append-only audit record tied to your account, with the purpose and the outcome. Tickets are matched to reviews within your account only, so an event can never cross into another customer's data. And when you remove the connection, Reviewflowz tears down its webhook and stops creating tickets.

Questions IT and Zendesk admins ask

How does it connect, and do we hand over credentials?

Through standard Zendesk OAuth, handled by Truto (our integrations provider). You authorize on Zendesk's own screen. Reviewflowz stores no Zendesk password, email, subdomain, or API token.

Who can set it up?

Anyone able to authorize an app for your Zendesk: an admin, or an agent allowed to grant app access.

What can it do in our Zendesk?

It works with the review tickets it opens: creating and updating them, adding public and private comments, and tagging them. It also registers one webhook for new ticket comments so agent replies can post back to the review platform. It isn't a broad Zendesk admin integration.

What does it store on your side?

Only an encrypted handle to the connected account and an encrypted per-connection webhook secret. The Zendesk access grant itself is held by Truto, not stored by Reviewflowz.

How are the incoming calls from Zendesk verified?

Each delivery carries a per-connection secret that Reviewflowz checks with a constant-time comparison. Unverified calls are rejected.

Can we see what it did?

Yes. Every action is written to an append-only audit record with its purpose and outcome.

Can we remove it?

Yes, anytime. Disconnect it in Reviewflowz and the webhook is removed and ticket creation stops.

Will it email our customers?

No. Tickets come in under a Reviewflowz contact, and translations, updates, removals, and reply outcomes are internal notes. Only a public reply your agent writes goes back to the review platform, never to the reviewer by email.

Where is our data handled, and are you GDPR-compliant?

Reviewflowz is a France-based (EU) company operating under GDPR. It publishes a privacy policy and terms of service, and can delete personal data on request.

Managing and disconnecting

Change what gets ticketed: edit the flow anytime (profiles or locations, rating filter, require-content, translation).
Multiple connections: you can connect more than one help desk and run several flows.
Disconnect: remove the Zendesk connection in Reviewflowz. The single webhook is torn down automatically and no new tickets are created. Existing tickets stay in your Zendesk.

Troubleshooting

The connection didn't complete ("Failed to find connected account after 30 seconds"). The authorization didn't come back in time. Click Connect Zendesk again and complete the Zendesk sign-in.
"Connection Failed." Zendesk declined or the authorization was cancelled. Retry, and make sure the account you authorize with can grant app access.
No tickets are being created. Check that the flow is turned on, has at least one review profile selected, and that your Send filter isn't excluding the reviews you expect (a "2 stars or less" filter skips 5-star reviews).
I replied in Zendesk but it didn't appear on the review site. Make sure it was a public reply, not an internal note, and that the platform supports replying from Zendesk (Google Maps, App Store, Play Store, Trustpilot, Facebook, with that connection set up). For other platforms, use the Read on [platform] link in the ticket to reply on the site. If a reply failed, the ticket will have a "could not be posted" note.
My reply's signature or footer showed up oddly. Reviewflowz strips signatures and email boilerplate before posting, so keep your actual response above your signature.
Still stuck? Contact support from the chat in your Reviewflowz dashboard, or email [email protected].