> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/codescan/codescan-integration/webhooks/slack-integration-with-zapier.md).
# Slack integration with Zapier
Zapier is a service that allows you to easily manage webhooks between apps. With Zapier, you can get notifications on your Slack channels when a scan is run.
{% hint style="info" %}
**Note:** This can be done at an Organization level or a Project level. At the Organization level, all scans will trigger the webhook. To choose this, use the **Administration > Webhooks** menu, either from the Organization page or a Project overview page.
{% endhint %}
1. First, sign up to Zapier and click **Make a Zap**.
2. Use the App search bar to find **Webhooks by Zapier** and then select it. Choose **Catch Hook** as the trigger event and then click on **Continue**.
3. You will be provided with a Custom **Webhook URL**, copy this URL.
4. Now login into CodeScan Cloud and go to **Administration > Webhooks** menu at either the Organization or Project level (see note above).
5. Create a **new webhook** using the custom URL and give it a name you will remember.
6. Now **run** a **scan** to trigger the webhook. This will allow you to find the the webhook in Zapier and customize the output as we'll see soon.
7. Next, search for **Slack** and select it. Choose the **Action Event** that you want.
8. Click **CONTINUE** and add your Slack Account. Click **CONTINUE**.
9. Customize the message to your liking using the webhook fields, your own text, and Zapier's formatting options.
10. Click **CONTINUE**, then send a test to Slack.
---
# 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://knowledgebase.autorabit.com/product-guides/codescan/codescan-integration/webhooks/slack-integration-with-zapier.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.
