> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/push-notification.md). # Push Notification The **Push Notification** action sends a mobile push notification to selected members of your workspace through the Datacake app. It sits alongside the **Email**, **SMS**, and **Webhook** actions in the New Rule Engine and is a good fit when you want an alert to reach people instantly on their phone — without managing a list of email addresses or spending SMS credits. Use it when: * You want on-call colleagues to be notified the moment a device goes offline or a threshold is crossed. * Your recipients already use the Datacake mobile app and prefer a push over email/SMS. ## Prerequisites Before you can set up a Push Notification action, make sure that: * **Recipients have the Datacake mobile app installed and are signed in.** A member can only receive a push once they have an active, signed-in app for the relevant branding. Members without the app can still be selected — they simply start receiving notifications once they install it and sign in. * **You have the `rules` permission** in the workspace. This is the same permission required to edit rules — no separate "members" permission is needed to pick recipients. * **Your rule's branding supports mobile push.** The action is only offered under the default Datacake branding, or under a white-label brand that has the **Mobile Push** integration enabled. See [#i-dont-see-the-push-notification-option](#i-dont-see-the-push-notification-option "mention") below. ## Setting up the action This walkthrough sets up a rule that notifies your team when a device goes offline. 1. **Create or open a rule** in the New Rule Engine and configure its trigger and conditions as usual. For an offline alert, use the **Device Goes Offline** trigger. 2. Under **Configure Actions**, click **Add Action**, open the **Notifications** category, and choose the **Push Notification** card.

The Push Notification card in the Add Action picker, under the Notifications category.

3. **Pick your recipients.** Click the **Recipients** field and search the list of workspace members by name or email. Select everyone who should receive the push. At least one recipient is required to save the action.

The recipient picker lists workspace members; search by name or email and tick everyone who should receive the push.

4. **Write the Title and Message.** Both fields come pre-filled with a sensible default that already uses variables, for example a title of `Device {{ triggering_device["name"] }} activated rule {{ rule["name"] }}`. Edit them to suit your alert. You can insert variables such as the device name or rule name through the variable autocomplete — start typing `triggering_device...` to see the available fields. {% hint style="info" %} Both **Title** and **Message** are required and are limited to **255 characters** each. A live character counter is shown beneath each field and turns red when you go over the limit; saving is blocked until you shorten the text. {% endhint %}

The Push Notification action editor, with Recipients, Title, and Message fields and the per-field character counter.

5. Adjust the **Advanced Settings** and **Time Restrictions** if needed — these behave exactly like the other actions (see [Advanced Settings](/portal/rule-engine/new-rule-engine/actions/advanced-settings.md) and [Time Restrictions](/portal/rule-engine/new-rule-engine/time-restrictions.md)). 6. **Save** the action and the rule. ### Using variables in the Title and Message The Title and Message support the same Jinja-style placeholders as the Email and Webhook actions. For example: ``` Device {{ triggering_device["name"] }} has gone offline. ``` For the full list of available variables and advanced templating, see: {% content-ref url="/pages/5siE7WEl5v6Yo4cB6Ctp" %} [Advanced Rule Engine E-Mail and Webhook Templates](/portal/rule-engine/new-rule-engine/advanced-rule-engine-e-mail-and-webhook-templates.md) {% endcontent-ref %} ## Understanding the recipient list Unlike Email and SMS, where you type free-text addresses or phone numbers, the Push Notification action lets you pick **actual workspace members**. Each member is shown with their name and email. Members who **cannot currently receive a push** — because they have no Datacake app installed, or no registered device for the relevant brand — are shown **greyed out with an amber warning icon**. They are **still selectable**: hovering the icon explains that the member has not installed the app yet and won't receive a push until they do. Once they install the app and sign in, they start receiving the notifications automatically.

A reachable member (top) and an unreachable member shown greyed out with an amber warning icon (bottom). Unreachable members can still be selected.

{% hint style="info" %} This lets you set up the rule **before** your colleagues have installed the app. If every selected recipient is currently unreachable, a soft amber warning appears — but the rule still saves. {% endhint %} ### Recipients stay valid over time If a selected member later leaves the workspace, the rule remains valid — that person is simply dropped from the recipients automatically. There is no error and the rule does not break. ## Troubleshooting ### I don't see the Push Notification option The Push Notification card is only shown when the rule's **branding** supports mobile push: * **Default Datacake branding** → push is always available. * **A white-label brand** → push is only available if that brand has the **Mobile Push** integration enabled. If it isn't, the card is hidden. This is the most common reason the option is missing. If your rule uses a white-label brand without Mobile Push, either switch the rule's branding to one that supports push, or enable the Mobile Push integration for that brand. If a push action already exists under an unsupported brand, the editor shows a warning that the action will not fire.

Under a white-label brand without Mobile Push, the Add Action picker only offers E-Mail, SMS, and Webhook — the Push Notification card is hidden.

{% content-ref url="/pages/-MIu\_y73tt\_jnbJeiIMZ" %} [White Label](/organization/white-label.md) {% endcontent-ref %} ### A recipient isn't getting notifications The most likely cause is that the member is currently **unreachable** — they have not installed the Datacake mobile app, are not signed in, or have no active registered device for the rule's brand. In the recipient picker they appear greyed out with an amber warning icon. Ask them to install the app and sign in; they will then start receiving the notifications. ### Saving is blocked * **Title or Message over 255 characters** — the character counter turns red and saving is blocked. Shorten the text. * **No recipients selected** — at least one recipient is required to save the action. --- # 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://docs.datacake.de/portal/rule-engine/new-rule-engine/actions/push-notification.md?ask=&goal= ``` `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.