# September 4: Workflow configuration; support for Notion feeds; document OCR

### New Features

* :fire: Added [**Workflow** entity](https://docs.graphlit.dev/api-reference/graphql-data-model/workflows) to data model for configuring stages of content workflow; can be assigned to Feed or with `ingestPage`, `ingestFile`, or `ingestText` mutations to control how content is ingested, prepared, extracted and enriched into the knowledge graph.
* :bulb: Added support for [Notion feeds](https://docs.graphlit.dev/api-reference/graphql-data-model/feeds/create-notion-feed): now can create feed to ingest files from Notion pages or databases (i.e. wikis).
* :bulb: Added support for API-created **Observation** entities, which allow for custom observations of observable entities (i.e. Person, Label) on Content.
* :bulb: Added support for [Azure AI Document Intelligence](https://learn.microsoft.com/en-us/azure/ai-services/document-intelligence/overview?view=doc-intel-3.1.0) as an optional method for preparing PDF files, using OCR and advanced layout analysis.
* :bulb: Added summarization strategies, where content can be summarized into paragraphs, bullet points or headline.
* Added ability to assign [default Workflow and Specification to project](https://docs.graphlit.dev/api-reference/graphql-data-model/projects).
* Added more well-known link types, during link crawling, such as Discord, Airtable and TypeForm.
* :information\_source: Free/Hobby plan now has 5GB storage quota; any content ingested past that limit will be auto-deleted.
* :zap: **Actions** have been moved into Workflow entity.
* :zap: Link enrichment for Feeds has been moved into the Workflow enrichment stage, now called *link crawling*.  `ExcludeContentDomain` property has been reversed and is now called `IncludeContentDomain`.

### Bugs Fixed

* GPLA-1204: Failed to ingest content with backslash in name.
* GPLA-1276: Failed to ingest RSS posts which contained enclosure URI, but no post URI.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://changelog.graphlit.dev/september-2023/september-4-workflow-configuration-support-for-notion-feeds-document-ocr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.