# July 4: Support for webhook Alerts, keywords summarization, Deepseek 128k context window, bug fixes ### New Features * :bulb: Graphlit now supports webhook Alerts. In addition to Slack notifications, you can now receive an HTTP POST webhook with the results of the published text (or text and audio URI) from a prompted alert. * Updated the Deepseek chat and coder models to support a [128k token context window](https://platform.deepseek.com/api-docs/#models). * Added `customSummary` property to `Content` object, which returns the custom summary generated via preparation workflow. * Added `keywords` summarization type, which is now stored in `keywords` property in `Content` object. * Added `slackChannels` query, which returns the list of Slack channels from the workspace authenticated by the Slack bot token. * :zap: We have changed the response from the `credits` query to return a single `ProjectCredits` object, rather than the list of correlated objects previously returned. The `credits` response now covers all credit usage over the time period specified. ### Bugs Fixed * GPLA-2874: Processing entities is taking longer than 30min for 300+ page PDF * GPLA-2875: Messages in queue expiring too early * GPLA-2881: Feed read count increasing, after hitting read limit * GPLA-2884: Need to handle Anthropic 'overloaded' API response * GPLA-2906: JIRA issue identifier not assigned to issue metadata --- # 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/july-2024/july-4-support-for-webhook-alerts-keywords-summarization-deepseek-128k-context-window-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.