Duplicating and moving requests in Postman - Build an Automation Script

Duplicate and move a request in Postman

Preconditions (3)

Step 1: Open the 'Sample Collection' in Postman

Step 2: Right-click on the request named 'Get User'

Step 3: Select 'Duplicate' from the context menu

Step 4: Verify a new request named 'Get User Copy' appears in the same collection

Step 5: Drag the duplicated request 'Get User Copy' to another collection named 'Backup Collection'

Step 6: Verify the request 'Get User Copy' is now listed under 'Backup Collection' and no longer under 'Sample Collection'

✅ Expected Result: The request is duplicated correctly with the new name and moved successfully to the target collection.

Automation Requirements - Postman Test Scripts with Newman CLI

Assertions Needed:

Verify the duplicated request exists in the original collection before moving

Verify the duplicated request is removed from the original collection after moving

Verify the duplicated request exists in the target collection after moving

Best Practices:

Use Postman Collection SDK to manipulate collections programmatically

Use explicit checks for request existence in collections

Avoid hardcoding collection IDs; use variables or dynamic retrieval

Use Newman CLI to run tests and validate collection structure

Automated Solution

Postman

import fs from 'fs';
import { Collection } from 'postman-collection';

// Load the original collection JSON
const sampleCollectionData = JSON.parse(fs.readFileSync('Sample_Collection.json', 'utf8'));
const backupCollectionData = JSON.parse(fs.readFileSync('Backup_Collection.json', 'utf8'));

const sampleCollection = new Collection(sampleCollectionData);
const backupCollection = new Collection(backupCollectionData);

// Find the request named 'Get User'
const originalRequest = sampleCollection.items.one('Get User');
if (!originalRequest) {
  throw new Error("Original request 'Get User' not found in Sample Collection.");
}

// Duplicate the request
const duplicatedRequest = originalRequest.clone();
duplicatedRequest.name = 'Get User Copy';

// Add duplicated request to Sample Collection
sampleCollection.items.add(duplicatedRequest);

// Assert duplicated request exists in Sample Collection
if (!sampleCollection.items.one('Get User Copy')) {
  throw new Error("Duplicated request not found in Sample Collection after adding.");
}

// Remove duplicated request from Sample Collection
sampleCollection.items.remove(duplicatedRequest);

// Assert duplicated request removed from Sample Collection
if (sampleCollection.items.one('Get User Copy')) {
  throw new Error("Duplicated request still exists in Sample Collection after removal.");
}

// Add duplicated request to Backup Collection
backupCollection.items.add(duplicatedRequest);

// Assert duplicated request exists in Backup Collection
if (!backupCollection.items.one('Get User Copy')) {
  throw new Error("Duplicated request not found in Backup Collection after adding.");
}

// Save updated collections back to files
fs.writeFileSync('Sample_Collection_Updated.json', JSON.stringify(sampleCollection.toJSON(), null, 2));
fs.writeFileSync('Backup_Collection_Updated.json', JSON.stringify(backupCollection.toJSON(), null, 2));

console.log('Request duplicated and moved successfully.');

This script uses the Postman Collection SDK to automate duplicating and moving a request between collections.

First, it loads the JSON files for the two collections: 'Sample Collection' and 'Backup Collection'.

It finds the original request named 'Get User' in the sample collection. If not found, it throws an error.

It clones this request and renames it to 'Get User Copy'.

The duplicated request is added to the sample collection, then verified to exist there.

Next, the duplicated request is removed from the sample collection and verified it no longer exists there.

Then, the duplicated request is added to the backup collection and verified to exist there.

Finally, the updated collections are saved back to JSON files.

This approach uses explicit checks after each step to ensure the duplication and move operations succeeded, following best practices for automation.

Common Mistakes - 4 Pitfalls

Hardcoding collection IDs or request IDs instead of using names or dynamic lookup

Not verifying the request exists after duplication or move

Modifying the original request object directly instead of cloning

Not saving the updated collections back to files after changes

Bonus Challenge

Now add data-driven testing to duplicate and move requests with three different request names.

Show Hint

Practice

1. What is the main benefit of duplicating a request in Postman?

easy

A. It exports the request to a file.

B. It saves time by reusing an existing request setup.

C. It merges two requests into one.

D. It deletes the original request automatically.

Solution

