Budget: $50 (success-based, one-time payment) Deadline: Must be completed within 3 days after offer acceptance Important Note After the contract starts, I will grant you editor access to Adalo, and admin access to Make and OneSignal. ( In compliance with Freelancer.com rules, no email exchange is required.) Current Situation ・The Make scenario is already built (Adalo → Make → OneSignal). ・Requests are successfully reaching OneSignal (HTTP 200, Success in Make history). ・However, no push notifications are delivered on iOS or Android devices. ・The issue is clear: ・External ID is empty in OneSignal Users. ・Push subscription is missing (no “Push / Subscribed” icon). ・In short, OneSignal receives the notification requests, but doesn’t know which user/device to deliver to. What Needs to Be Done Step 1 — Fix user registration ・Implement external_id binding: Adalo User.id must be registered in OneSignal. ・Ensure the device shows Push / Subscribed in OneSignal → Users. Step 2 — Confirm delivery with instant send ・Run an immediate notification (no send_after). ・Verify: ・Make → OneSignal returns HTTP 200. ・OneSignal → Messages shows “Delivered”. ・Test device receives the notification. Step 3 — Add 10-hour delay ・Configure send_after in ISO8601 format: {{ formatDate(addHours(now; 10); "YYYY-MM-DD'T'HH:mm:ssXXX") }} ・First test with a 3-minute delay (0.05h) to validate scheduling, then switch to 10 hours. Step 4 — Scenario hardening ・Add filters (only send when status = queued and onesignal_id is empty). ・Write back OneSignal response into Adalo (status = scheduled, onesignal_id = ...). ・Optional: use collapse_id to prevent duplicates. Step 5 — App cleanup ・Remove Adalo’s native Trigger Notification action to avoid conflicts. ・Ensure message creation always saves to_user_id (receiver). Deliverables * A fully working system where sending a message in Adalo results in a 10-hour delayed push notification, reliably delivered on both iOS and Android. * At least one successful test case (screenshot/log).