Hi there,
What am I missing here? I have Benzinga API pulling Get IPOs set up in the backend workflow and in the plugin page, but it doesn’t seem to be working. Even when I search “Uses API” Benzinga doesn’t show up. Here is the back end workflow along with the plugin. Any help would be appreciated. Thanks!
In your second screenshot, you have static text for those parameters. You’ll want to replace those with actual dates and an IPO type. You’re probably getting an error because of this.
You can confirm if there’s an error by looking at your server logs and enable the advanced filters for “plugin server side output” and “plugin server side error”
it should also be pulling the dates and IPO type from the API, right?
Yeah, seems like it’s still going through. Weird, I would think those texts you have in the date parameters would create issues, but looks like it’s returning 50 items. It might be ignoring the text and just returning data unfiltered. OK, what does your “update-ipos” workflow setup look like?
Indeed! You’re scheduling this workflow (update-ipos) for each item in the list, but nothing is happening here. For example, if you wanted to create a record for each item, you’ll want to add a “create new thing” action to this workflow and map all those parameter values to the fields.
Thanks, so I need to create a new thing for every key in the update-ipos? Ticker, name, dealsize, etc? Isnt this what is being done on my 3rd screen shot above?
I’m only assuming that creating records was your goal, so you don’t have to if that’s not ultimately what you’re trying to achieve.
Your third screenshot is only a scheduling action. It’s defining:
You’ve set up this scheduling action well. If the API returns 50 items, then you’re scheduling “update-ipos” 50 times, once for each item. And, each run is going to have different values for all those parameters. So, again, all good there.
However, your newest screenshot (update-ipos) is the actual workflow being scheduled. It will receive all that data and you need to tell Bubble what to do with it. Look at this workflow from the perspective of one item (i.e. one IPO). You should only need one Create action where you can map all the parameters to all the fields in your data structure. One action will create one record and save the ticker value to the ticker field, the name value to the name field, etc. But make sure to set up that Create action – Bubble’s not going to know which parameters go to which fields. If you schedule this workflow on 50 items, then you’ll come out with 50 records.
What I would recommend for testing is to modify your expression in the “List to run on” field (3rd screenshot) so it says “result of step 1’s ipos :items until 5” – this will limit the list to only 5 items so you can test with a much smaller set of data until you can confirm you’re getting the data you need in your database. Alternatively, you can set the API parameter values to pagesize=5, page=1 (2nd screenshot), which should limit the API response to only the first page of results with 5 items in the page. Again, this is just my suggestion for while you sort things out. Once it looks good, you can remove/change those limits.
OK, so you have a condition that failed, which means the action won’t run. What’s the conditional expression you have? If you click on the part that says “Schedule API Workflow get-ipos-action”, it should take you right to the action in your workflow.
