← Marketplace
Zendesk logo

ConnectorSupport & comms

Zendesk

Tickets, macros, and customer history in as events; the same support capability, different vendor.

Ask how Zendesk fits what you run.

Answers are based on this listing. For anything it can't answer, our team can.

For anything this page can't answer, talk to us.

About

The target Zendesk connector reads tickets, comments, customer history, macros, tags, and SLA state. Capability indirection can preserve an operator contract only after auth, schema, behavior, policy, and recovery parity are validated; migration is not guaranteed to be configuration-only.

The target design uses cursor-based export, verified tenant and source context, and stable-key duplicate suppression for supported writes. Those controls reduce retry risk but do not guarantee the downstream ticket state. Zendesk is managed early access.

Highlights

  • Reads tickets, macros, customer history
  • Swap-in for Kustomer
  • Writes use idempotency keys and single-flight controls to suppress duplicate effects on retry
  • Provisioned with a deployment engineer through the early-access program
Kind
Connector
Category
Support & comms
Publisher
Fibric
Availability
Early access
Delivery
Managed by Fibric; nothing to install
Data direction
Reads and writes
Pricing
Early access
Sold by
Fibric
Support
Developed and supported by Fibric
Tags
support, cx, tickets, conversations

Authentication

A Zendesk API token paired with an agent email, stored in your tenant's secret store.

What it reads

  • Tickets and comments as they arrive and change
  • Requester history, tags, and custom ticket fields
  • SLA policy state and breach events per ticket

What it can do

  • Adds private comments to a ticket, idempotently
  • Updates ticket status, priority, and assignment
  • Applies tags an operator has decided on

How it works

1

Sense

Tickets and comments as they arrive and change.

2

Reason

Operators reason over this connector's signals next to the rest of your stack, so decisions are grounded in the same records you run on.

3

Act

Target capability: Adds private comments to a ticket, idempotently. Actual authority, duplicate controls, and recovery depend on the validated deployment and downstream system.

Pricing

Managed early access

This listing is informational and not self-serve. A deployment review must validate the connector, credentials, action boundary, recovery path, support, and contractual pricing before use.

Deployment engineer
Wires and verifies the integration with you during onboarding
Managed validation
Review maturity, authority, supported records, and deployment boundaries before go-live
Execution records
Supported reads, proposals, policy decisions, and reported outcomes kept for review
Support from the builders
Developed, run, and supported directly by Fibric

Requirements

System requirements
  • A Zendesk Support instance with API token access enabled
  • An agent identity with the ticket read and write permissions you intend to grant

Your deployment engineer verifies each line with you during onboarding.

Support and resources

Supported by the people who built it

This connector is developed, run, and supported by the same Fibric team. Support starts during onboarding with a named deployment engineer and doesn't hand you off afterward.

Works with

Listings this is designed to pair with. Each listing has its own live or managed early-access state.

Operator by Fibric

Order Risk

BearScope has a live governed order-risk path. This listing expresses that capability as a target operator contract, not as a public pack or generalized runtime claim.

View details

Operator by Fibric

Operations Analyst

Ask what is happening in plain language and get an answer grounded in your real data. Then turn that answer into a vetted action.

View details

Support & comms connector

Amazon Connect

Brings live and recorded call context into the operational picture, with status sync back to your CX platform of record.

View details

Support & comms connector

Slack

Posts the proposed action, waits for the human confirm, then executes, all inside a channel that keeps the record.

View details

Commerce & orders connector

Shopify

Streams orders, fulfillments, and inventory. Swapping storefronts is configuration, not a rewrite of your operator.

View details

Bring Zendesk into your early-access deployment

Early access means a deployment engineer wires this with you, and it runs propose-only until you approve live actions.