> For the complete documentation index, see [llms.txt](https://docs.tagshelf.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tagshelf.dev/event-api/fileevents/file-category-create.md).

# File Category Create

### Usage

This file event triggers when a tag has been successfully assigned to a specific file within the Alfred platform. In the `description` key it is possible to find the tag under which the file was classified. 

The file will continue the corresponding pipeline after a successful classification.

### Example JSON Payload

```
{
  "event_id": "(UUID format) - Unique identifier for the event.",
  "event_type": "Describes the type of event that occurred.",
  "event_time": "(floating-point numeric timestamp) - Unix timestamp representing the time when the event occurred, including milliseconds.",
  "event": {
    "event_name": "Name of the specific event.",
    "event_type": "Type of the event, often matching or related to the outer event_type.",
    "company_id": "(UUID format) - Unique identifier for the company associated with the event.",
    "company_name": "Name of the company associated with the event.",
    "file_log_id": "(UUID format) - Unique identifier for the log entry related to the file event.",
    "description": "Brief textual description of the event or action taken.",
    "confidence": "(floating-point numeric value) - Confidence level of the action taken or the classification, typically between 0.0 and 1.0.",
    "creation_date": "(ISO 8601 date format) - Date and time when the file category was initially created.",
    "update_date": "(ISO 8601 date format) - Date and time when the file category was last updated."
  }
}
```

```
{
  "event_id": "abcd1234-ef56-7890-gh12-ijkl34567890",
  "event_type": "file_event_type",
  "event_time": "1651018865.75",
  "event": {
    "event_name": "file_category_create_event",
    "event_type": "file_event_type",
    "company_id": "123e4567-e89b-12d3-a456-426614174000",
    "company_name": "Example Company",
    "file_log_id": "123e4567-e89b-12d3-a456-426614174002",
    "description": "Initial classification",
    "confidence": "0.95",
    "creation_date": "2023-04-26T12:00:00Z",
    "update_date": "2023-04-27T12:00:00Z"
  }
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tagshelf.dev/event-api/fileevents/file-category-create.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.