> For the complete documentation index, see [llms.txt](https://docs.coresignal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coresignal.com/self-service/features-and-tools/monitors.md).
# Monitors
Track employee-profile changes with weekly webhooks. Monitor new matches, removals, and profile updates without rerunning queries.
Tracking changes across employee profiles, such as job moves and new roles, normally means rerunning the same query and comparing results by hand. Coresignal’s [Monitors](https://dashboard.coresignal.com/monitors) help you automate this by setting up an ongoing webhook on a query that reports any matching profile changes weekly. This means you can find the right profiles that match your query once, and you’ll be regularly notified of changes to that list.
Monitors give you the following webhook insights:
* Total matches – shows total profile matches to the query
* New matches – shows new profiles that started matching the saved query after the webhook was created
* No longer matching – shows profiles that stopped matching the query after the webhook was created
* Profile updates – shows the number of profiles that have been updated after the webhook was created
### Monitors setup
You can set up your Monitors in two ways: via [AI Data Search](/self-service/features-and-tools/ai-data-search.md) or directly through the [Monitors](https://dashboard.coresignal.com/monitors) tool in the Self-service dashboard. Below, you’ll find step-by-step guides for creating a webhook using both methods.
#### **Setup via AI Data Search**
{% stepper %}
{% step %}
**Write a prompt**
Open AI Data Search and write your prompt describing your search intent in plain language. You don’t need to write the query yourself.
{% prompt description="Find decision-makers working at Google with +7 years of experience." %}
```markdown
Find decision-makers working at Google with +7 years of experience.
```
{% endprompt %}
Alternatively, you can use any pre-made prompts that fit your search intent.
{% endstep %}
{% step %}
**Review results**
The search returns a preview list with 20 records. Check if they match your query and whether you want to make any adjustments. For example, if you additionally want to include location, specify that in the chat.
Optionally, in this step, you can also enrich your records with additional fields using the **Enrich** button.
{% endstep %}
{% step %}
**Create a webhook**
Once you have reviewed your list and finished your modifications, you can create a webhook.
In the right corner of the window, locate and click the **Start monitoring** button.
In the pop-up window, review your webhook information, including the number of current data records, notification frequency, and expiration date. You can also turn email notifications on or off and add a webhook URL, but these steps are not mandatory.
Next, click the **Create webhook** button. A pop-up will open, confirming that your webhook was created successfully.
{% endstep %}
{% endstepper %}
#### **Setup via Monitors tool**
Alternatively, you can create webhooks straight from the Monitors tool.
{% stepper %}
{% step %}
**Write a prompt**
Click the **Create new webhook** button and write your prompt or select one from the pre-made prompts library.
{% endstep %}
{% step %}
**Review the list and create your webhook**
From here, the process is identical to creating webhooks via AI Data Search. After you submit your prompt, the search returns results with 20 profiles to preview. You can refine your list in the chat or move directly to creating a webhook on the right side of the window.
{% endstep %}
{% step %}
**View your webhook list**
Once you’ve created your webhook, you can view it by clicking the **Monitors** tool. It opens a window where you can view your webhooks and filter them by all, active, or expired.
From the same window, you can create more webhooks, track how many more you can create before reaching the limit, and see activity updates in the **Last run** column.
{% endstep %}
{% step %}
**View information**
If you see that information has changed in any of your webhooks since the last run and you want to investigate it further, click on the one that you want to explore. In the new window, you’ll see what changes have been reported.
For example, you may see new profiles matching your query, profile updates, or profiles that no longer match the query.
In the top-right corner there’s also a **View query** button, which opens a window showing your prompt converted into the query used to match profiles. You can copy and reuse the query.
If you want to see exact changes to the records, you have to collect data.
{% endstep %}
{% step %}
**Collect profiles**
Export records by collecting profiles to see more information about the record changes. Click the **Collect Profiles** button in the top-right corner.
In the pop-up window you can choose, which profiles and their data you want to export:
* Profiles that started matching the query
* Profiles that stopped matching the query
* Profiles that changed
After finalizing your selection, click **Generate**.
{% endstep %}
{% endstepper %}
### Deleting a webhook
If a webhook is no longer relevant, you can delete it to make room for a new one. In the Monitors tool, click on the webhook you want to delete. In the new window, click the three-dot icon next to the **Collect profiles** button. Then click **Delete webhook**. Confirm your choice by clicking **Delete** or **Cancel**.
### Notifications
After you subscribe to Coresignal Monitors, once a week, you will get an email notification. If you don’t want to receive weekly email notifications, you can also turn them off and check the report page in self-service at any time you want.
### Limits
Each team can set up to 5 monitors, with each monitor tracking a query population of up to 10,000 employee profiles, checked on a fixed weekly schedule. Currently, Monitors can be set up only for employee data. They expire after 90 days but can be renewed.
---
# 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.coresignal.com/self-service/features-and-tools/monitors.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.