Yes, it’s easy to send data types to an API connector call. I was referring to getting data back from the API - which will return the Thing’s unique ID and fields not the Thing itself as Bubble needs it.
Did you ever manage to get the return data to work on recursive workflows?
Nope, tried several things, but didn’t manage to make it work. 
Maybe I’ll try again someday.
1 Like
Thank you for this solution. Regarding usage, I’ve received the following error when implementing:
Workflow error - Error connecting to a Bubble app: Invalid data for key defaultWorkItems: array length exceeds the limit of 200 entries. Contact support@bubble.io if you need to increase this limit
I’m passing a list of 831 items to my API workflow workflow!
Does this error also occur when calling the API workflow manually using something like Postman rather than the app connector? I’ve never come across this - passing a list of more than 200 surely isn’t a default limit…
1 Like
Unfortunately, I haven’t tested this error using any other request client.
As an update, I’ve avoided the need to pass such a large list (and therefore avoided the error) by obtaining the list using a search in the API workflow itself. This may not be suitable when considering privacy rules.
1 Like
If I am not mistaken the API connector is the only one allowing workflows to continue on error, contrary to App Connector?
Correct
Another way to see this is to check the logs. The original way Bubble saved it always appears. In my case, the difference is that the first letter of the Display was capitalized, and Bubble always saves it in lowcase.
Having the same issue. Did you ever get a workaround?
No, sorry, I didn’t manage to find a way to make this method work on recursive. If you have more luck than me please let me know !
@georgecollier brilliant mate. 7 years in Bubble and first I’ve heard of this!
One thing I noticed is that it pulls your main version workflows, not workflows in any other branches.
So if you are working in a non-main branch you’ll have to update the BE workflow in main > click refresh > use the new field in your workflow action.
3 Likes
Yes correct, the app connector was added prior to version control so if in live it’ll use version-live, if it’s in any development branch it’ll use version-test.
2 Likes
Hello there,
I used your workaround, but now I have an error message, despite the workaround working.
Is there any “correct way” to make it recognise option sets ? I didn’t understand the undelaying ID method…
Make the backend workflow take text parameter instead of option. Use Get all options:filtered (This Option’s Display is parameter):first item inside the backend workflow to convert it back to the option
1 Like
Hi @georgecollier thanks for the great tutorial. I have the same question, does the Bubble App Connector expose private data?
The API key you put into the plugin settings are protected. However, any other parameters you put into the action if used on a front-end action could be accessed.
My use case is for variable API keys. Each user will have their own key, since my app will connect to their external system. So in the API call options the “Private” box It is not checked, but all the action is in the backend. My fear is that the App Connector plugin will leak this information. Do you know if this is possible in this scenario?
If the user is allowed to know their own API key, then it’s fine. You’ll protect API keys by privacy rules and a user could only ever see their own API key.
Hello,
I have a problem, like everyone else here lol.
I’ve encapsulated my web application using the webtonative plugin.
I’ve set up a payment button that natively opens the appstore payment popup.
Upon payment, I receive the payment data via a web platform for processing Apple “Revenue Cat” in-app payments.
I immediately retrieve the payment data from Revenue Cat via a WEBHOOK I’ve set up on my BACKEND WORKFLOW.
I made a DETECT DTATA and just after create a new thing where I place the data in front of each field.
The problem is that I can’t attribute this to the current user from the workflow backend, so I have all the payment data but I can’t find out who paid because I can’t add the user id or the email address of the user who made the payment to my data base.
Could you please help me, I haven’t been able to for several days. 