# Connect Firebase / Firestore to Code::Stats When **New Document Within a Firestore Collection** fires in [Firebase / Firestore](https://apiant.ai/connections/firebase-firestore), your agent runs **Get user** in [Code::Stats](https://apiant.ai/connections/code-stats). Describe the whole flow and it is built, tested on every scenario and kept running. Firebase / Firestore **1** trigger Firebase / Firestore **6** actions Code::Stats **1** action What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Firebase / Firestore and Code::Stats to do together? Give your AI client this address. `https://mcp.apiant.ai` Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser. ### Set it up in your client ### Claude Code Run this in the directory you want to work in. `claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### Claude, web and desktop Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Cursor Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Codex and the ChatGPT desktop app Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### Any other MCP client Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) Example flows ## What Firebase / Firestore can start in Code::Stats - When **New Document Within a Firestore Collection** in Firebase / Firestore then **Get user** in Code::Stats Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships. Everything your agent can do with Firebase / Firestore and Code::Stats ## Triggers and actions 1 trigger · 7 actions - Trigger **New Document Within a Firestore Collection** Triggers when a new document is added to a Cloud Firestore collection. - Action **Create Cloud Firestore Document** Creates a new document within a Cloud Firestore collection. - Action **Delete Cloud Firestore Document** Deletes a Firestore document by its collection path and document ID. - Action **Find Cloud Firestore Document** Finds a document using a Structured Query within a collection. - Action **Get Cloud Firestore Document** Returns one Firestore document by its collection path and document ID. - Action **Run Cloud Firestore Query** Returns the Firestore documents in a collection that match a field filter. - Action **Update Cloud Firestore Document** Updates the given fields on an existing Firestore document. - Action **Get user** Retrieve a public user's profile (total XP, new XP in last 12h, per-machine, per-language and per-date XP). ## Each app on its own - [ **Firebase / Firestore** Firebase Realtime Database and Google Cloud Firestore are flexible databases that give you the ability to...](https://apiant.ai/connections/firebase-firestore) - [ **Code::Stats** Automatic time tracking for programmers](https://apiant.ai/connections/code-stats) Reviews ## What our customers say ## More from Firebase / Firestore - [ **Firebase / Firestore to Google Cloud Text-to-Speech** Cloud API that converts written text into natural-sounding spoken audio in multiple languages and voices.](https://apiant.ai/connect/firebase-firestore-to-google-cloud-text-to-speech) - [ **Firebase / Firestore to HubSpot** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/firebase-firestore-to-hubspot) - [ **Firebase / Firestore to Salesforce** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/firebase-firestore-to-salesforce) - [ **Firebase / Firestore to Slack** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/firebase-firestore-to-slack) - [ **Firebase / Firestore to Google Sheets** Google Sheets](https://apiant.ai/connect/firebase-firestore-to-google-sheets) - [ **Firebase / Firestore to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/firebase-firestore-to-gmail) ## More into Code::Stats - [ **HubSpot to Code::Stats** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-code-stats) - [ **Salesforce to Code::Stats** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-code-stats) - [ **Slack to Code::Stats** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-code-stats) - [ **Google Sheets to Code::Stats** Google Sheets](https://apiant.ai/connect/google-sheets-to-code-stats) - [ **Gmail to Code::Stats** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-code-stats) - [ **Google Calendar to Code::Stats** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-code-stats) Questions ## Firebase / Firestore and Code::Stats, answered ### ### What can start an automation from Firebase / Firestore? Any of Firebase / Firestore's 1 trigger in the catalog, including New Document Within a Firestore Collection. Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Code::Stats when something happens in Firebase / Firestore? Any of Code::Stats's 1 action, including Get user. Your agent maps the data both ways and tests every scenario before it ships. ### ### Can it also run from Code::Stats to Firebase / Firestore? Code::Stats has no triggers in the catalog today, so automations start in Firebase / Firestore. If you need the other direction, ask: your agent reads Code::Stats's API documentation and adds it. ### ### Do I have to build a connector for Firebase / Firestore or Code::Stats? No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running. ### ### What happens when something fails? Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships. ### ### Is there a free plan? Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.