Zapier integration in public beta, GitHub Sync that holds up on large instances, and more reliable webhooks and Public API. Here is what shipped and why it matters.

Zendesk is a strong platform. What it does not give you is a safety net around configuration change. No version history on your triggers and automations, no way to preview the blast radius before you apply, and no easy way to get config events out to the rest of your stack. That gap is where Configly lives, and v1.3.0 widens it on every side.

Configly now connects to Zapier (public beta)

This is the headline. Configly plugs into Zapier, so you can wire your health checks, syncs, and config changes into the thousands of apps your team already uses. No code, no middleware to babysit.

A few things you can set up in about two minutes:

  • Drop a Slack message the moment a health check score falls, so config drift gets noticed the same day it happens, not at the next quarterly audit.
  • Alert your team when a sync fails on a revoked or expired Zendesk connection, so a broken integration does not sit silent for a week.
  • Post to a channel every time changes are applied to your production Zendesk. That is a running change log your whole team can see, without anyone maintaining a spreadsheet.
  • Run a health check on a schedule and route any critical finding to wherever your team actually works.

The triggers cover sync completed, sync failed, health check completed, health score changed, critical finding detected, and config applied. Actions let you run a health check and preview an apply. Searches let you look up a config item or a connection and feed it straight into the next step of a Zap.

It is in public beta and live in the Zapier app directory now. One setup note worth knowing up front: turning on a trigger registers a webhook on your connection, and that is a write operation, so connect Configly to Zapier with a read/write API key. A read-only key cannot register webhooks, so the triggers will not fire.

GitHub Sync that holds up on real estates

GitHub Sync exports your Zendesk configuration to a Git repo as version-controlled YAML. In this release it stops being a feature that only works on small instances.

Large estates with 1,500 or more config files used to fail partway through a sync. That is fixed. Big multi-brand and agency-managed instances now export cleanly from end to end.

Two more changes that take the friction out of it:

  • A sync now shows clearer progress and realistic time expectations while it runs, so a long export on a large instance does not look like a hang.
  • A failed sync no longer leaves the connection stuck. You can retry without disconnecting and reconnecting first.

If you have been holding off on GitHub Sync because your instance is too big, it is worth another look.

More reliable webhooks and Public API

If you build on top of Configly, this release tightens the contract.

  • The config applied webhook now fires reliably whenever an Apply finishes successfully. If you were relying on it to confirm a change landed, it now does what it says.
  • The sync failed webhook now fires for connection and credential problems, such as revoked OAuth or an expired token, which is the most common real-world failure. It carries full failure detail, not just a bare error string.
  • Apply history now includes an operation identifier, so you can correlate an apply across calls and tie it back to the matching webhook delivery.
  • A new endpoint returns your sync attempt history, both successes and failures, so you can build your own monitoring on top.

Also fixed

  • Disconnecting a connection no longer errors when there is no active connection.
  • Fixed an email-matching issue affecting mixed-case email addresses.

What is next

Zapier is the first of the workflow platforms. n8n and Make are next in the pipeline, so if you live in one of those instead, support is coming. The async work that lets long-running exports like Sync to GitHub run from inside a Zap is also on the roadmap.

Try it

If you already run Configly, find Configly in the Zapier app directory and connect it with a read/write API key. If you do not, this is a good release to start on. Configly is infrastructure-as-code for Zendesk, built by a Zendesk practitioner, for the admins, consultants, and agencies who carry the weight of keeping a Zendesk instance honest.

Full release notes are in the change log