1. Step 1: Understand duplicating requests

   Duplicating means making a copy of an existing request to reuse its setup.

2. Step 2: Identify the benefit

   Reusing saves time because you don't have to create the request from scratch.

3. Final Answer:

   It saves time by reusing an existing request setup. -> Option B

4. Quick Check:

   Duplicating = Reuse setup [OK]

Hint: Duplicating means copying to reuse quickly [OK]

Common Mistakes:

• Thinking it deletes the original request
• Confusing duplication with merging requests
• Assuming it exports the request

2. Which of the following is the correct way to duplicate a request in Postman?

easy

A. Rename the request with a new name.

B. Drag the request to the trash bin.

C. Click 'Send' button twice quickly.

D. Right-click the request and select 'Duplicate'.

Solution

1. Step 1: Locate duplication method

   In Postman, duplicating is done by right-clicking the request and choosing 'Duplicate'.

2. Step 2: Eliminate wrong options

   Dragging to trash deletes, clicking send sends request, renaming changes name only.

3. Final Answer:

   Right-click the request and select 'Duplicate'. -> Option D

4. Quick Check:

   Duplicate = Right-click + Duplicate [OK]

Hint: Right-click request to duplicate it [OK]

Common Mistakes:

• Trying to duplicate by clicking send
• Dragging request to trash instead of duplicating
• Thinking renaming duplicates the request

3. Given a collection with requests A, B, and C, you duplicate request B and move the duplicate to a new folder named 'Tests'. What will be the order of requests in the original collection and the new folder?

medium

A. Original collection: A, B, C; New folder: B (duplicate)

B. Original collection: A, C; New folder: B (original and duplicate)

C. Original collection: A, B, C; New folder: empty

D. Original collection: A, B; New folder: C, B (duplicate)

Solution

1. Step 1: Understand duplication effect

   Duplicating request B creates a copy but does not remove the original from the collection.

2. Step 2: Understand moving the duplicate

   Moving the duplicate to 'Tests' folder places only the copy there; original stays in the main collection.

3. Final Answer:

   Original collection: A, B, C; New folder: B (duplicate) -> Option A

4. Quick Check:

   Duplicate copy moved; original stays [OK]

Hint: Duplicate copies; moving affects only the copy [OK]

Common Mistakes:

• Assuming original is removed when duplicate is moved
• Thinking duplicate appears in both places
• Confusing original and duplicate requests

4. You tried to move a request to another folder in Postman but it did not move. What is the most likely reason?

medium

A. You dragged the request outside any folder accidentally.

B. The request is locked and cannot be moved.

C. You duplicated the request instead of moving it.

D. Postman does not support moving requests between folders.

Solution

1. Step 1: Check Postman folder behavior

   Postman allows moving requests by dragging them into folders.

2. Step 2: Identify common mistake

   Dragging outside any folder leaves the request in the original place, so it appears not moved.

3. Final Answer:

   You dragged the request outside any folder accidentally. -> Option A

4. Quick Check:

   Drag inside folder to move [OK]

Hint: Drag request carefully inside target folder [OK]

Common Mistakes:

• Confusing duplication with moving
• Assuming requests can be locked
• Believing Postman disallows moving requests

5. You have a collection with 5 requests. You want to create a new folder and move 3 specific requests into it, but also keep duplicates of those 3 requests in the original collection. What is the correct sequence of actions in Postman?

hard

A. Delete the 3 requests, then create new ones in the folder.

B. Move the 3 requests into the new folder, then duplicate them back to the original collection.

C. Duplicate the 3 requests, then move the duplicates into the new folder.

D. Rename the 3 requests and drag them into the new folder.

Solution

1. Step 1: Understand requirement

   You want duplicates in the new folder and originals to remain in place.

2. Step 2: Choose correct order

   Duplicating first creates copies; moving duplicates places them in the folder without removing originals.

3. Step 3: Eliminate wrong options

   Moving first removes originals from collection; deleting loses data; renaming doesn't duplicate.

4. Final Answer:

   Duplicate the 3 requests, then move the duplicates into the new folder. -> Option C

5. Quick Check:

   Duplicate first, then move duplicates [OK]

Hint: Duplicate first, then move copies to folder [OK]

Common Mistakes:

• Moving first removes originals
• Deleting requests instead of duplicating
• Thinking renaming duplicates requests