feat(datasource-zendesk): add Zendesk datasource

[christophebrun-forest]

Summary

New @forestadmin/datasource-zendesk package: a datasource exposing Zendesk tickets, users and organizations over the Zendesk API, with condition-tree translation, custom-field introspection, and two plugins (close-ticket, create-ticket-with-notification).

What's included

• Collections for tickets / users / organizations (CRUD + count) over the Zendesk Search & resource APIs
• Condition-tree → Zendesk Search translation, with the primary key resolved via direct id lookup (outside Search)
• Custom-field introspection at boot (ticket_fields / user_fields / organization_fields) mapped to Forest columns
• Plugins: close-ticket and create-ticket-with-notification (multi-step form with email templates)

Behavior & limitations

• Zendesk Search has no OR operator: multi-value In/NotIn matches each value exactly only on the primary key; on other fields Zendesk ANDs the terms (documented in the README).
• The Search API caps pagination at 1000 results; larger windows raise UnsupportedOperatorError.
• Aggregation is limited to Count (no groups), reflecting Zendesk Search capabilities.

Correctness highlights (addressed during review)

• Scope/segment enforcement: an id-lookup combined with other conditions is re-checked in memory, so list/update/delete/count never bypass the caller's perimeter (including scopes on the derived requester_email).
• Bulk update/delete page through every match up to the Search cap instead of silently affecting only the first 100, and warn when the cap is exceeded.
• Pagination honors non-page-aligned skip/limit by fetching the covering pages and slicing.
• Aggregate count verifies record existence rather than trusting the requested id count.
• description is ignored on update (Zendesk derives it from the first comment and cannot edit it afterwards).
• create-ticket form loads the selected record's fields so requesterEmailDefault and {{record.x}} template tokens are populated on the second step.
• Operator vocabularies are advertised so the operators-equivalence decorator does not rewrite supported filters into an unsupported Or.

Testing

• yarn workspace @forestadmin/datasource-zendesk test → 133 tests passing
• lint + build green
• Validated end-to-end against a live Zendesk account from a NestJS POC (ticket creation with notification, filtering, scoped delete)

🤖 Generated with Claude Code

Note

Add Zendesk datasource with ticket, user, and organization collections

• Introduces a new @forestadmin/datasource-zendesk package exposing three collections (zendesk_ticket, zendesk_user, zendesk_organization) backed by the Zendesk Search and REST APIs via a new ZendeskHttpClient.
• Supports list, create, update, delete, and count operations with filter/sort/pagination; searches are translated from Forest condition trees to Zendesk Search query strings via condition-tree-translator.ts.
• Introspects active custom fields at startup and maps them into the collection schema; ticket custom fields use custom_<id> naming, user/organization fields use the Zendesk field key.
• Adds two smart-action plugins: closeTicketPlugin (mark tickets solved/closed with outcome classification) and createTicketWithNotificationPlugin (create a ticket with an optional public/private comment and writeback of the ticket id).
• Risk: Zendesk Search is capped at 1,000 results (MAX_TOTAL_RESULTS); bulk update/delete operations that match more than 1,000 records will silently stop after that cap with a logger warning.

^{Macroscope summarized f9e1f86.}

[qltysh]

26 new issues

Tool	Category	Rule	Count
qlty	Structure	Function with high complexity (count = 14): extractIdLookup	11
qlty	Structure	Function with many parameters (count = 6): constructor	7
qlty	Structure	Function with many returns (count = 5): extractIdLookup	6
qlty	Structure	Deeply nested control flow (level = 4)	2