> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/incident_search.md). # All Quiet Incident Search Blocks that read All Quiet incidents — fetching a single incident by ID, or searching the incident list by status, severity, team, text or time range. ## AllQuiet Get Incident ### What it is Fetches a single All Quiet incident by ID ### How it works Fetches one incident by ID and flattens its current status and severity onto the result — All Quiet stores those at the head of the incident's event timeline rather than on the incident itself. `allowed_intents` reports which transitions the incident will currently accept. Turning on `include_markdown` makes a second call for All Quiet's rendered markdown report, which bundles the attributes and full timeline into prose that is well suited to feeding an LLM. ### Inputs | Input | Description | Type | Required | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------- | ------------ | -------- | | incident\_id | ID of the incident to fetch | str | Yes | | include\_markdown | Also fetch an LLM-friendly markdown report of the incident, including its attributes and full timeline. Costs one extra API call. | bool | No | | region | The All Quiet deployment your API key belongs to. Use EU if you signed up on allquiet.eu. | "us" \| "eu" | No | ### Outputs | Output | Description | Type | | ---------------- | ----------------------------------------------- | ---------------------------------- | | error | Error message if the request failed | str | | incident | The incident | Incident | | status | Current status, when the incident reports one | "Open" \| "Resolved" | | severity | Current severity, when the incident reports one | "Critical" \| "Warning" \| "Minor" | | allowed\_intents | Transitions this incident currently accepts | List\[str] | | markdown | Markdown report, if include\_markdown was set | str | ### Possible use case A triage agent receives an incident ID from the trigger block, fetches it with `include_markdown` enabled, and feeds the markdown report — attributes, timeline and all — to an LLM to draft a first-response summary and suggest a likely cause. *** ## AllQuiet List Incidents ### What it is Searches All Quiet incidents by status, severity, team or text ### How it works Searches the incident list with All Quiet's server-side filters: status, severity, teams, a free-text title match, an unattended flag, and a created-at range. Results are paginated (`limit`/`offset`) and `has_more` reports whether further pages exist. Alongside the full list the block emits each incident individually, plus a list of bare `incident_ids` that feeds straight into Get Incident or Update Incident. ### Inputs | Input | Description | Type | Required | | -------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | -------- | | statuses | Only return incidents in these statuses. | List\["Open" \| "Resolved"] | No | | severities | Only return incidents at these severities. | List\["Critical" \| "Warning" \| "Minor"] | No | | team\_ids | Only return incidents routed to these teams. | List\[str] | No | | search\_term | Free-text match against the incident title. | str | No | | unattended | Set true to return only incidents nobody has picked up. | bool | No | | limit | Maximum number of incidents to return. | int | No | | offset | Number of incidents to skip, for paging. | int | No | | created\_from | Only incidents created at or after this ISO-8601 timestamp. | str | No | | created\_until | Only incidents created at or before this ISO-8601 timestamp. | str | No | | sort\_by | Field to sort the results by. | "Created" \| "LastUpdatedAt" \| "LatestInteraction" \| "Urgency" \| "Title" | No | | ascending | Sort oldest first instead of newest first. | bool | No | | region | The All Quiet deployment your API key belongs to. Use EU if you signed up on allquiet.eu. | "us" \| "eu" | No | ### Outputs | Output | Description | Type | | ------------- | ----------------------------------------------------- | --------------- | | error | Error message if the request failed | str | | incidents | All matching incidents | List\[Incident] | | incident | Each matching incident, emitted one at a time | Incident | | incident\_ids | IDs of the matching incidents | List\[str] | | count | Number of incidents returned | int | | has\_more | Whether more incidents are available beyond this page | bool | ### Possible use case A morning-standup agent lists every incident created in the last 24 hours, groups them by severity, and posts a digest — or, filtering on `unattended`, chases anything still open that nobody has picked up. *** --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://agpt.co/docs/integrations/block-integrations/incident_search.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.