You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Replace `<projectID>` with your GCP or Firebase project.
261
-
* If you want to test a different Cloud Function, update `sendUserPushNotificationsTrigger` too.
260
+
- Replace `<projectID>` with your GCP or Firebase project.
261
+
- If you want to test a different Cloud Function, update `sendUserPushNotificationsTrigger` too.
262
262
2. Paste the following JSON into the <kbd>Configure Triggering Event</kbd> text area.
263
263
```json
264
264
{
@@ -275,9 +275,9 @@ Here's how to test FlutterFlow's `sendUserPushNotificationsTrigger` function in
275
275
}
276
276
```
277
277
3. In the `name` property:
278
-
* Replace `<projectID>` with your GCP or Firebase project.
279
-
* Replace `<documentID>` with the ID of the document. This document must already exist in Firestore.
280
-
* If you're testing another function than `sendUserPushNotificationsTrigger`, update `ff_user_push_notifications` with the collection where the document is written.
278
+
- Replace `<projectID>` with your GCP or Firebase project.
279
+
- Replace `<documentID>` with the ID of the document. This document must already exist in Firestore.
280
+
- If you're testing another function than `sendUserPushNotificationsTrigger`, update `ff_user_push_notifications` with the collection where the document is written.
281
281
4. Update the values under the `fields` property for the message you want to send.
282
282
\
283
283
The `fields` in the example above are for FlutterFlow's built-in `sendUserPushNotificationsTrigger` function. If you're testing a different Cloud Function, you will need to update the `fields` for the code in *that* function.
0 commit comments