> For the complete documentation index, see [llms.txt](https://docs.developers.symphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.developers.symphony.com/admin-guide/change-log/universal-webhook/univ-webhook-2.1.md).

# Univ Webhook - 2.1

The 2.1 version of the Universal Webhook features the following:

* A user guide has been added to the extension app which walks new users through setting up their first webhook.
* More assistance is available in the webhook creation form, with clearer descriptions of all of the requirements and a direct link to the user guide.
* Once configured by an admin, users can launch a chat with the Universal Webhook bot in one click, directly from this page.
* The admin section has been upgraded with an RSA key pair generator and additional guidance on setting up service accounts and rotating RSA keys.
* Our Admin Guide has been added to Symphony Docs.


---

# 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://docs.developers.symphony.com/admin-guide/change-log/universal-webhook/univ-webhook-2.1.md?ask=<question>&goal=<endgoal>
```

`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.
