With Zendesk phasing out API tokens, SendSafely has updated our Zendesk Dropzone Connector for GCP to use OAuth 2.0 instead. Zendesk's deadlines for this cutover are detailed here.

Unlike our AWS and Azure connectors, the GCP connector can't be updated in place. Several resources it creates use fixed names that don't vary by deployment — the (default) Firestore database, Secret Manager secret IDs, and the zd-connector-sa service account — and your current connector already occupies these in its project, so redeploying into that same project will fail.

Instead, deploy a new connector into a new GCP project by following Installing the Dropzone Connector for Zendesk (GCP), point your Dropzone's webhook at the new connector once it's working, then decommission the old one.