Firebase Admin StrawberryDocuments checked against firebase realtime database records, in one pass
Hand a companion the outcome. It reads the Firebase Admin documents, does the 6-operation version of the job, and stops for your click on anything that changes a record.
Open the document. Check it against something else. Write the change. Move to the next one. That is the Firebase Admin afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a document until you approve it.
What it can do is exactly what Firebase Admin exposes to an account you authorise and nothing beyond it: 6 operations, 3 reads and 3 writes. In practice that means it can update a document, create firebase realtime database record and create a document, and work across the documents, firebase realtime database records and save events.
The Firebase Admin API stops at Firebase Admin. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Where do the documents come from?
3 of the 6 operations are reads.
Your account, not a guess at it: a companion can save event to firestore, list documents and get a document, and the full list below is the whole list, with nothing inferred from Firebase Admin's documentation.
The documents are what most of this inventory is about, alongside the firebase realtime database records. A companion can hold all 6 of these operations and forty open tabs in the same pass, which is how an afternoon of Firebase Admin admin becomes a queue you review.
- Save Event to Firestore
- List Documents
- Get Document
What happens before it can update document?
All 3 write operations wait for you.
A companion can update a document, create firebase realtime database record and create a document, and each one is staged on an approval card first: you see the document, the field and the new value before it lands in Firebase Admin.
Nothing in Firebase Admin is sent, changed or deleted on your behalf without that click, and a rejected card leaves the document exactly as it was. The gate is the same one on every surface, described at security.
- Update Document
- Create Firebase Realtime Database Record
- Create Document
What does the recurring documents pass look like?
Yes.
Saved as a routine, the Firebase Admin documents pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Firebase Admin documents sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents