I’m just starting out with an API implementation and now I’m facing problems with “Schedule API Workflow on a list”.
I implemented an API call requesting a list of contacts from HubSpot. Authentication works, the API delivers results. I can show them in a repeating group, so data is available.
I added a button to save the contacts to the database with the following workflow:
Get Contacts is the API call, results is a json element containing the contacts. I schedule save_contact_to_database.
To keep it simple and reduce the risk of errors, I limit the call to the contact’s firstname for now.
hm its probably because when scheduling API you have set up a type of thing “Get Contact result” and what you are passing is a text string. I assume in the backend the “firstname” is setup as text. So the action is scheduled but no data is passed. My first guess.
I would change the “Type of thing” to text (on scheduling action). That should do it.
thanks for your reply. I can’t change the type of things to text because I need Get contacts results for the loop. And as you can see in the scheduling log I showed above, the calls are scheduled and they include the correct parameters.
So, my impression is that the scheduling works properly but the call of the background process is not getting processed.
I think Bubble process the firstname correctly in the scheduling action but when it comes to triggering the backend workflow it doesn’t do that because of the type of things “Get Contact results” even though you only send text string.
You should be able to set it up as text, the list to run on should be list of texts so you would have to change it to “Hubspot connector - Get contact’s results firstname”. But I’m not 100% sure here
The weird things is that he is only passing text and “Get Contact results” is not a thing in DB. So technicaly he can’t apply privacy rules here.
I just tested passing simple list of texts and it works for me . If you @k.richter confirm that it works for you by passing the list of texts manually (e.g. through multidropdown) then I would assume that this is a bubble bug with passing the data from Get call.