[GH-ISSUE #5861] [feature]: Common Workspace & Cross-Request Execution #2304

New issue

Open

opened 2026-03-16 23:54:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 23:54:14 +03:00

Owner

Originally created by @roopepaajanen on GitHub (Feb 11, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5861

Is there an existing issue for this?

I have searched the existing issues

Summary

Problem / Motivation

In real-world API testing, many requests depend on shared setup logic such as:

Creating users
Authenticating sessions
Seeding test data

Currently, Hoppscotch supports running a single collection in sequence, but there’s no way to:

Share reusable setup requests across multiple workspaces or collections
Define that one request must run before another

This makes complex workflows harder to model and maintain.

Proposed Solution

1️⃣ Common / Shared Workspace

Introduce a Common Workspace where reusable requests (e.g., auth flows, user creation, session setup) can live and be:

Imported into other workspaces or collections
Referenced as links instead of copied, so updates propagate automatically

2️⃣ Cross-Request Execution / Dependencies

Add a way to define that:

“Before running this request, run another request.”

This could be implemented as:

A pre-request script
Or a built-in helper like:

hopp.executeRequest("request-name-or-id", "optional-workspace");

This would allow composing workflows across workspaces and collections instead of being limited to a single collection’s order.

Why should this be worked on?

Benefits

Enables reusable authentication and setup flows
Improves support for realistic integration / end-to-end API testing
Reduces duplication across workspaces and collections
Makes complex workflows easier to maintain

Originally created by @roopepaajanen on GitHub (Feb 11, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5861 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary ### Problem / Motivation In real-world API testing, many requests depend on shared setup logic such as: - Creating users - Authenticating sessions - Seeding test data Currently, Hoppscotch supports running a single collection in sequence, but there’s no way to: - Share reusable setup requests across multiple workspaces or collections - Define that one request must run before another This makes complex workflows harder to model and maintain. --- ### Proposed Solution #### 1️⃣ Common / Shared Workspace Introduce a **Common Workspace** where reusable requests (e.g., auth flows, user creation, session setup) can live and be: - Imported into other workspaces or collections - Referenced as links instead of copied, so updates propagate automatically #### 2️⃣ Cross-Request Execution / Dependencies Add a way to define that: > “Before running this request, run another request.” This could be implemented as: - A pre-request script - Or a built-in helper like: ```js hopp.executeRequest("request-name-or-id", "optional-workspace"); ``` This would allow composing workflows across workspaces and collections instead of being limited to a single collection’s order. ### Why should this be worked on? ## Benefits - Enables reusable authentication and setup flows - Improves support for realistic integration / end-to-end API testing - Reduces duplication across workspaces and collections - Makes complex workflows easier to maintain