Power Automate and Zendesk
If your company already runs on Microsoft 365, Power Automate is the automation platform you're not paying extra for. That's most of the argument for it.
The connector, and its shape
Power Automate has a Zendesk connector. Treat what follows as the pattern rather than a fixed feature list, because Microsoft revises connectors on their own schedule and the current documentation is the only reliable source.
Two things to check before you commit a project to it.
First, licensing. Many third-party connectors in the Power Platform sit behind a premium licence, so a flow that works fine for you as an admin may refuse to run for a colleague on a bundled Microsoft 365 plan. Confirm the tier on the connector reference page rather than discovering it at rollout.
Second, triggers. Connectors vary in whether they offer real event triggers or only actions you call. If the Zendesk connector gives you actions but no trigger you can trust, you aren't stuck, you just start the flow from the Zendesk end instead. More on that below.
Authentication
You connect with your Zendesk subdomain plus credentials. Same rule as everywhere else: create a dedicated integration user in Zendesk, give it a role with the permissions the flow needs and nothing more, and connect as that account.
The reason is boring and important. A connection authenticated as a real person breaks the day that person leaves, and every flow they ever built breaks with it, usually in the middle of a quarter. It also makes the audit log unreadable, since every automated change looks like it came from a human.
In Power Platform, the connection is an object owned by whoever created it. Share it deliberately, or put the flow in a solution and use a service principal where your tenant allows it.
Power Automate Zendesk flows worth building
refund kicks off a Teams approval, and the approver decision writes back as an internal note. This is the flow Power Automate is genuinely best at, because Microsoft approvals are excellent and nothing in Zendesk matches them.The pattern that always works
When the connector does not do what you need, or the trigger you want is not there, use this instead. It is more reliable than fighting the connector.
Create a flow with the "When an HTTP request is received" trigger. Power Automate generates a URL. Then in Zendesk, build a webhook pointing at that URL and a trigger that fires it on the condition you care about, so Zendesk pushes the event the moment it happens. Details are in the webhooks guide.
For the return leg, use the HTTP action to call the Zendesk REST API directly. You get every endpoint, not just the ones the connector exposes, and the payload is yours to shape. See the ticket API guide for the resource you will use most.
The trade-off is that HTTP actions are usually premium too, and you are now handling auth headers yourself. Store the credential in Azure Key Vault or an environment variable, never in the flow definition, because flow definitions get exported and shared.
Limits to design around
Power Automate throttles. There are limits on requests per connection over a rolling window, on flow runs, and on how long a single run may take, and they differ by licence. Look them up for your plan rather than assuming, and assume they are lower than you would like.
Zendesk throttles too, per account, and a flow that loops over a few thousand tickets will hit that ceiling. Honour the Retry-After header on a 429, add a delay inside loops, and set loop concurrency down rather than up.
Also: a flow that fails doesn't tell anyone by default. Turn on failure notifications, or better, add a scheduled flow that checks run history and posts failures to a channel. Silent automation is worse than no automation, because people build process on top of it and don't find out until the process breaks.
Compared with a Zap, a flow is slower to build and stronger once built. If you only need one small connection and no approvals, Zapier will get you there faster.
Frequently asked questions
Is this the same as Microsoft Flow?
Yes, renamed. Microsoft Flow Zendesk connectors are now Power Automate, and any Zendesk Microsoft integration built there uses the same connector. For anything the connector doesn't expose, the Power Automate Zendesk API route is a custom HTTP action.
Is there an official Zendesk connector for Power Automate?
Yes, Power Automate ships a Zendesk connector. Check the current connector reference for its exact actions, triggers and licensing tier, since Microsoft revises these regularly.
Do I need a premium licence?
Very likely. Most third-party connectors and the HTTP action are premium in the Power Platform, so confirm the tier before rolling a flow out to colleagues.
How do I trigger a flow from a Zendesk event?
Use the "When an HTTP request is received" trigger, then create a Zendesk webhook and a Zendesk trigger that calls that URL. It's instant and does not depend on connector triggers.
Can Power Automate do approvals on Zendesk tickets?
Yes, and it is the best reason to use it. Fire an approval in Teams from a tag, then write the outcome back to the ticket as an internal note or a field update.
What limits should I expect?
Power Automate throttles by licence and Zendesk rate limits per account. Add delays inside loops, keep concurrency low, and honour the Retry-After header on 429 responses.
Automations do not check for duplicates
A flow that opens a ticket has no idea one already exists for the same problem. Ticket Merger does that part.
Start free trial14-day free trial. No credit card required.