Alfred v1.66.3.0
Alfred
Alfred
  • Introduction
  • Authentication
  • Event API
    • File Events
      • File Add To Job
      • File Category Create
      • File Category Delete
      • File Change Tag
      • File Done
      • File Extracted Data Create
      • File Extracted Data Delete
      • File Failed
      • File Move
      • File Move To Pending
      • File Move To Recycle Bin
      • File Property Create
      • File Property Delete
      • File Remove Tag
      • File Status Update
      • File Update
    • Job Events
      • JobCreateEvent
      • JobExceededRetriesEvent
      • JobFailedEvent
      • JobFinishedEvent
      • JobInvalidEvent
      • JobRetryEvent
      • JobStageUpdateEvent
      • JobStartEvent
    • Event Structures
  • endpoints
    • Alfred
    • File
      • Remote Sources
      • File Status
    • Deferred Session
    • Job
      • Job Stages
    • Tag
    • Metadata
    • Metadata Values
    • Report
    • Account
    • Company
Powered by GitBook
On this page

Was this helpful?

  1. Event API

File Events

Last updated 1 year ago

Was this helpful?

File Events in Alfred's Event API are a cornerstone in monitoring and managing the document processing workflow within the platform. These events are specifically designed to respond to a variety of actions or status changes related to files, making them a crucial element in tracking document progression and managing the automated workflow. Each File Event, such as "FileAddToJobEvent," "FileDoneEvent," or "FileFailedEvent," is triggered by a specific action, like adding a file to a job, completing file processing, or encountering a processing failure. This enables a responsive and interactive environment where changes in the file status are closely monitored and acted upon. These events are vital for applications that need to track the progress of files in real-time, manage document processing stages efficiently, and respond promptly to any changes in the file lifecycle.

Receiving File Events is streamlined through the Events API, which sends JSON-based payloads to a specified Webhook endpoint. This process is a part of the Event Loop, an event-driven sequence that starts with a user-triggered event, leading to the receipt of a JSON payload describing the event.

The system then acknowledges the event, and the server performs any required actions based on the event details. This loop, documented on the page, allows for a dynamic interaction between the Alfred platform and the user's application, ensuring that each significant file-related action is captured and can be acted upon in a timely manner.

File Event List

Event Type
Description

Triggered when a file is added to a job for processing.

Occurs when a new category is created for a file.

Signals the deletion of a file's category.

Indicates a change in the tag associated with a file.

Marks the completion of file processing.

Triggered when new data is extracted from a file.

Occurs when extracted data from a file is deleted.

Indicates a failure in file processing.

Signals the movement of a file within the system.

Triggered when a file is moved to a pending state.

Indicates movement of a file to the recycle bin.

Reflects the creation of a file property.

Signals the deletion of a file property.

Signals the removal of a tag from a file.

Indicates an update in the file's status.

Triggered when a file is updated in any manner.

Event Loop documentation
FileAddToJobEvent
FileCategoryCreateEvent
FileCategoryDeleteEvent
FileChangeTagEvent
FileDoneEvent
FileExtractedDataCreateEvent
FileExtractedDataDeleteEvent
FileFailedEvent
FileMoveEvent
FileMoveToPendingEvent
FileMoveToRecycleBinEvent
FilePropertyCreateEvent
FilePropertyDeleteEvent
FileRemoveTagEvent
FileStatusUpdateEvent
FileUpdateEvent