> For the complete documentation index, see [llms.txt](https://assetstore.essentialkit.voxelbusters.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://assetstore.essentialkit.voxelbusters.com/features/notification-services/playmaker/use-cases/use-case-2-listen-and-respond.md).

# Listen and Respond to Notifications

## Goal

Handle notifications when they are received while the app is running or when the user taps a notification to open the app.

## Actions Required

| Action                                          | Purpose                        |
| ----------------------------------------------- | ------------------------------ |
| NotificationServicesOnNotificationReceived      | Listen for notification events |
| NotificationServicesGetReceivedNotificationInfo | Extract notification details   |

## Variables Needed

* notificationId (String)
* notificationTitle (String)
* notificationBody (String)
* wasLaunchedFromNotification (Bool)
* userInfoKeys/userInfoValues (String arrays, optional)

## Implementation Steps

### 1. State: ListenForNotifications

**Action:** NotificationServicesOnNotificationReceived

* **Outputs:**
  * notificationId → notificationId variable
  * title → notificationTitle
  * body → notificationBody
  * wasLaunchedFromNotification → wasLaunchedFromNotification
* **Events:**
  * receivedEvent → HandleNotification

**Note:** This is a persistent listener state - it remains active and fires the event each time a notification is received.

### 2. State: HandleNotification

**Logic:** Check wasLaunchedFromNotification

* If true: User tapped notification → Navigate to relevant content
* If false: Notification received in foreground → Show in-app banner

**Optional: Extract payload** Use `NotificationServicesGetReceivedNotificationInfo` to read `userInfoKeys` / `userInfoValues` (and other fields like subtitle/badge/sound).

### 3. State: NavigateToContent

Based on extracted payload (for example, `contentId`), navigate to the appropriate scene or UI element.

### 4. Return to ListenForNotifications

The listener continues to monitor for new notifications.

## Listener Pattern

```
State: ListenForNotifications (PERSISTENT)
  └─ Stays active, fires receivedEvent on each notification

OnEnter: Subscribe to notification events
OnExit: Unsubscribe from events
```

## Common Issues

* **Listener Not Firing**: Ensure the state with OnNotificationReceived is active when notification arrives
* **Multiple Triggers**: Each notification fires the event once; handle event properly to avoid duplicate actions
* **Background vs Foreground**: wasLaunchedFromNotification distinguishes between tapped (true) and foreground (false)
* **UserInfo Parsing**: Ensure JSON format is valid when building notifications

## Use Cases

**Foreground Notification:**

* App is open → Notification arrives → Show in-app toast/banner

**Background/Closed Tap:**

* App closed → User taps notification → App launches → Navigate directly to content

## Performance Tip

Keep the HandleNotification state logic simple and fast. Heavy operations should be deferred to avoid blocking the notification callback.


---

# 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://assetstore.essentialkit.voxelbusters.com/features/notification-services/playmaker/use-cases/use-case-2-listen-and-respond.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.