When you call an endpoint using the Schedule API workflow from an action within a workflow you’re not able to retrieve any returned data from that workflow. Instead, you’ll always receive the ID of the scheduled workflow.
To work around this you need to build the call into the API Connector, make the call directly to your own app, and then you’ll receive back any returned values.
The call would be setup as below, and then (once it’s initialised) it will show as an available action within your workflows. All subsequent steps will have access to the response values, and will wait a response if you create that dependency.
I have not yet explored this feature and feel it may be suitable for my use case and prior to going down the path to try and implement it I was curious if you think it is a suitable approach for the use case.
In the app I need to perform a search of the database and the data values needed for constraints are hidden by privacy rules as the goal is to have a algorithm of sorts.
Would you think using the return data from api is the correct approach for a use case like this since I could ‘ignore privacy rules’ in the backend workflows to still access the values hidden by privacy rules and then have the search results returned to be displayed on the page?
I’d imagine I’d be setting up a GET call for my Bubble app to be run in the backend workflow.
I suppose then that I might be able to in the repeating group have the datasource be the data API which would essentially do the same thing of keeping the algorithmic data components hidden through privacy rules.
You find your base url for the API in your settings > API. You’ll see the “workflow API root url”.
The parameters passed are those defined by you in your Backend API workflow.
So the endpoint URL would be your API root url plus the api workflow slug (the name you give to it). Set it as a “POST” call, add the parameters you have set in your Backend API Workflow and it should be good to go.