Monk Document Processed TriggerInstall

Summary

Poll for newly processed documents from the Monk Document Extraction API at a configured interval, filtering by verification status, upload ID, and processing status, and emit matching documents either individually or as a batch.

Inputs

• Server Environment (required) — Select whether to use the base URL from the Monk API credentials or specify a custom server URL.
• Custom Server URL — Specify a custom Monk API server URL (used only if Server Environment is set to 'Custom').
• Poll Interval (Minutes) (required) — Set how often (in minutes) the trigger checks the Monk API for newly processed documents, between 1 and 60.
• Items Per Page (required) — Number of documents to fetch on each API call, between 1 and 100.
• Emit Mode (required) — Choose to emit each new document as a separate execution or all new documents in a single batch.
• Verified Filter (required) — Filter documents by verification status: all, verified only, or unverified only.
• Upload ID Filter — Optionally filter documents to only those belonging to a specific upload ID.
• Status Filter (required) — Filter documents based on processing status: all, completed only, failed only, or processing only.
• Include Document Data (required) — Choose whether to include the extracted document data in the trigger's output.

Output shape

A single execution emitting either one document per execution or a batch of documents, each containing metadata such as document ID, format, status, timestamps, creator info, and optionally the extracted document data.

Documents are fetched incrementally using a 'processed_after' timestamp to avoid duplicates. The trigger maintains internal state of seen document IDs and last processed date to emit only new documents since the last poll. Errors during polling emit an error object. The emit behavior depends on the chosen 'Emit Mode' configuration.