How to Delete Data from Your FlutterFlow Database

Select the Delete button widget on your list item. Open the Action Flow editor. As the first action, add a Show Alert Dialog action: set the title to 'Delete Item', the message to 'This cannot be undone. Are you sure?', the confirm button text to 'Delete' with a red color, and the cancel button text to 'Cancel'. Only continue the flow if the user confirms. After the dialog confirmation action, add a Backend Call action → set the Call Type to Delete Document. In the Document Reference field, bind to the document reference from your Backend Query (for list items, this is typically the document reference of the current loop item — accessible via the Generate Dynamic Children binding menu). After the delete action, add a Show Snackbar action with text 'Deleted successfully'. The list will automatically update because the Backend Query re-runs.

If your Firestore document has subcollections (e.g., a posts document with a comments subcollection), you cannot use the built-in Delete Document action directly — orphaned subcollection documents remain even after the parent is gone, still consuming storage and reads. Create a Custom Action named deleteDocWithSubcollections. Import firebase_cloud_firestore. Write: final docRef = FirebaseFirestore.instance.doc(docPath); final commentsSnap = await docRef.collection('comments').get(); for (final comment in commentsSnap.docs) { await comment.reference.delete(); } await docRef.delete();. Pass the document path as a String parameter. Call this Custom Action from the Action Flow instead of the built-in Delete Document action. This ensures all comments are deleted before the parent post.

For deleting all items matching a condition (e.g., delete all notifications older than 30 days, or delete all selected items in a multi-select list), create a Custom Action named batchDelete. Import firebase_cloud_firestore. Use WriteBatch for up to 500 documents: final batch = FirebaseFirestore.instance.batch(); for (final docRef in docRefs) { batch.delete(docRef); } await batch.commit();. Pass a List<DocumentReference> as the parameter. In FlutterFlow, use a multi-select list (checkboxes bound to App State selectedIds) and on the Delete Selected button, call batchDelete passing the selected document references. WriteBatch is atomic — all deletions succeed or all fail together — which prevents partial deletes that leave the UI in an inconsistent state.

For Supabase-backed FlutterFlow projects, deleting a row uses the Backend Call action configured differently. In the Action Flow, add Backend Call → Supabase row delete. Select the table, then set the matching condition — typically the id column equals the row ID from your current list item. The Supabase delete follows the same confirmation dialog pattern as Firestore (add the Show Alert Dialog action first). Ensure your Supabase Row Level Security (RLS) policy allows delete for the authenticated user — a common mistake is enabling RLS without adding a delete policy, which silently blocks the operation without a clear error. Test in the Supabase SQL editor: DELETE FROM table WHERE id = 'test-id' while authenticated as a test user to verify the RLS policy works.

A Snackbar with an Undo button dramatically reduces support requests from users who accidentally delete data. Instead of deleting immediately, implement a soft delete: add an isDeleted Boolean field to your Firestore documents (default false). On the 'Delete' action, update isDeleted to true and hide the item from the list by filtering the Backend Query (where isDeleted == false). Show a Snackbar with an Undo button — if tapped within 5 seconds, call Update Document to set isDeleted back to false. After the Snackbar dismisses, call a Cloud Function or scheduled task to permanently delete documents where isDeleted == true and deletedAt timestamp is older than 24 hours. This pattern is used by Gmail, Slack, and most productivity apps because it drastically reduces complaints about accidental deletions.