Connector library

Implemented source CX & Support APIs

Zendesk connector.

Create and retrieve Zendesk Support tickets, add private or public comments, and update ticket status with collision protection.

Connector download

Download Zendesk

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.2.0.1 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Bearer token
Connection settings
API Base URL
Package size
8 KB
SHA-256
2e8b0c08be3655280fc304035c451b945736f1dba8272133b5e1445eae55fbc7

Version history

What's new

  1. v0.2.0.1Latest · 2026-10-03 · Implemented source

    Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.

  2. v0.2.0.0Earlier · 2026-10-02 · Implemented source

    Create and retrieve Zendesk Support tickets, add private or public comments, and update ticket status with collision protection.

  3. v0.1.1.0Earlier · 2026-10-02 · Starter scaffold

    Historical generic HTTP scaffold, retained unchanged.

Included in this version

Included actions

Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.

Get ticket

Retrieve a ticket and its update timestamp.

Create ticket

Open a ticket with an initial private comment and optional requester ID.

Add ticket comment

Append a comment while protecting against concurrent changes.

Update ticket status

Set an allowed ticket status with collision protection.

Vendor API

API and access

Implementation considerations
  • Support APIs often distinguish agent/admin operations from end-user request operations; confirm the right permission model.
  • Keep requester identity, organization, assignee, status, and external IDs mapped explicitly.
  • Use ticket events for updates, but protect against loops when CXFabric writes back to the same system.
  • Zendesk tickets represent customer support communication and can originate from email, Help Center, chat, phone, social, or the API.
  • CXFabric Zendesk workflows should distinguish agent/admin ticket operations from end-user request operations and preserve requester context.

Support

Need help with Zendesk?

Tell us what you need to connect or change.