The Freshservice triage sender forwards available native-event and sidebar attachment metadata in
its signed ticket payload without a Freshservice metadata API request or additional credential.
Text-only workflow definitions accept the optional manifest independently of file ingestion.
Capture remains explicitly incomplete until runtime qualification establishes source coverage.
The operator installs the prepared Freshservice app ZIP before this behavior becomes live.
The Freshservice connection client accepts account-qualified attachment URLs with or without
attachment IDs. Ingestion preserves signed query strings, refuses unrelated destinations and
redirects, and reports ordinary file failures while continuing to later attachments. The
procedure exposes explicit completeness status and a documented per-file report, with limits
of 20 files, 100 MiB per file, and 250 MiB total. Workflow activation and sandbox storage
qualification are separate release steps.
Newly published Freshservice triage workflows can carry the Customer verified at signed admission
into the private-note summary. Blank client labels and requester email domains no longer contradict
that identity. Existing pinned workflow versions are unchanged until operators publish a successor.
The approved organization knowledge move now admits whole units of up to 80 existing chunks and
4 MiB of complete preparation arguments, qualified against all 58 units in its 140-entry inventory.
Source checks, atomic ownership and RAG writes, text limits and combined write limits remain enforced.
This change supports preparation of that approved cohort; deployment and migration completion still
require their existing readiness checks.

