> For the complete documentation index, see [llms.txt](https://docs.momentum.sh/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.momentum.sh/getting-started/installation/cloud-integrations/firebase.md).

# Firebase

You will need a firebase project, add one from here : [https://console.firebase.google.com/](https://console.firebase.google.com/u/0/)

Once a project is created, do the following.\
\
1\. Click on Project overview from the sidebar.\
2\. Open Service accounts tab.\
3\. You will see the option to generate a new private key in the firebase admin sdk sub-section. Click on that.\
4\. Read the warning, and then generate the key. Rename the downloaded key to - firebase\_service\_account.json and move it to server folder in the root of momentum source code. \\

{% hint style="info" %}
Note: The file name 'firebase\_service\_account.json' is already part of .gitignore and should be safe to use. It never goes on git. But in case you loose it, you'll need a new one. So keep it secure and safe. (Repeating the warning that google gave you during key generation)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.momentum.sh/getting-started/installation/cloud-integrations/firebase.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.