NOTIF_StorePushSubscription

Store user PushSubscription objects with endpoint and keys in Supabase.

Updated Mar 26, 2026

Search Tags:#database #Supabase #push notifications #secure data handling #subscription storage

Ready to run

npx skills add https://github.com/apakou/wolow --skill notif-storepushsubscription

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: NOTIF_StorePushSubscription
Source: https://github.com/apakou/wolow/tree/main/.claude/skills/NOTIF_StorePushSubscription
Command: npx skills add https://github.com/apakou/wolow --skill notif-storepushsubscription

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that user's PushSubscription objects are securely stored, allowing for targeted notifications to be sent to the correct endpoint later.

Core Features & Use Cases

Secure Storage: Persists push subscription details in a dedicated Supabase table.
Input Handling: Accepts userId and pushSubscription JSON object containing endpoint, keys.p256dh, keys.auth.
Output: Confirms successful storage or provides an error message.
Use Case: Useful for any application that requires reliable notification delivery, such as mobile apps or websites with push notification features.

Quick Start

Store a user's push subscription details by executing the NOTIF_StorePushSubscription skill with the userId and the pushSubscription JSON.

Frequently Asked Questions about NOTIF_StorePushSubscription

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I store a user's push subscription details in a database for later notifications?▼

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.

What data format does a PushSubscription object need for secure database storage?▼

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.

Can I use Supabase to securely manage web push notification subscriptions?▼

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.

What is the best way to save browser push notification endpoints for future server-side delivery?▼

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.

Does this push subscription storage method require any specific database setup?▼

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.

Why are my stored push subscription keys not working when sending notifications?▼

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.