Cloud Functions setup in Firebase - Step-by-Step Execution

Process Flow - Cloud Functions setup

Install Firebase CLI

↓

Initialize Firebase Project

↓

Write Cloud Function Code

↓

Deploy Functions to Cloud

↓

Function Ready to Trigger

This flow shows the steps to set up Firebase Cloud Functions from installation to deployment and readiness.

Execution Sample

Firebase

firebase init functions
cd functions
npm install
cd ..
firebase deploy --only functions

This sequence initializes functions, installs dependencies, and deploys them to Firebase.

Process Table

Step	Action	Command/Code	Result
1	Install Firebase CLI	npm install -g firebase-tools	Firebase CLI installed globally
2	Initialize Firebase Project	firebase init functions	Functions folder created with config files
3	Write Cloud Function Code	Edit index.js with function code	Function code ready in functions folder
4	Install dependencies	npm install	Node modules installed in functions folder
5	Deploy Functions	firebase deploy --only functions	Functions deployed to Firebase cloud
6	Function Ready	Trigger function via HTTP or event	Function executes in cloud environment
7	Exit	No further commands	Setup complete, functions ready to use

💡 Setup ends after functions are deployed and ready to trigger

Status Tracker

Variable	Start	After Step 2	After Step 4	After Step 5	Final
Firebase CLI	Not installed	Installed	Installed	Installed	Installed
Functions folder	Not present	Created	Created	Created	Created
Function code	Empty	Template created	Edited with code	Edited with code	Deployed
Dependencies	None	None	Installed	Installed	Installed
Deployment status	Not deployed	Not deployed	Not deployed	Deployed	Deployed

Key Moments - 3 Insights

Why do we run 'npm install' inside the functions folder?

Because the functions folder contains the code and dependencies for Cloud Functions, running 'npm install' there installs required packages locally, as shown in step 4 of the execution_table.

What happens if we skip 'firebase deploy --only functions'?

Skipping deployment means the functions code stays local and is not uploaded to the cloud, so functions won't run remotely. This is shown in step 5 where deployment updates the cloud.

Why do we initialize Firebase with 'firebase init functions'?

This command sets up the functions folder and configuration files needed to write and deploy Cloud Functions, as seen in step 2 of the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, after which step are the Node.js dependencies installed?

A After Step 2

B After Step 3

C After Step 4

D After Step 5

💡 Hint

Check the 'Action' and 'Result' columns for Step 4 in the execution_table.

At which step does the Cloud Function become available to run in the cloud?

A Step 3

B Step 6

C Step 5

D Step 7

💡 Hint

Look for when the function is described as ready to trigger in the execution_table.

If you forget to run 'firebase init functions', what will be missing according to the variable_tracker?

A Functions folder and config files

B Firebase CLI installation

C Node.js dependencies

D Deployment status

💡 Hint

Check the 'Functions folder' row in variable_tracker after Step 2.

Concept Snapshot

Cloud Functions setup steps:
1. Install Firebase CLI globally
2. Initialize project with 'firebase init functions'
3. Write function code in functions folder
4. Run 'npm install' inside functions
5. Deploy with 'firebase deploy --only functions'
Functions run in cloud after deployment.

Full Transcript

To set up Firebase Cloud Functions, first install the Firebase CLI globally using npm. Then initialize your Firebase project with 'firebase init functions' to create the functions folder and config files. Write your function code inside this folder. Next, install dependencies by running 'npm install' inside the functions folder. Finally, deploy your functions to the cloud using 'firebase deploy --only functions'. After deployment, your functions are ready to be triggered and run in the cloud environment.

Practice

1. What is the first command you run to start setting up Cloud Functions in a Firebase project?

easy

A. firebase init functions

B. firebase deploy --only functions

C. firebase start functions

D. firebase create functions

Solution

1. Step 1: Understand Firebase setup commands

   The command firebase init functions initializes Cloud Functions in your project by creating necessary files and folders.

2. Step 2: Differentiate from deploy command

   firebase deploy --only functions is used after setup to upload your functions to Firebase, not to start setup.

3. Final Answer:

   firebase init functions -> Option A

4. Quick Check:

   Setup starts with firebase init functions [OK]

Hint: Setup always begins with 'firebase init functions' command [OK]

Common Mistakes:

• Confusing deploy command as setup
• Using non-existent commands like 'firebase start functions'
• Skipping initialization step

