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

# Integration

Show the notifications of your framework and every other script in the Striga Notify design.

Do the step for your framework, so **every** script on your server uses the new design, not only the Striga scripts.

{% tabs %}
{% tab title="ESX" %}
**No file to edit.** Striga Notify takes the place of `esx_notify`, so `ESX.ShowNotification` and `xPlayer.showNotification` show here.

In `server.cfg`, **remove** this line:

```
ensure esx_notify
```

{% hint style="warning" %}
Keep the `esx_notify` **folder**, only remove the `ensure` line. ESX checks that the folder exists.\
Never run `esx_notify` and Striga Notify at the same time.
{% endhint %}

To turn this off, set `Config.Capture.Esx = false` in `editable/config.lua`.
{% endtab %}

{% tab title="QBCore" %}

1. Open `qb-core/client/functions.lua`
2. Find `function QBCore.Functions.Notify`
3. Add the **middle line** below right under it:

```lua
function QBCore.Functions.Notify(text, texttype, length, icon)
    if GetResourceState('striga-notify') == 'started' then return exports['striga-notify']:Notify(text, texttype, length, icon) end
    -- the rest stays as it is
```

This covers `QBCore.Functions.Notify`, `TriggerClientEvent('QBCore:Notify', ...)` and `exports['qb-core']:Notify`.
{% endtab %}

{% tab title="Qbox / ox\_lib" %}
Qbox shows its notifications with ox\_lib.

1. Open `ox_lib/resource/interface/client/notify.lua`
2. Find `function lib.notify(data)`
3. Add the **middle line** below right under it:

```lua
function lib.notify(data)
    if GetResourceState('striga-notify') == 'started' then return exports['striga-notify']:Notify(data) end
    -- the rest stays as it is
```

This covers `lib.notify`, `exports.qbx_core:Notify` and `TriggerClientEvent('ox_lib:notify', ...)` from every script.

{% hint style="success" %}
Running QBCore or ESX **with** ox\_lib? Do this step too, so scripts that use `lib.notify` show in the new design as well.
{% endhint %}
{% endtab %}
{% endtabs %}

{% hint style="info" %}
These one-line patches are safe. If Striga Notify is stopped, the original notifications come back by themselves.
{% endhint %}

***

## What is covered

After the step above, the normal functions of your framework show in the Striga Notify design. No change in your scripts needed:

| Framework | Client                                          | Server                                                              |
| --------- | ----------------------------------------------- | ------------------------------------------------------------------- |
| ESX       | `ESX.ShowNotification(text, type, duration)`    | `xPlayer.showNotification(text, type, duration)`                    |
| QBCore    | `QBCore.Functions.Notify(text, type, duration)` | `TriggerClientEvent('QBCore:Notify', source, text, type, duration)` |
| Qbox      | `exports.qbx_core:Notify(text, type, duration)` | `exports.qbx_core:Notify(source, text, type, duration)`             |
| ox\_lib   | `lib.notify({ ... })`                           | `TriggerClientEvent('ox_lib:notify', source, { ... })`              |

{% hint style="info" %}
The position a script asks for is ignored on purpose. All notifications show in one tidy list, at the position the player (or your config) picked.
{% endhint %}

{% content-ref url="/pages/7a60ggKkXjeQTSEMEv6O" %}
[Exports & Events](/docs/striga-notify/exports-and-events.md)
{% endcontent-ref %}


---

# 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://striga.gitbook.io/docs/striga-notify/integration.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.