# Exports // Triggers

| Variable | Type              | Example                                 |
| -------- | ----------------- | --------------------------------------- |
| type     | string            | info, error, success, twitter, dispatch |
| message  | string            | Test message                            |
| header   | string or boolean | 10-13a, Some text or false              |
| time     | number            | 20000                                   |

## Lua code examples for Client Side

```lua
exports["sfnotify"]:notify(type, message, header, time)

-- examples, default time is 10000
exports["sfnotify"]:notify("info", "test message")
exports["sfnotify"]:notify("info", "test message", false, 5000)
exports["sfnotify"]:notify("info", "test message", "Notification")
```

```lua
TriggerEvent("sfnotify", "dispatch", "test message", "10-13a")
```

```lua
TriggerEvent("sfnotify:cinematic", true) -- if set true notifications do not show
TriggerEvent("sfnotify:cinematic", false) -- if set false notifications show up
```

## Lua code examples for Server Side

```lua
TriggerClientEvent("sfnotify", source, "info", "test message")
```


---

# Agent Instructions: 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:

```
GET https://docs.scriptsfivem.com/resources/sfnotify/exports-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
