NOTIF_StorePushSubscription

To store push subscription details, you pass the user's userId and the pushSubscription JSON object to this Skill, which securely persists the endpoint, keys.p256dh, and keys.auth in a Supabase table for future notification delivery.

A PushSubscription object for secure database storage requires a JSON structure containing the endpoint URL, and cryptographic keys including keys.p256dh and keys.auth, alongside a userId to associate the subscription with the correct user.

Yes, you can use Supabase to securely manage web push notification subscriptions by storing the PushSubscription JSON objects in a dedicated table, allowing targeted notifications to be sent to specific user endpoints later.

The best way to save browser push notification endpoints is to store the full PushSubscription JSON in a secure database like Supabase, linking it to the userId so your server-side logic can retrieve and send targeted notifications later.

This push subscription storage method requires a Supabase database setup with a dedicated table to persist the subscription details securely, but it does not list any additional external dependencies for the core storage logic.

If stored push subscription keys are not working, verify that the complete pushSubscription JSON, specifically the keys.p256dh and keys.auth values, was correctly passed and persisted in the Supabase table alongside the accurate userId.