Add Push Notifications to Existing App

About this workflow

Integrate Firebase Cloud Messaging so users receive real push notifications and tokens are persisted in the backend.

What happens when you run it

1. 1
   Provide the cloud messaging service and keys needed for both client and server.

   Runs flow-push-notifications-1-create-firebase-project-obtain-credentials-43465b on Claude Sonnet 4.6
2. 2
   Install the messaging SDK and integrate the downloaded google‑services.json into the React Native project.

   Runs flow-push-notifications-2-add-fcm-client-library-and-configure-android-b-86bb08 on Claude Sonnet 4.6
3. 3
   Obtain the device’s FCM token and request user permission, then send the token to the backend for persistence.

   Runs flow-push-notifications-3-implement-permission-request-token-retrieval-o-54d6ee on Claude Sonnet 4.6
4. 4
   Store each user's FCM token in PostgreSQL so notifications can be targeted later.

   Runs flow-push-notifications-4-create-backend-endpoint-to-persist-tokens-e98234 on Claude Sonnet 4.6
5. 5
   Provide an endpoint that triggers an FCM push to a specific user’s devices.

   Runs flow-push-notifications-5-build-server-side-push-sender-service-e5a240 on Claude Sonnet 4.6
6. 6
   Provide a simple screen for admins to send a test push and verify end‑to‑end flow.

   Runs flow-push-notifications-6-add-in-app-test-notification-ui-095193 on Claude Sonnet 4.6
7. 7
   Confirm that a token is stored, the send endpoint works, and the device receives the push.

   Runs flow-push-notifications-7-validate-end-to-end-delivery-2f2df6 on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used