@bijection/connectors/zendesk entrypoint to declare Zendesk resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
tickets
observations: Evidence-checked tickets
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:zendesk/tickets/observations/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: zendesk. Keep credential material in the private credential inventory.
Provider setup requirements:
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Cursor incremental ticket export. The provider exclusion window is sixty seconds. Explicit deleted rows withdraw tickets. A terminal page may retain an already committed cursor; an initial terminal page without a cursor is held without changing the serving publication. HTTP 400 resets an existing cursor; other failures cannot discard it. Compiled declaration examples and configuration details are published in the connector reference. Configure the typed setup fields withbind and keep credentials in native
credential custody. Use zendesk.credential("inventory-name") for a private
credential reference.
Compiled declaration examples and configuration details are published in the connector reference.
Package replay is not live qualification. See the generated catalog for exact
declared scenarios and evidence status.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.