# How To Return Data From Backend API Workflows (no manual API connector)

**URL:** <https://forum.bubble.io/t/how-to-return-data-from-backend-api-workflows-no-manual-api-connector/306357>\
**Category:** Tips\
**Created:** [February 7, 2024, 1:37pm UTC](https://forum.bubble.io/t/how-to-return-data-from-backend-api-workflows-no-manual-api-connector/306357 "2024-02-07T13:37:43Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![georgecollier](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/georgecollier/32/182327_2.png) [@georgecollier](https://forum.bubble.io/u/georgecollier)\
**Post date:** [July 28, 2024, 3:47am UTC](https://forum.bubble.io/t/how-to-return-data-from-backend-api-workflows-no-manual-api-connector/306357/37 "2024-07-28T03:47:23Z")

</div>

Okay, just have caution with security as you’ll run into the same security issue as here:

> [@Log in "as a user" - but be careful. Admin usage](https://forum.bubble.io/t/log-in-as-a-user-but-be-careful-admin-usage/330344/6):
>
> Just as a word of warning, this is not secure if you follow the methodology of the original post exactly, as it will allow any logged in user to generate a login token for any other user provided they know the other user’s unique ID. Explanation: To call this workflow from the backend, the workflow must be public. You may think that ‘this workflow can be run without authentication’ being unchecked would protect it. This is not the case. Any logged in user is ‘authenticated’. Therefore, any logg…

---

_[View the full topic](https://forum.bubble.io/t/how-to-return-data-from-backend-api-workflows-no-manual-api-connector/306357)._