Skip to content
ClickRuntime

Automate Firebase

Keep an eye on your Firebase project without opening the console: new Firestore documents, fresh Realtime Database entries, yesterday's sign-ups and nightly Firestore exports. Each check reads your project on a schedule and sends you what changed. Tell your assistant which collection or path to watch, review the plan it shows you, and from then on it runs by itself.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 5 minutes, check my Firestore 'orders' collection for documents newer than the last one by createdAt and post each new order's customer, total and status to #orders in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Firebase

New orders and messages reported within minutes, a morning count of what your app created, a list of who signed up, and a Firestore backup that tells you when it did not finish. These are ready-made starting points. Anything else you can describe works too.
Every 5 minutes

Hear about every new Firestore document

A few minutes after a document lands in the collection you pick, you get its key fields in Slack or email.

See how it works
Daily

Get a morning count of new users and orders

Each morning you see how many documents yesterday added to each collection, next to the day before.

See how it works
Every 5 minutes

Get new Realtime Database entries by email

New children under a database path reach your inbox shortly after they are written.

See how it works
Daily

Export Firestore to Cloud Storage nightly

Your Firestore data is exported to a dated folder each night, and you are told if an export fails.

See how it works
Daily

See yesterday's new sign-ups each morning

A private email lists the accounts created in the last 24 hours, with how each person signed in and the running total.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Firebase, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Firebase automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Firebase should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every hour, check my Firestore orders collection for documents stuck in pending status for more than 30 minutes and flag them.

Every 15 minutes, add new Firestore user documents to my Google Sheet with signup date and plan.

Every day, read new entries in my Firestore feedback collection, have AI pick out bug reports, create a Linear issue for each, and post the count to Slack.

Beyond chat

Have Firebase work when you're not in the chat

Connecting Firebase to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Firebase

Firebase connects with a service account key from your own project, so no Google sign-in screen is involved. Use a service account with only the roles your automations need rather than the broad default Admin SDK account.

Firebase

Developer / Backend (BaaS)

  1. In the Firebase console, open Project settings and go to the Service accounts tab.
  2. Click Generate New Private Key, then Generate Key, to download the JSON key file. For tighter access, create a narrower service account in Google Cloud IAM and generate its key instead.
  3. Give that account the roles your automations need, for example Cloud Datastore Viewer for reading Firestore or Firebase Authentication Viewer for sign-ups.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the contents of the JSON key as a secret for Firebase.

Good to know

Firebase limits that affect automations

  • The default Admin SDK service account has wide rights across the project, so a dedicated account with read-only roles is the safer choice for reporting.
  • Some Google Cloud organizations block key creation with the iam.disableServiceAccountKeyCreation policy; an admin has to allow it before you can download a key.
  • Access tokens made from the key expire after an hour and are renewed automatically on each run, so you never paste a new one.
  • Firestore exports to Cloud Storage need the Blaze plan, and the target bucket cannot use Requester Pays.
  • New-document and new-entry alerts work by checking every few minutes, not by a push from Firebase, so expect a short delay.

FAQ

Questions about automating Firebase

Which parts of Firebase can ClickRuntime reach?
Whatever the service account's roles allow. The ready automations read Firestore collections, Realtime Database paths and Firebase Authentication users, and the backup one starts a Firestore export into a bucket you name.
Why a service account key instead of signing in with Google?
The key comes from your own project, so you decide its roles and can delete it from Google Cloud whenever you like. No consent screen or app review is involved.
How fast do I hear about a new Firestore document?
Within about five minutes. The automation queries the collection for documents newer than the last one it saw, so it needs a timestamp field such as createdAt to sort by.
Is it safe to email sign-up details?
User emails are personal data, so the sign-up list is meant to go to the project owner only, not to a shared channel or a wide mailing list.
Is AI involved in these Firebase automations?
Not in the ready ones; counts, alerts and backups are plain reads and exports. If you ask for a written summary, it uses the AI included in your ClickRuntime plan, with no separate AI key.
Is this a Firebase connector for ChatGPT or Claude?
Not for chatting with Firebase data. A chat connector lets your assistant read and change Firebase while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Firebase event.

Related pages

Keep exploring

Tell your assistant what Firebase should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude