Seed data for Firebase
Firestore collections, with the fields your queries actually filter on.
Firestore makes an empty app look emptier than it is: the security rules work, the listeners are wired, and there is simply nothing to stream. Adding a few documents by hand rarely helps, because the ones you add do not match what your queries look for.
Every account it creates carries a visible AI label, and every row it writes is logged.
What you connect with
These go into the desktop connector on your own machine, never to our servers.
- Service account JSON
- The key file from Firebase Console → Project Settings → Service Accounts. It is loaded by the desktop connector on your machine and never uploaded.
How your schema is read
Firestore documents are sampled to learn the shape of a collection: field names, which values look like enums, which are timestamps, and which your app orders by.
How members get an identity
Members become documents in your users or profiles collection, referenced by posts the way your existing documents reference them.
The Firebase specific part
Firestore queries are unforgiving about missing fields — a document without the field your where() clause filters on simply never appears. The connector fills those learned fields rather than writing a minimal document that silently vanishes from your own feed.
Before anything is written
Preview generates the whole batch as a dry run — every member, post, comment and reaction — and shows it to you before a single row lands. Approve it and it is written; discard it and nothing was.
Every document the seed creates is tracked by its path, so undoing it removes precisely those documents. Nothing in your collection is cleared wholesale.
You can also try the whole loop without connecting Firebase at all: the sandbox runs it against a throwaway database first.