2. Which of the following is the correct way to deploy only Cloud Functions after writing your code?

easy

A. firebase deploy --only database

B. firebase deploy --only hosting

C. firebase deploy --only functions

D. firebase deploy --only storage

Solution

1. Step 1: Identify deployment targets

   Firebase allows deploying specific parts like hosting, functions, database, or storage using the --only flag.

2. Step 2: Match the correct target for Cloud Functions

   To deploy Cloud Functions only, use firebase deploy --only functions.

3. Final Answer:

   firebase deploy --only functions -> Option C

4. Quick Check:

   Deploy functions with --only functions [OK]

Hint: Use '--only functions' to deploy just Cloud Functions [OK]

Common Mistakes:

• Using wrong target like hosting or database
• Omitting '--only' and deploying everything
• Typing incorrect command syntax

3. Given this Cloud Function code snippet, what will happen when an HTTP request is made to it?

const functions = require('firebase-functions');
exports.helloWorld = functions.https.onRequest((request, response) => {
  response.send('Hello from Firebase!');
});

medium

A. The function does nothing and times out.

B. The function returns 'Hello from Firebase!' as the HTTP response.

C. The function throws an error because of missing return statement.

D. The function returns a JSON object with message 'Hello from Firebase!'.

Solution

1. Step 1: Understand the function trigger type

   This function uses functions.https.onRequest, which handles HTTP requests and sends responses.

2. Step 2: Analyze the response sent

   The function calls response.send('Hello from Firebase!'), which sends a plain text response with that message.

3. Final Answer:

   The function returns 'Hello from Firebase!' as the HTTP response. -> Option B

4. Quick Check:

   HTTP function sends plain text response [OK]

Hint: HTTP functions respond with response.send() text [OK]

Common Mistakes:

• Thinking response.send requires return
• Expecting JSON without using response.json()
• Assuming function times out without response

4. You wrote this Cloud Function but get an error when deploying:

exports.myFunction = functions.https.onRequest((req, res) => {
  res.send('Hi');
}

What is the problem?

medium

A. Missing closing parenthesis and semicolon after the function definition.

B. Using 'req' and 'res' instead of 'request' and 'response'.

C. The function name 'myFunction' is invalid.

D. Cloud Functions cannot handle HTTP requests.

Solution

1. Step 1: Check function syntax carefully

   The code snippet is missing a closing parenthesis ')' and semicolon ';' after the arrow function.

2. Step 2: Validate other parts

   Using 'req' and 'res' is valid parameter naming. Function name is valid. Cloud Functions support HTTP triggers.

3. Final Answer:

   Missing closing parenthesis and semicolon after the function definition. -> Option A

4. Quick Check:

   Syntax errors cause deployment failure [OK]

Hint: Check for missing brackets and semicolons in function code [OK]

Common Mistakes:

• Ignoring syntax errors like missing parentheses
• Thinking parameter names must be 'request' and 'response'
• Assuming Cloud Functions don't support HTTP

5. You want to create a Cloud Function that triggers when a new user is added to Firebase Authentication and logs their email. Which setup is correct?

hard

A. exports.logNewUser = functions.database.ref('/users/{userId}').onCreate((snapshot) => {
console.log('New user:', snapshot.val().email);
});

B. exports.logNewUser = functions.storage.object().onFinalize((object) => {
console.log('New user:', object.email);
});

C. exports.logNewUser = functions.https.onRequest((req, res) => {
console.log('New user:', req.body.email);
res.send('Logged');
});

D. exports.logNewUser = functions.auth.user().onCreate((user) => {
console.log('New user:', user.email);
});

Solution

1. Step 1: Identify the correct trigger for new Firebase Authentication users

   The trigger functions.auth.user().onCreate runs when a new user is created in Firebase Authentication.

2. Step 2: Confirm the logging of user email

   The callback receives a user object with an email property, which can be logged directly.

3. Step 3: Differentiate from other triggers

   Database triggers listen to database changes, HTTP triggers respond to requests, and storage triggers respond to file changes, so they are incorrect here.

4. Final Answer:

   Use auth user onCreate trigger to log new user email. -> Option D

5. Quick Check:

   Auth user onCreate triggers new user events [OK]

Hint: Use auth.user().onCreate for new Firebase Authentication users [OK]

Common Mistakes:

• Using database triggers for auth events
• Using HTTP triggers to detect user creation
• Confusing storage triggers with auth triggers