> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/manage/settings/notifications/technical-references/test-slack-webhook-notification.md).
# Test a Slack Webhook Notification in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
You can test a Slack webhook notification from Patch My PC (PMPC) Cloud both at the time it is created and afterward.
## Testing a Slack webhook notification at the time of creation
1. Follow the [Create a Slack Webhook Notification](/patch-my-pc-cloud/manage/settings/notifications/create-slack-webhook-notification.md) process.
2. Once you have entered and saved the webhook URL, click the small envelope beside the webhook URL () to send a test message.
The portal will send a test Slack notification and display the **Success - Test webhook has been sent** notification.
If your Slack webhook is valid, the test message appear as a notification and in the configured Slack channel:
## Testing a Slack webhook notification after it has been created
1. Follow the [Modify a Notification](/patch-my-pc-cloud/manage/settings/notifications/modify-notification.md) process and select the relevant Slack notification you want to test.
2. Click the small envelope beside the webhook URL () to send a test message.
The portal will send a test Slack notification and display the **Success - Test webhook has been sent** notification.
If your Slack webhook is valid, the test message appears as a notification and in the configured Slack channel:
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.patchmypc.com/patch-my-pc-cloud/manage/settings/notifications/technical-references/test-slack-webhook-notification.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
