> 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/triggers-1.md). # All Quiet Triggers A webhook trigger that starts a graph when All Quiet posts an incident to it, so agents can react to incidents rather than only create them. ## AllQuiet Incident Trigger ### What it is Triggers a graph when All Quiet posts an incident to this webhook ### How it works Runs when All Quiet's outbound webhook posts to this block's URL. Because the request body is whatever Handlebars template you configure in All Quiet, the block does not impose a schema: it always emits the raw `payload`, and additionally reads the well-known keys from both All Quiet's stock flattened template (`incidentId`/`incidentTitle`/`incidentProperties`) and a fuller template that forwards the incident itself. If you enable signing in All Quiet and paste the secret into the block, each delivery is verified as an HMAC-SHA256 of `:` — both the All Quiet (`x-aq-signature`) and AWS (`x-amzn-event-signature`) header formats are accepted — and stale timestamps are rejected to prevent replay. Leave the secret empty and the webhook URL is the only credential. ### Inputs | Input | Description | Type | Required | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | -------- | | signing\_secret | Optional. If All Quiet's outbound webhook has signing enabled, paste the signing secret here and deliveries with a missing or bad signature are rejected. Both the All Quiet (x-aq-signature) and AWS (x-amzn-event-signature) formats are accepted. Leave empty for unsigned webhooks. | str | No | ### Outputs | Output | Description | Type | | --------------- | ------------------------------------------------------ | ---------------------------------- | | error | Error message if the operation failed | str | | payload | The raw payload All Quiet delivered | Dict\[str, Any] | | incident\_id | ID of the incident that fired | str | | incident\_title | Title of the incident | str | | event\_id | ID of the timeline event that triggered this delivery | str | | status | Incident status, if the payload template includes it | "Open" \| "Resolved" | | severity | Incident severity, if the payload template includes it | "Critical" \| "Warning" \| "Minor" | | attributes | Incident attributes flattened to a name/value mapping | Dict\[str, str] | ### Possible use case An incident is raised in All Quiet by a Prometheus alert. The trigger starts a graph that pulls the incident's attributes, queries the relevant logs and dashboards, drafts a probable-cause summary with an LLM, and posts it back as a comment — so the responder opens an incident that already has a first pass of investigation attached. *** --- # 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/triggers-1.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.