Return Data from API Not Working As I Expect

matthewpomar · 2025-01-19T22:32:57.148Z

I have created a data type called Site. I created an API Workflow called get-most-aged-site with a single node, “Return data from API”.

image1590×1630 181 KB

All I’m doing in the “Return data from API” is returning a single Site:

image1500×1164 53.1 KB

However, when I try to consume this API by trying to log the return value to my Log data type, I am unable to resolve that the return value from the get-most-aged-site api is Site:

image1460×1218 68.9 KB

image1546×1874 176 KB

Finally, the API does return something, but it just returns an incrementing number, such as 174, 175, 176, etc. each time I run it. I’m expecting it to return a JSON representation of Site.

I am trying to create a simple API that queries the Site table and returns a single Site, but this does not seem possible with my approach.

Any suggestions?

LittleBubbler · 2025-01-20T01:15:28.328Z

In the last step - do you have an option for request data’s source when trying to map the Message field?

Jici · 2025-01-20T01:36:44.664Z

Return data from API can only be used if you call your backend workflow from outside Bubble or using API Connector, not using schedule workflow. You can search forum about this subject/request but read this post:

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

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 calls I have a lot of feelings today, as I’ve learned something that would’ve saved me hours of time had I known earlier, and it feels like something that only a handful of people know about (based on th…

matthewpomar · 2025-01-20T11:30:39.496Z

No, because I was not using the Bubble App Connector. Appreciate your help.

matthewpomar · 2025-01-20T11:32:01.119Z

Thanks for sending me this. This is exactly my problem and I see the workaround is to use the Bubble App Connector.

matthewpomar · 2025-01-20T11:37:59.384Z

Now that I understand that if I am going to take the current approach of putting specific “logic” into individual backend workflows, I am questioning my overall approach.

What I need to do is query a single Site, then once I find the aged Site, I need to query for a single Category belonging to that site, then using the output of that call, I need to query for a single Tag associated with that Category.

This all needs to happen on the backend workflow.

What is the best approach to handle something like this?

Jici · 2025-01-20T12:24:07.949Z

Why do you use backend WF? I don’t see any reason for that from your screenshot. Basically, your are just doing a search no?

matthewpomar · 2025-01-20T12:26:51.523Z

There is no UI component for this in the end. I only setup a button for testing. This will be a recurring backend workflow. It will take the results from the searched Site, Category, and Tag and store them into the database.

Jici · 2025-01-20T16:00:16.086Z

What do you mean there’s no UI component?

Actually, your backend WF just do a search and return the result of the search. This can be done in frontend. After, you said that from this response, you query a single category… Is it another DB? If yes, this can be done in front end… same for tag…
Finally, what do you need to store them in DB? The result of the search? or will the user do some actions and this is what you need to store? (select a site, afte select a category and finally select a tag?)

matthewpomar · 2025-01-20T22:19:57.156Z

@Jici what I mean is this entire process will be done only with backend workflows. I am all wiring it up to a button click for convenience.

So, in the end, it will be a backend workflow that gets locked off initially by a recurring workflow or external API call into the site. Then it will process the records (query site, then category, then tag), and then store those values into a new record.

Hopefully that makes sense.