Skip to main content
Use the @bijection/connectors/freshdesk entrypoint to declare Freshdesk 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

changes: Tickets by updated_since with the deleted view as deletions

The following example matches configuration standard.

Configuration: standard

Case: freshdesk/tickets/changes/standard. Connection and resource configuration are declared by this exact case. Credential kind: freshdesk. Keep credential material in the private credential inventory. Provider setup requirements:
Native admission analysis is available for this exact declaration. Collection: tickets
Recorded checks Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.

Provider guidance

Compiled declaration examples and configuration details are published in the connector reference. The connection is one helpdesk (domain fills https://<domain>.freshdesk.com/api/v2/), authorized by an API key as HTTP Basic <key>:X (a basic envelope). tickets.changes walks live tickets by updated_since with order_by=updated_at&order_type=asc: each request asks from the largest updated_at the previous page returned, a cursor the host derives from the retained page, so Freshdesk’s 300-page cap never binds. It then walks the deleted view (filter=deleted) from the beginning on every pass, because a soft delete is not documented to move updated_at; its tickets are withdrawn, and a restored ticket reappears in the live view. A finished pass carries the live bound and the next begins five minutes before it. Point reconciliation re-reads known tickets and never withdraws one. Whether filter=deleted honours updated_since and the sort is undocumented: a page that ignored either fails rather than being trusted. Nothing is written (no documented precondition). Built from the provider’s published API documentation; nothing here has run against Freshdesk or been qualified.

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.