user_id is the user a file or document belongs to — null when none is associated yet. document-collection-preprocessing-completed is the exception: it carries a users array instead.
These events cover preprocessing — validation and AI categorization of uploaded files. They do not cover finalization. Finalization creates Links and Tasks; track that with task-status-updated.
Document status updated
Event type:document-collection-file-status-updated
Fires every time an uploaded file changes status — not just when it reaches a final state — so you can show live progress. See the full list of file statuses in the Document Collections object.
These fields appear in every payload:
Each entry in
documents contains:
An early update, before categorization runs —
documents is empty:
documents is populated:
Documents preprocessed
Event type:document-collection-preprocessing-completed
Fires once per collection, right after the last file finishes processing — every file has reached a final status. Use it to know that validation and categorization are done for the whole collection.
This is not the same as finalized. It means every file has been validated and categorized. Whether the collection turns into employer records and Tasks depends on your settings and can happen later.
If a user later uploads more files to the same collection, this event fires again once those files finish processing.
A collection can belong to more than one user, so this event carries a
users array instead of the common single user_id field.