Zendesk action flows got cheaper:
Marketplace connectors, MCP and credit-free native actions

Two announcements this month changed the math on Zendesk action flows. On August 4, Zendesk opened a Zendesk Marketplace section for action flow connectors. On August 13, it stopped charging action credits for native Zendesk actions, including the ones AI agents and Copilot invoke. Action flows are now easier to plug into other systems, and most of the steps in a typical flow cost nothing to run.

For commerce brands, that's a bigger deal than it sounds. Most support work on an order follows the same shape: look something up, decide, do one thing in another system, then record what happened on the ticket. Now only the steps that reach into another system still cost credits. Since November 2025, agnoStack's Actionable Options have let support agents start that kind of flow from the order they're looking at.

Zendesk action flows since general availability

An action flow is built in the Zendesk action builder: one trigger, then a series of steps that act in Zendesk and in external systems. The action builder and action flows reached general availability in October 2025, according to Zendesk's release notes through October 31, 2025. It's been a busy ten months since:

• May 13, AI agents. Zendesk AI agents can now invoke custom actions and action flows from the AI agents workspace. The flow has to use the Run on demand trigger, and the AI agent receives "only the outputs passed by the last step of the flow."
• July 24, error handling. With step-level error handling in the action builder, each step can halt the flow or continue, with separate paths for success and failure. Rollout finished August 10.

If you're new to the action builder, Thomas Verschoren's overview of Zendesk's Action Platform on Internal Note is a good primer on how flows, custom actions and connectors fit together.

Zendesk action flow connectors on the Marketplace

The August 4 release added a new segment of the Zendesk Marketplace "dedicated to action flow connectors." Zendesk says admins can install and use 50+ connectors, including Slack and Microsoft Teams. It also highlights the MCP Client, which "allows you to link out to any third party hosting an MCP Server" and use its actions in action flows.

The first partner-built connector comes from SweetHawk. In Zendesk's words: "As we move out of the early access program (EAP) phase, this initial release focuses on our Zendesk-built connector and our first partner-built connector."

That's the "pluggable" part. Zendesk already had its own prebuilt connectors, and custom actions for everything else. The Marketplace makes connectors something partners can package and ship, and an MCP server can expose a whole set of tools through one connection. Thomas Verschoren's deep dive on connected action flows covers the new Connections area and the MCP Client in detail. His demo flow checks a customer's orders and adds an internal note when one is still open, which is a commerce pattern through and through.

Action credits: what's free now

The August 13 change is simpler to explain. These no longer use action credits:

• Action flow triggers
• Flow control and utility steps
• Zendesk actions, including tasks, approvals and custom objects
• AI agent and Copilot-invoked actions
• IT asset management actions
• Test runs performed in the action builder

Two kinds of steps still use credits: third-party connectors, including SaaS and partner integrations, and custom actions that you define. Plan allowances, pricing and quantities haven't changed, and existing flows picked up the new rules automatically on August 13.

The short version: you now pay for the step that reaches outside Zendesk, not for the logic around it or for writing the result back to the ticket.

Free test runs matter too. You can iterate on a flow until it's right without spending your monthly allowance.

Write the result back to the ticket

The pattern this makes cheap is the one we'd recommend for any commerce flow: do one thing outside Zendesk, then write down what happened inside it.

Take a damaged-item claim. The flow starts on a trigger, branches on order status and value, and makes one call to the system that issues the replacement or the return label. That call is a connector or custom action, so it uses credits. Everything after it is native: an internal note with the label link, a tag the team can report on, a custom field with the new order number, a status change. Before August 13, each of those write-back steps used a credit too. Now they're free, so there's no reason to leave them out.

It also changes how you design flows for AI agents. A Run on demand flow only hands its last step's outputs back to the AI agent, so the ticket is the natural place to record everything else the flow did. Credit-free native actions mean every flow can leave a clear, reportable record there, whether a person or an AI agent started it.

Actionable Options: action flows from the order panel

This is where agnoStack comes in. Actionable Options shipped in agnoStack 5.34.0 in November 2025. They let retailers put custom actions directly on the agnoStack Order Details panel in the Zendesk ticket, configured through four paths: Knots.io, Make.com, the Zendesk Data Provider, and the Zendesk Action Builder.

With the Action Builder path, a support agent looking at an order picks an option and an action flow runs with the full picture: the order, the ticket and the agent working it, the conversation so far, and what your connected retail back office knows about that customer, from CRM and loyalty to marketing automation and ratings and reviews. The flow does the work, using agnoStack's connectors (coming soon to early access), and writes the result back to the ticket. With the August changes, only the step that reaches another system uses credits.

That matters most for the brands we work with, which run on Shopify, BigCommerce, commercetools, VTEX, Adobe Commerce and more, alongside subscription, loyalty and returns providers. A connector covers the systems it was built for, and the Marketplace will keep growing. Actionable Options put the flow on the order panel your team already uses, wherever that order lives. Support agents stop copying order numbers into other tabs and become agents that act, right from the ticket.

What's next

Zendesk action flows aren't a year old yet, and this month alone they gained a Marketplace for connectors, alongside the MCP Client, and credit-free native actions. The AI agents that call them benefit from both. We're working on more for AI agents on our side, and we'll share it when it's ready.

Stay tuned: action flows from plain language. On August 20, Zendesk opened an early access program for AI-powered action flow creation through admin copilot, open to Suite Professional plans and above. Admins describe a use case in plain language and admin copilot generates the whole flow, including JavaScript for custom code steps, which can transform data but can't make network calls. We're digging in and will share more soon.

To see Actionable Options and agnoStack's order panel in your own Zendesk, schedule a demo. For help wiring an action flow to Actionable Options, email support@agnostack.com.