Flow creation in Postman - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a flow in Postman?

A flow in Postman is a sequence of API requests and actions connected logically to automate testing or data processing.

beginner

How do you start creating a flow in Postman?

You start by opening the Flows tab and clicking 'Create Flow' to add requests and actions in order.

intermediate

What is the purpose of adding conditions in a Postman flow?

Conditions let you control which requests or actions run based on previous results, like checking if a response status is 200.

intermediate

How can you pass data between requests in a Postman flow?

You can store data from one request's response in variables and use those variables in later requests within the flow.

beginner

Why is it useful to use flows instead of running requests one by one?

Flows automate the process, reduce manual errors, and allow complex testing scenarios with data dependencies and conditions.

What is the first step to create a flow in Postman?

A Send a request manually

B Write a test script

C Export the collection

D Open the Flows tab and click 'Create Flow'

You start creating a flow by opening the Flows tab and clicking 'Create Flow' to begin adding requests.

How do you control which requests run in a flow based on previous results?

A By changing the request URL

B By adding conditions

C By exporting the flow

D By using Postman monitors

Conditions let you decide if a request should run depending on earlier responses or variables.

How can data be shared between requests in a Postman flow?

A Using variables to store response data

B By copying and pasting manually

C By exporting the collection

D By running requests in parallel

Variables allow you to save data from one request and use it in another within the flow.

What is a key benefit of using flows in Postman?

A Automates sequences of requests with logic

B Requires no internet connection

C Automatically fixes API errors

D Generates API documentation

Flows automate running requests in order with conditions and data passing.

Which Postman feature is used to create flows?

A Monitors tab

B Collections tab

C Flows tab

D Environments tab

The Flows tab is where you create and manage flows.

Explain how to create a simple flow in Postman that sends two requests one after another.

Think about how you add and link requests in the flow editor.

Describe how you can use conditions and variables in a Postman flow to handle different API responses.

Consider how to make the flow smart and dynamic.

Practice

1. What is the main purpose of creating a flow in Postman?

easy

A. To automate API tests by chaining multiple requests

B. To write SQL queries inside Postman

C. To design user interfaces for APIs

D. To create database backups automatically

Solution

1. Step 1: Understand flow creation in Postman

   Flow creation means linking API requests so they run one after another automatically.

2. Step 2: Identify the purpose of chaining requests

   Chaining helps automate tests by passing data between requests and checking responses.

3. Final Answer:

   To automate API tests by chaining multiple requests -> Option A

4. Quick Check:

   Flow creation = automate chained API tests [OK]

Hint: Flows chain requests to automate tests quickly [OK]

Common Mistakes:

• Confusing flow creation with UI design
• Thinking flow creates database backups
• Assuming flow writes SQL queries

2. Which Postman script section is used to pass data from one request to the next in a flow?

easy

A. Pre-request Script

B. Headers

C. Tests

D. Body

Solution

1. Step 1: Identify where to save data after a request

   The Tests script runs after a request and can save response data to variables.

2. Step 2: Understand data passing in flows

   Saved variables from Tests can be used in the next request's Pre-request Script or URL.

3. Final Answer:

   Tests -> Option C

4. Quick Check:

   Data passing happens in Tests script [OK]

Hint: Use Tests to save data for next request [OK]

Common Mistakes:

• Using Body to pass data between requests
• Confusing Pre-request Script as data saver
• Trying to pass data via Headers

3. Consider this Postman Tests script snippet:
pm.environment.set('token', pm.response.json().access_token);
What will be the value of token after this runs if the response JSON is {"access_token": "abc123"}?

medium

A. undefined

B. "abc123"

C. pm.response.json()

D. null

Solution

1. Step 1: Extract value from response JSON

   The code accesses the 'access_token' key from the JSON response, which is "abc123".

2. Step 2: Store value in environment variable

   pm.environment.set saves "abc123" as the value of 'token'.

3. Final Answer:

   "abc123" -> Option B

4. Quick Check:

   token = "abc123" after set [OK]

Hint: pm.environment.set stores exact JSON key value [OK]

Common Mistakes:

• Assuming token becomes undefined
• Confusing the whole JSON with the value
• Expecting null instead of actual token

4. You wrote this Pre-request Script to use a token saved in environment variables:
pm.request.headers.add({key: 'Authorization', value: 'Bearer ' + pm.environment.get('token')});
But the API returns 401 Unauthorized. What is the likely error?

medium

A. Bearer keyword should be lowercase 'bearer'

B. The header key should be lowercase 'authorization'

C. pm.request.headers.add is not valid syntax

D. The token variable is not set or is empty

Solution

1. Step 1: Check if token variable exists

   If 'token' is missing or empty, the Authorization header will be invalid.

2. Step 2: Verify header syntax and casing

   Header keys are case-insensitive, and 'Bearer' is case-sensitive but usually uppercase works fine.

3. Step 3: Confirm method usage

   pm.request.headers.add is valid to add headers dynamically.

4. Final Answer:

   The token variable is not set or is empty -> Option D

5. Quick Check:

   Missing token causes 401 Unauthorized [OK]

Hint: Check if token variable is set before request [OK]

Common Mistakes:

• Changing header key case unnecessarily
• Lowercasing 'Bearer' keyword
• Thinking pm.request.headers.add is invalid

5. You want to create a flow where the first request logs in and saves a token, and the second request uses that token in its header. Which steps correctly describe this flow setup?

hard

A. In first request Tests, save token to environment; in second request Pre-request Script, add Authorization header using saved token

B. In first request Body, save token; in second request Tests, add Authorization header

C. In first request Headers, save token; in second request Body, add Authorization header

D. In first request Pre-request Script, save token; in second request Tests, add Authorization header

Solution

1. Step 1: Save token after login request

   Use Tests script in first request to extract token from response and save it to environment variables.

2. Step 2: Use token before second request

   In second request's Pre-request Script, read the saved token and add it to the Authorization header.

3. Final Answer:

   In first request Tests, save token to environment; in second request Pre-request Script, add Authorization header using saved token -> Option A

4. Quick Check:

   Save token in Tests, use in Pre-request Script [OK]

Hint: Save token in Tests, use in Pre-request Script for next request [OK]

Common Mistakes:

• Trying to save token in Body or Headers
• Adding header in Tests instead of Pre-request Script
• Saving token before request runs