# Push Notification Task

The **Push Notification Task** enables a Microflow or Process Flow to send **real‑time push notifications** to mobile applications.\
This task integrates ONEWEB with a **push‑notification hub**, allowing backend logic and workflows to notify users on **Android and iOS devices**.

<figure><img src="/files/iArBc8N1DGh0sShCDG3Q" alt=""><figcaption></figcaption></figure>

Push Notification Task is typically used as a **downstream action** that responds to events, workflow progress, or integration outcomes.

***

### Purpose of Push Notification Task

The Push Notification Task is designed to:

* Trigger push notifications from backend logic
* Send alerts and updates to mobile users
* Integrate workflows and system events with mobile UI

#### Typical Use Cases

* Approval or workflow notifications
* Status updates from long‑running processes
* Alerts generated from external system integrations

This task helps bridge backend execution with **mobile‑first user experiences**.

***

### Push Notification Task Configuration

The Push Notification Task Configuration Panel consists of **three tabs**, each serving a specific purpose in defining notification behavior and data contracts.

***

#### General Tab

The **General** tab contains basic task metadata used for identification and documentation:

* **Task Name**
* **Task ID** (system‑generated)
* **Description**

These properties help organize and maintain clarity within Microflows or Process Flows.

***

#### Business Object Tab

The **Business Object** tab defines the data contract for the Push Notification Task.

It is used to:

* Define the **input payload** sent to the notification hub
* Define any **output data** returned by the task (if applicable)

This ensures a clear and structured interface between the flow logic and the notification system.

***

#### Push Notification Tab

The **Push Notification** tab defines platform‑specific settings and connection details for sending notifications.

<figure><img src="/files/b6mywaRfjQXHsTmT68kk" alt=""><figcaption></figcaption></figure>

Both supported platforms can be configured within a **single Push Notification Task**, allowing unified management of mobile notifications.

✅ **Android and iOS platforms can be enabled simultaneously.**

***

#### **Android Platform Configuration**

When the Android platform is enabled, configuration is performed within the **Android Platform panel**.

Key aspects include:

* Platform connection settings
* Message priority configuration

**Priority behavior**

* **High** – Wakes sleeping devices if required
* **Normal** – Delivery may be delayed in Doze mode

<figure><img src="/files/9E2arRIxtu4MgPAqQLrP" alt=""><figcaption></figcaption></figure>

***

#### **iOS Platform Configuration**

When the iOS platform is enabled, configuration is performed in the **iOS Platform panel**.

* Environment‑specific credentials are required
* Certificates and private‑key files must be uploaded

The **Upload** button is used to upload certificate and private‑key files for each environment.

<figure><img src="/files/i1cz1oNZDfGb44DcruXg" alt=""><figcaption></figcaption></figure>

***

### Parameter Mapping

Both Android and iOS configuration panels provide an **Open Mapping Parameter** option.

Using parameter mapping, users can:

* Map Microflow or Process input parameters to notification payload fields
* Map output parameters (if returned) back to the flow

This allows push notifications to be **dynamic and data‑driven**, reflecting real‑time system or workflow state.

***

### Best Practices

To ensure secure and reliable push notification integration:

* Use **environment variables** for node URLs and credentials
* Never hard‑code server keys or certificates
* Keep notification payloads concise
* Use Push Notification Tasks as **downstream actions**, not core business logic
* Combine with **Error** or **Timer** events to handle failures gracefully

Following these practices improves reliability, security, and maintainability.

***

### Summary

The **Push Notification Task** enables ONEWEB applications to communicate with mobile users in real time from backend logic and workflows.

With this task, developers can:

* Send push notifications to **Android and iOS** applications
* Configure multiple platforms in a unified node
* Trigger notifications from **Microflows or Processes**
* Manage credentials and configuration per environment

Push Notification Task is a key capability for building **event‑driven, mobile‑enabled enterprise applications** using ONEWEB.


---

# 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.onewebstack.com/oneweb-platform-th/designer-reference/microflow-designer/push-notification-task.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.