> ## Documentation Index
> Fetch the complete documentation index at: https://docs.comify.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Create a Push Notification Template
> Build a push notification template in the Comify dashboard — title, body, action link, and image — with a live Android/iOS preview, then save it for campaigns and triggers.
Push notification templates are reusable messages delivered to a user's device. You set the title, body, tap action, and optional image, give the template a name, and save it. Campaigns and triggered communications then reference it by name.
This is a dashboard walkthrough. Screens are captured from **cloud.comify.io** → **Template Manager → Manage Templates → Push Notification**.
## Before you start: connect a provider
Open **Template Manager → Push Notification** to reach the **Push Notification Templates** list. It has a **push provider selector**, a **Status** filter, search, and **Create Template**.
If you see **"No Push Provider Connected,"** add a push provider (FCM, OneSignal, or Amazon SNS) before creating templates, then **select it from the provider selector**. The create form requires a connected provider. See [Push Providers](/channels/push/overview).
## Create a template
Click **Create Template** to open the push editor. Fill in the fields on the left; the **Notification Preview** on the right updates live.
The screens below are illustrative mockups, not live captures. Comify's push template editor sits behind a connected push provider (FCM, OneSignal, or Amazon SNS), and no provider is connected on the account used to build this documentation — see the warning above. Field names and layout are accurate; exact visual styling may differ slightly once you have a provider connected.
Enter a **Template name** (e.g. `cart_reengagement`) — the identifier used in campaigns and triggers.
An optional reference to tie the template to a campaign.
Choose the **Recipient field** — the payload field that holds the device token/target. Select a **Data Source** from the top bar first so recipient options appear.
Add targeting **Tags** in `label.value` format (e.g. `age_group.Young`). Use **Manage tags** to curate the list.
The bold heading of the notification (up to 200 characters). The toolbar offers **emoji, bold, italic, strikethrough,** and **Personalize** to insert `{{variables}}`.
```
Hey {{first_name}}, check this out!
```
The message text (up to 1024 characters), with the same formatting toolbar and **Personalize**. Devices truncate long text, so lead with the key point.
Where a tap goes — an in-app **deep link** or a **URL** (e.g. `https://example.com/page`). Use **Personalize** for per-recipient links.
Choose **No image**, **Image URL**, or **Upload image** for a rich notification.
## Preview across platforms
The **Notification Preview** shows an **Android** / **iOS** toggle and renders both the **collapsed** and **expanded** notification states, so you can confirm how the title, body, and image appear on each platform.
Keep titles short and front-load the value — the OS truncates anything too long, and the first few words are what the user sees on a locked screen.
## Save the template
Click **Save Template** in the top bar. The template appears in the Push Notification Templates list, where the **Status** filter helps you find it.
Test on real devices where possible — rendering, sound, and deep links behave differently across Android, iOS, and web.
## Best practices
Put the most important words first; the OS truncates the rest.
A notification that opens a relevant screen converts far better than one that just opens the app.
Use `{{variables}}` for names and context, but always have sensible fallbacks.
Too many pushes drive opt-outs. Reserve them for timely, relevant messages.
## Next steps
* Send it: [Create a campaign](/campaigns/overview)
* Other channels: [Email template](/platform/create_email_template) · [WhatsApp template](/platform/create_whatsapp_template)