TLDR: calling backend workflow from API connector is unreasonably tedious app connector auto-sets up and syncs fields result/returned data from backend workflow can be used in following front-end steps Returning data from backend workflow in front-end without manually setting up API connector cal…

Really appreciate this mate. Do you know if there is a way to make the data types the same? In the backend workflow a parameter is set to type User. However when I try and use that data in the front end it is type Appname’s User.

[image] harry7: However when I try and use that data in the front end it is type Appname’s User. You’ll have to Do a search for User:unique ID = Appname’s User’s unique ID:first item to convert it back to a data type (because the API connector doesn’t ‘know’ that this is a data type rather th…

The issue with that is that then I would have to make the user data type public as the user isn’t logged in when this needs to happen (it’s part of the login process)

If you’re checking if a user exists with a certain email, a backend workflow that returns a yes/no is sufficient (userExists = yes/no). It would take the user email as a parameter, and return data from API as Do a search for user where email = BE workflow’s email:first item is not empty. Otherwise …

Really appreciate the help! However I need to assign a temp password to the user. I just realised now that I could do this in the backend and just return the password to log the user in. I’m not at my laptop now but I’ll update in case anyone else is having a similar issue

Okay, just have caution with security as you’ll run into the same security issue as here: [image] Log in "as a user" - but be careful. Admin usage Tips Just as a word of warning, this is not secure if you follow the methodology of the original post exactly, as it will all…

Great post, its really helpful. I am using my flow for signup/login with an API. So what I decided to do is send the tokens retrieved on the front end to the backend workflow. Then make the call to get the email on the backend (I figured this is the security as it is almost impossible to guess thes…

[image] georgecollier: With this method: you can trigger backend workflows to run synchronously from the front-end as a consequence, you can use the returned data in following front-end steps any backend workflow changes are easily updated in the API calls Someone just pointed me to this po…

Thanks for this @georgecollier . It seems like I may have hit an edge case as I am trying to set this up in my app with multiple branches but the App connector only seems to be able to reference workflows present in the live and main environments and can’t see workflows I create in a new branch. Hav…

You can actually send the ID of the user to the User field. [image] [image] [image] [image]

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

Tips

georgecollier July 28, 2024, 3:47am 37

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

Topic		Replies	Views
Let us return data from API workflows Idea	16	3486	September 12, 2024
Simpler, more secure alternative to API / App Connector for "returning" data Tips	23	782	June 4, 2026
Result Of Backend Workflow & Return Data From API fix Tips	16	3084	July 19, 2024
Return json response from back end workflows APIs	5	252	March 6, 2025
[New Features] API Connector New features	53	9960	December 28, 2022

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

Related topics