# January 22: Support for Google and Microsoft email feeds, reingest content in-place, bug fixes ### New Features * :bulb: Graphlit now supports Google and Microsoft email feeds. Email feeds can be created to ingest past emails, or poll for new emails. Emails create an `EMAIL` content type. Attachment files can optionally be extracted from emails, and will be linked to their parent email content. If assigning a workflow to the feed, the workflow will be applied both to the email content and the extracted attachment files. * :bulb: Graphlit now supports reingesting content in-place. The `ingestText`, `ingestPage` and `ingestFile` mutations now take an optional `id` parameter for an existing content object. If this id is provided, the existing content will be updated from the provided text or URI source, and will restart the assigned workflow. * Added `restartAllContents` mutation to restart workflow on all partially-ingested contents in project. * Added `text` field to ConversationCitation type, which returns the relevant text from the content source with the citation. ### Bugs Fixed * GPLA-1313: Not extracting links from HTML * GPLA-2030: No text extracted from shapes in PPTX files --- # 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/january-2024/january-22-support-for-google-and-microsoft-email-feeds-reingest-content-in-place-bug-fixes.md?ask= ``` 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.