> For the complete documentation index, see [llms.txt](https://detected.gitbook.io/detected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://detected.gitbook.io/detected-docs/api-overview/webhooks/common-questions.md).

# Common Questions

| **Question**                                                                         | **Answer**                                                                                                                                                                                                                                                                                                                                                                  |
| ------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Does the profile webhook lifecycle diagram mean webhooks only fire on status change? | **No.** `profile.updated` also fires for some metadata changes (e.g. `customer_reference`, assignee) without `review_status` changing. The diagram shows the main lifecycle moments, not every trigger. In-progress portal work and adding a person via API often do not fire Status Webhooks until submit or a later step. See **When** `profile.updated` **fires** below. |
| Can we subscribe to specific statuses only?                                          | **No.** You cannot filter by status in the dashboard. Enable the Status Webhook once; your handler filters on `data.review_status`. Use early events (`profile.created` / `profile.updated` with `Processed`) for parallel sales or operations work while due diligence continues.                                                                                          |
| What fires when a business or individual is added or changed?                        | **Business:** `profile.created` on case create; `profile.updated` on status and metadata changes. **Adding a person** (`POST /representatives`) does not webhook by itself.                                                                                                                                                                                                 |
| Is the webhook payload enough for CRM?                                               | **No.** Use the webhook as a trigger, then GET endpoints for full data.                                                                                                                                                                                                                                                                                                     |


---

# 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://detected.gitbook.io/detected-docs/api-overview/webhooks/common-questions.md?ask=<question>&goal=<user_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.