[GH-ISSUE #196] Chain requests. Execute a bunch of requests one by one and produce results #74

New issue

Closed

opened 2026-03-16 13:11:56 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 13:11:56 +03:00

Owner

Originally created by @liyasthomas on GitHub (Oct 18, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/196

Is your feature request related to a problem? Please describe.
Nope

Describe the solution you'd like

Under request section an "add new request" button.
This will create another request section with defaults or inherits last request's setup.
"Send" button on each request section as well as there's a "send all" button.
Sending requests will executes requests top to botton (0 to n)
Results will be a table of all results

Describe alternatives you've considered
Sending each requests one by one.

Additional context
An option to display results next to corresponding request will be awesome.

Originally created by @liyasthomas on GitHub (Oct 18, 2019). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/196 **Is your feature request related to a problem? Please describe.** Nope **Describe the solution you'd like** 1. Under request section an "add new request" button. 2. This will create another request section with defaults or inherits last request's setup. 3. "Send" button on each request section as well as there's a "send all" button. 4. Sending requests will executes requests top to botton (0 to n) 5. Results will be a table of all results **Describe alternatives you've considered** Sending each requests one by one. **Additional context** An option to display results next to corresponding request will be awesome.

kerem

2026-03-16 13:11:56 +03:00

closed this issue
added the
help wanted

feature

good first issue
labels

kerem commented

2026-03-16 13:12:12 +03:00

Author

Owner

@anthonkendel commented on GitHub (Oct 23, 2019):

Hey, 😄 I would be interested in helping out. Is this anything that you looked into @liyasthomas ?

I checked out the source code but it seems like the current implementation only keeps track of one request at a time. Correct me if I am wrong.

@anthonkendel commented on GitHub (Oct 23, 2019): Hey, 😄 I would be interested in helping out. Is this anything that you looked into @liyasthomas ? I checked out the source code but it seems like the current implementation only keeps track of one request at a time. Correct me if I am wrong.

kerem commented

2026-03-16 13:12:17 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 23, 2019):

@anthonkendel currently only one request can be sent at a time. This feature is a very helpful one and it would be great if you could help us pull this off!

@liyasthomas commented on GitHub (Oct 23, 2019): @anthonkendel currently only one request can be sent at a time. This feature is a very helpful one and it would be great if you could help us pull this off!

kerem commented

2026-03-16 13:12:22 +03:00

Author

Owner

@NBTX commented on GitHub (Oct 25, 2019):

I'd like to propose extending #139 to include this.
We could make some sort of 'timeline' or 'step by step' view, where requests can be executed one by one and optionally some script could be inserted between requests to set data for the next request.

@NBTX commented on GitHub (Oct 25, 2019): I'd like to propose extending #139 to include this. We could make some sort of 'timeline' or 'step by step' view, where requests can be executed one by one and optionally some script could be inserted between requests to set data for the next request.

kerem commented

2026-03-16 13:12:27 +03:00

Author

Owner

@NBTX commented on GitHub (Oct 25, 2019):

Please refer to #218.

@NBTX commented on GitHub (Oct 25, 2019): Please refer to #218.

kerem referenced this issue

2026-03-17 00:06:19 +03:00

[PR #75] [MERGED] fixes #74 fallback for findEntryStatus when match is missing or other… #2396