> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackone.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Firebase with Service Account – StackOne Hub

> Link a Firebase account in the StackOne Hub using Service Account. End-user guide to authorize the integration and start using Firebase actions.

> [!WARNING]
>
> You need permission to create service accounts, grant roles and create keys in the Google Cloud project, such as the Service Account Admin, Service Account Key Admin and Project IAM Admin roles.

## Creating a service account key

Work in the Google Cloud project behind the Firebase project you are connecting. Every Firebase project is also a Google Cloud project and shares its IAM. The roles you grant the service account decide which actions work.

**1. Enable the required APIs**

Sign in to the [Google Cloud Console](https://console.cloud.google.com/) and select the project. Turn on the Firebase Management API, Identity Toolkit API, Cloud Firestore API and Firebase Cloud Messaging API.

<ul>
  <li>For each API, search for it in **Search (/) for resources, docs, products, and more** and open it.</li>
  <li>Click **Enable**.</li>
  <li>If the page shows **Manage** and **API Enabled**, the API is already on.</li>
</ul>

**2. Create the service account**

Open **IAM & Admin** > **Service Accounts**.

<ul>
  <li>Click **Create service account**.</li>
  <li>**Service account name**: `StackOne Integration`</li>
  <li>Click **Create and continue**.</li>
</ul>

![Create service account form with the Service account name field and the Create and continue button highlighted.](https://mintcdn.com/stackone-60/7nMIoSBferDNXmwJ/connectors/firebase/images/service-account-config-create-account.png?fit=max\&auto=format\&n=7nMIoSBferDNXmwJ\&q=85\&s=392a4c9ffd9145aed59c3cbb90c0fc37)

**3. Grant the roles**

Under **Permissions (optional)**, add the role that matches what this connection will do. One role is enough for each level of access.

<ul>
  <li>Click **Select a role**.</li>
  <li>**Firebase Viewer** covers every read in this connector, including projects, apps and their configuration, Authentication users and Firestore documents. It grants no writes.</li>
  <li>**Firebase Admin** covers all of that plus creating, changing, deleting and undeleting projects, apps and SHA certificates, managing Authentication users and Firestore documents, and sending Cloud Messaging messages. Nothing else needs to be added alongside it.</li>
  <li>To stay narrower than Firebase Admin, add **Firebase Authentication Admin** for Authentication users, **Cloud Datastore User** for Firestore documents and **Firebase Cloud Messaging API Admin** for sending messages, choosing only the ones you need.</li>
  <li>Click **Continue**.</li>
  <li>Click **Done**.</li>
  <li>New roles can take a few minutes to become active.</li>
</ul>

![Permissions step of the Create service account form with the selected role and the Continue button highlighted.](https://mintcdn.com/stackone-60/7nMIoSBferDNXmwJ/connectors/firebase/images/service-account-config-grant-role.png?fit=max\&auto=format\&n=7nMIoSBferDNXmwJ\&q=85\&s=a975e55e826a7b2dae1df616fcd9613f)

**4. Grant the roles on every Firebase project you will reach**

Each action takes its Firebase project as an input, so one connection can reach several projects. A service account has no access to a Firebase project just because it was created in another one, and a project it has not been granted on is invisible to it rather than merely restricted, so calls fail with a permission error.

<ul>
  <li>For each Firebase project this connection should reach, open **IAM & Admin** > **IAM** on that project.</li>
  <li>Click **Grant access**.</li>
  <li>**New principals**: the service account's email address, which ends in `iam.gserviceaccount.com`.</li>
  <li>Assign the same role you chose above, then click **Save**.</li>
  <li>Skip this if the connection only reaches the project the service account was created in, where the roles above already apply.</li>
</ul>

**5. Create the JSON key**

In **Service Accounts**, click the email of the new service account and open the **Keys** tab.

<ul>
  <li>Click **Add key**.</li>
  <li>Select **Create new key**.</li>
  <li>**Key type**: **JSON**</li>
  <li>Click **Create**. The key file downloads once, and Google can't recover it if it is lost.</li>
  <li>If your organization blocks key creation with an organization policy, ask an organization policy administrator to allow it for this project.</li>
</ul>

![Create private key dialog with the JSON key type and the Create button highlighted.](https://mintcdn.com/stackone-60/7nMIoSBferDNXmwJ/connectors/firebase/images/service-account-config-create-key.png?fit=max\&auto=format\&n=7nMIoSBferDNXmwJ\&q=85\&s=6e8e215f53460e7a9a1c13e03d1831dd)

## Entering the key

Open the downloaded `.json` key file in a text editor. The whole file, including the outer braces, is the key.

<ul>
  <li>Copy the **Service Account Key (JSON)** across.</li>
  <li>Actions take the Firebase project as an input rather than a connection setting. Use the `project_id` value from the key file, or the ID of another Firebase project the service account has roles on.</li>
</ul>

## Link the Account

**1. Connect**

<ul>
  <li>Click **Connect**.</li>
  <li>If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider's authorization flow.</li>
  <li>Once authorization is successful, you will see a confirmation popup.</li>
</ul>

**2. Use Actions**

Connect an AI platform to the linked account's actions. See [AI Platforms](https://docs.stackone.com/ai-platforms/overview.md).

Other ways to call actions are listed in [Protocols & SDKs](https://docs.stackone.com/connect/protocols-and-sdks.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.