# Adding 'result of' feature to access Return data from API in workflows

**URL:** <https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909>\
**Category:** Idea\
**Created:** [November 4, 2019, 2:59pm UTC](https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909 "2019-11-04T14:59:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![luke2](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/luke2/32/256674_2.png) [@luke2](https://forum.bubble.io/u/luke2)\
**Post date:** [November 4, 2019, 2:59pm UTC](https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909/1 "2019-11-04T14:59:21Z")

</div>

Within API workflows, we have the action ‘Data \> Return data from API’.

It would be super useful if we could refer to these keys of data within a later workflow e.g. result of step 1 key _start-date_.

It would essentially allow for local variables to be composed without touching the DB and could even be used as a ‘get data from external API’ to return data and query on parameters.

![image](https://us1.discourse-cdn.com/bubble/original/3X/f/f/ff69a9090605660c753fe9f11c8f28bad93cb430.png)

![image](https://us1.discourse-cdn.com/bubble/original/3X/9/f/9f260da4a7b2e8835883b93a75664696c3b0a606.png)  
_Example of local variable_

Cheers

---

<div class="post-metadata">

**Author:** ![MattN](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/mattn/32/100743_2.png) [@MattN](https://forum.bubble.io/u/MattN)\
**Post date:** [February 4, 2020, 10:06am UTC](https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909/2 "2020-02-04T10:06:54Z")

</div>

I second this

---

<div class="post-metadata">

**Author:** ![keith](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/keith/32/56020_2.png) [@keith](https://forum.bubble.io/u/keith)\
**Post date:** [February 4, 2020, 3:25pm UTC](https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909/3 "2020-02-04T15:25:51Z")

</div>

While it may not be exactly what @luke2 was suggesting, in my “List Popper and Friends” plug-in there are SSAs Flow State and Flow State List that are akin to local variables for server-side workflows.

> [@List Popper and Friends: New SSA Plugin for Your Backend Workflow (API Workflow) Needs](http://forum.bubble.io/t/list-popper-and-friends-new-ssa-plugin-for-your-api-workflow-needs/75594):
>
> Just published a new “free” plugin, “[List Popper and Friends](https://bubble.io/plugin/list-popper-and-friends-ssas-1578336100803x771148244366655500)”, a set of trivial (but fiendishly clever) Server Side Actions that enable some very useful things in API Workflows. (Like my List Shifter plugin, List Popper and Friends is Karma-Ware. If you find it useful, you can [support my efforts here](https://grupz.com/karma).) The most interesting one (at the moment) is List Popper, which is very very handy for certain types of recursive API Workflows. The application is best explained via example… So here in this tal…

---

<div class="post-metadata">

**Author:** ![FJP](https://avatars.discourse-cdn.com/v4/letter/f/7993a0/32.png) [@FJP](https://forum.bubble.io/u/FJP)\
**Post date:** [February 4, 2020, 3:35pm UTC](https://forum.bubble.io/t/adding-result-of-feature-to-access-return-data-from-api-in-workflows/70909/4 "2020-02-04T15:35:25Z")

</div>

I second this too
