> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.thehivetrigger.md).

# TheHive Trigger

On this page, you'll find a list of events the TheHive Trigger node can respond to and links to more resources.

{% hint style="info" %}
**TheHive and TheHive 5**

n8n provides two nodes for TheHive. Use this node (TheHive Trigger) if you want to use TheHive's version 3 or 4 API. If you want to use version 5, use [TheHive 5 Trigger](/integrations/builtin/trigger-nodes/n8n-nodes-base.thehive5trigger.md).
{% endhint %}

{% hint style="info" %}
**Examples and templates**

For usage examples and templates to help you get started, refer to n8n's [TheHive Trigger integrations](https://n8n.io/integrations/thehive-trigger/) page.
{% endhint %}

## Events <a href="#events" id="events"></a>

* Alert
  * Created
  * Deleted
  * Updated
* Case
  * Created
  * Deleted
  * Updated
* Log
  * Created
  * Deleted
  * Updated
* Observable
  * Created
  * Deleted
  * Updated
* Task
  * Created
  * Deleted
  * Updated

## Related resources <a href="#related-resources" id="related-resources"></a>

n8n provides an app node for TheHive. You can find the node docs [here](/integrations/builtin/app-nodes/n8n-nodes-base.thehive.md).

View [example workflows and related content](https://n8n.io/integrations/thehive-trigger/) on n8n's website.

Refer to TheHive's documentation for more information about the service:

* [Version 3](https://docs.thehive-project.org/thehive/legacy/thehive3/api/)
* [Version 4](https://docs.thehive-project.org/cortex/api/api-guide/)

## Configure a webhook in TheHive <a href="#configure-a-webhook-in-thehive" id="configure-a-webhook-in-thehive"></a>

To configure the webhook for your TheHive instance:

1. Copy the testing and production webhook URLs from TheHive Trigger node.
2. Add the following lines to the `application.conf` file. This is TheHive configuration file:

   ```
   notification.webhook.endpoints = [
   	{
   		name: TESTING_WEBHOOK_NAME
   		url: TESTING_WEBHOOK_URL
   		version: 0
   		wsConfig: {}
   		includedTheHiveOrganisations: ["ORGANIZATION_NAME"]
   		excludedTheHiveOrganisations: []
   	},
   	{
   		name: PRODUCTION_WEBHOOK_NAME
   		url: PRODUCTION_WEBHOOK_URL
   		version: 0
   		wsConfig: {}
   		includedTheHiveOrganisations: ["ORGANIZATION_NAME"]
   		excludedTheHiveOrganisations: []
   	}
   ]
   ```
3. Replace `TESTING_WEBHOOK_URL` and `PRODUCTION_WEBHOOK_URL` with the URLs you copied in the previous step.
4. Replace `TESTING_WEBHOOK_NAME` and `PRODUCTION_WEBHOOK_NAME` with your preferred endpoint names.
5. Replace `ORGANIZATION_NAME` with your organization name.
6. Execute the following cURL command to enable notifications:

   ```sh
   curl -XPUT -uTHEHIVE_USERNAME:THEHIVE_PASSWORD -H 'Content-type: application/json' THEHIVE_URL/api/config/organisation/notification -d '
   {
   	"value": [
   		{
   		"delegate": false,
   		"trigger": { "name": "AnyEvent"},
   		"notifier": { "name": "webhook", "endpoint": "TESTING_WEBHOOK_NAME" }
   		},
   		{
   		"delegate": false,
   		"trigger": { "name": "AnyEvent"},
   		"notifier": { "name": "webhook", "endpoint": "PRODUCTION_WEBHOOK_NAME" }
   		}
   	]
   }'
   ```


---

# 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.n8n.io/integrations/builtin/trigger-nodes/n8n-nodes-base.thehivetrigger.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.