How do you notify the recipient of a chat message in Adalo?
Trigger a push notification to the intended recipient from available screen data, or create an in-app notification record related to that user.
Add a Trigger Notification action to the chat Send button and select the intended recipient from Available Screen Data or a user filter—not the Logged-in User who is sending the message. For an in-app inbox, create a Notification record related to that recipient and filter the recipient’s list accordingly.
Use the conversation’s other participant as the notification recipient. Push notifications use Adalo’s Trigger Notification action; an in-app inbox stores recipient-related Notification records and filters them for the logged-in user.
The intended outcome
A chat send action targets the other participant with a push notification or creates a recipient-scoped in-app alert.
Requirements
- A chat screen with the intended recipient available as screen data
- Notification permission configured for push alerts
- A Notifications collection for an in-app inbox
Step by step
- 01
Keep the recipient in screen context
Make the other chat participant available to the chat screen through the conversation or message relationship before configuring the action.
- 02
Add the push action
Add Trigger Notification to the Send button and choose the intended recipient from Available Screen Data or a user filter. Do not target the Logged-in User who triggers the action.
- 03
Configure the notification
Set the title and body, and choose a destination screen for native builds. PWA notifications always return to the app’s Home Navigation screen.
- 04
Create an in-app record
For an in-app inbox, create a Notifications collection with title, message, read state, and a many-to-one Recipient relationship to Users.
- 05
Filter and test both states
Filter the notification list to the logged-in recipient, then test sender, recipient, permission-denied, and inactive-user cases.
The underlying logic
Push notifications target users selected from available data or a filter; the user who triggers the notification cannot receive that same notification.
In-app notifications are ordinary records whose Recipient relationship controls which user’s filtered list can display them.
Data model
| Collection | Important properties | Relationships |
|---|---|---|
| Notifications | Title, message, read state, created date | Belongs to one recipient User and optionally one Conversation or Message |
What still needs checking?
- This is a forum-native answer with no original Adalocado video. Current official notification documentation corrects the ambiguous recipient wording in the accepted reply.
Common failure modes
The sender is selected as recipient
Choose the other chat participant from Available Screen Data or a user filter rather than the Logged-in User.
No push notification arrives
Confirm the recipient is logged in, recently active, has the app installed, and granted notification permission.
Every user sees the in-app alert
Relate the record to one Recipient and filter the list where Recipient equals Logged-in User.
Testing checklist
0 of 7 checked on this device
Current limitations
- Adalocado has not reproduced this complete chat workflow in a current builder project.
- Push delivery requires installation, login, recent activity, and notification permission; PWA target-screen behavior differs from native builds.
Current evidence screenshots have not yet been added. Treat the guidance as documented or legacy material according to the status shown above.
What the Adalo community is reporting
These are concise editorial summaries of public forum posts—not endorsements or independently reproduced results.
Chat message notification
The accepted answer proposes push and in-app notification paths for chat messages.
Boundary: Its 'Current User' wording is ambiguous, so the published guidance follows current official recipient-selection rules instead.
mizuhase (question) and Ali-Bazzi (accepted answer) · March 2026Sources and status
This page was last reviewed on Aug 14, 2026. Its current status is Documented from current sources.
Verification owner: Automatically organized from an accepted forum answer; monitored for corrections. Next review: Oct 14, 2026.
Changelog
Automatically posted from a solved Adalo forum topic; corrections are monitored on the live site.
Report this answer.
Forum answers post automatically. If a step is wrong, outdated, unclear, or missing an important boundary, send the exact correction and the editor will check the live page.
Report a problemDid this solve your problem?
Never deal with an Adalo problem again.
Rehost becomes the monthly team behind your app. Fixes, releases, integrations, and ongoing changes have an owner.
See monthly managementBring us the messy version.
Describe what you expected, what happened instead, and what you already tried.
Ask Adalocado
