{"id":27,"date":"2026-03-31T18:53:44","date_gmt":"2026-03-31T18:53:44","guid":{"rendered":"https:\/\/configly.app\/updates\/?p=27"},"modified":"2026-03-31T18:53:44","modified_gmt":"2026-03-31T18:53:44","slug":"stop-breaking-prod-why-i-built-a-configuration-manager-for-zendesk","status":"publish","type":"post","link":"https:\/\/configly.app\/updates\/stop-breaking-prod-why-i-built-a-configuration-manager-for-zendesk\/","title":{"rendered":"Stop Breaking Prod: Why I Built a Configuration Manager for Zendesk"},"content":{"rendered":"\n

You know the feeling.<\/strong><\/p>\n\n\n\n

It’s 4pm on a Friday. Someone’s updated a trigger. Maybe two triggers. Support tickets are routing to the wrong group, SLAs are firing on the wrong conditions, and three agents are pinging you asking why their views look different.<\/p>\n\n\n\n

You open Admin Centre, stare at 140 triggers, and try to figure out what changed. There’s no diff. No history. No audit trail that actually tells you what the trigger looked like before<\/em>. Just the current state and a timestamp that says “modified 2 hours ago.”<\/p>\n\n\n\n

Good luck.<\/p>\n\n\n\n

\n\n\n\n

The problem nobody talks about<\/h2>\n\n\n\n

Every Zendesk instance over a certain size becomes a house of cards. Triggers depend on ticket fields that feed into automations that affect SLAs that route to views. Change one thing and three other things break silently.<\/p>\n\n\n\n

And the tools Zendesk gives you to manage this? A flat list sorted by position. Maybe a search bar if you’re lucky. Want to know which triggers reference a custom field before you delete it? Click through every single one. Want to test a change before it hits production? You’ll need a sandbox \u2014 and that means Enterprise pricing, or a sponsored instance if you’re a partner.<\/p>\n\n\n\n

For the mid-market admin managing a complex instance on Suite Growth or Professional, the options are: be very careful, or break things and fix them fast.<\/p>\n\n\n\n

Neither is a real strategy.<\/p>\n\n\n\n

I’ve been that admin<\/h2>\n\n\n\n

I’ve spent years configuring Zendesk instances for clients. I’ve made the Friday afternoon trigger change that broke routing. I’ve spent evenings undoing damage because there was no way to preview what a change would do. I’ve maintained spreadsheets \u2014 actual spreadsheets \u2014 to track which triggers do what, because Zendesk doesn’t give you a dependency map.<\/p>\n\n\n\n

At some point I stopped accepting it and started building the tool I wished existed.<\/p>\n\n\n\n

Configly: Infrastructure as Code for Zendesk<\/h2>\n\n\n\n

Configly connects to your Zendesk instance via OAuth, pulls your configuration across 8 object types (triggers, automations, macros, views, ticket fields, user fields, organisation fields, and SLAs), and gives you what Zendesk doesn’t:<\/p>\n\n\n\n

See everything, clearly.<\/strong> Your entire configuration in one place, searchable, filterable, with human-readable conditions instead of raw JSON. No more clicking through 140 triggers to find the one that references a specific field.<\/p>\n\n\n\n

Know what changed.<\/strong> Configly takes snapshots of your configuration and lets you diff any two points in time. Exact before-and-after comparison, field by field. No more guessing what someone modified last Tuesday.<\/p>\n\n\n\n

Understand dependencies.<\/strong> Before you delete that custom field or deactivate that trigger, Configly maps every object that references it. See the blast radius before you pull the trigger (pun intended).<\/p>\n\n\n\n

Test without risk.<\/strong> The What-If simulator lets you model changes against your real configuration without touching production. See what would break, what would change, and what would stay the same. Sandbox-level confidence without the sandbox.<\/p>\n\n\n\n

Push when ready.<\/strong> When you’re confident, apply changes directly from Configly to your live instance. Reviewed, tested, intentional changes instead of live-editing in Admin Centre with your fingers crossed.<\/p>\n\n\n\n

Sync to GitHub.<\/strong> Export your configuration as YAML and version it properly in Git. Real version control, real audit trail, real rollback capability.<\/p>\n\n\n\n

Enterprise-level control without Enterprise pricing<\/h2>\n\n\n\n

Here’s what frustrates me about the Zendesk ecosystem: the admin managing 200 triggers on Suite Professional needs configuration management just as much as the Enterprise customer with a sandbox. Maybe more, because they don’t have the safety net.<\/p>\n\n\n\n

Configly starts at \u00a399\/month for a single instance. Multi-instance management for partners and agencies is \u00a3349\/month. No Enterprise contract required. No sandbox required.<\/p>\n\n\n\n

If you’re managing Zendesk configuration for clients across multiple instances, the Agency plan at \u00a3999\/month gives you a unified dashboard across all of them.<\/p>\n\n\n\n

Built by a practitioner, not a platform company<\/h2>\n\n\n\n

Configly isn’t built by a team that read about Zendesk in a market report. It’s built by someone who configures Zendesk instances every day, who knows the pain firsthand, and who got tired of working around limitations that shouldn’t exist.<\/p>\n\n\n\n

Every feature exists because I needed it. The dependency mapper exists because I once deleted a ticket field that broke 12 triggers. The snapshot diffing exists because I spent an hour trying to figure out what changed after a colleague “tidied up” some automations. The What-If simulator exists because I was tired of testing changes by making them live and hoping for the best.<\/p>\n\n\n\n

Get started<\/h2>\n\n\n\n

Configly is live now at go.configly.app<\/a>. Connect your Zendesk instance, take your first snapshot, and see your configuration the way you’ve always wanted to.<\/p>\n\n\n\n

Your Zendesk configuration is too important to manage by memory and crossed fingers. It’s time to manage it properly.<\/p>\n\n\n\n

\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

You know the feeling. It’s 4pm on a Friday. Someone’s updated a trigger. Maybe two triggers. Support tickets are routing to the wrong group, SLAs…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[4,8],"tags":[],"class_list":["post-27","post","type-post","status-publish","format-standard","hentry","category-news","category-product-updates"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/posts\/27","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/comments?post=27"}],"version-history":[{"count":1,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/posts\/27\/revisions"}],"predecessor-version":[{"id":28,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/posts\/27\/revisions\/28"}],"wp:attachment":[{"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/media?parent=27"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/categories?post=27"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/configly.app\/updates\/wp-json\/wp\/v2\/tags?post=27"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}