Firebase

Rowsend reads your Firebase Authentication users through Google’s APIs with a service-account key. It can also add fields from a Firestore collection that holds one document per user.

1. Create a read-only service account

1. In Google Cloud, open your Firebase project’s IAM & Admin → Service accounts and create a service account.
2. Give it the Firebase Authentication Viewer role.
3. If you want fields from Firestore, also give it Cloud Datastore Viewer.
4. Under Keys, add a JSON key. Your browser downloads a file.

2. Connect

1. In Rowsend, open Contacts, click Connect a database and choose Firebase.
2. Click Choose key file and pick the downloaded file. The key stays on your computer, encrypted with your system keychain.
3. Rowsend reads each user’s email, name, sign-up and last sign-in times, and whether the email is verified.
4. To add profile fields, choose a Firestore collection whose documents are named by user id (uid), then tick the fields you want.
5. Click Test and connect.

Before connecting, Rowsend checks that the key can’t make changes. It asks Firebase to delete a user and a document that don’t exist. A read-only key gets “permission denied”; a key that could write gets “not found”, and Rowsend refuses it. Nothing changes either way.

What to know

• Firebase doesn’t record when a user last changed, so every sync reads every user. Large projects take longer to sync than SQL databases.
• email_verified and disabled become custom fields you can filter on, so you can leave out unverified or disabled accounts.
• Users with no email, such as phone-only sign-ins, are skipped.
• To change the Firestore fields later, open Project settings → Database and click Edit fields.