Create another API Workflow. Let’s just call it “create” as an example. The only action you need to add to “create” is the “Create A New Thing” action.
Now, for your current API Workflow (let’s call it “data”). The only action you should have here is “Schedule an API Workflow on a list”. Select the “create” API Workflow we just created. The list will the text list you got from the API Connector.
@dbevan - tks for the help but things are not working as I expected.
So… I setup like you said my “data” Workflow calling the Schedule Workflow API. The only thing that I did different it was adding a first step that would call the API and save the data so the Schedule Workflow would work on that data.
Please notice that on Step 2 the “List to run on” is actually a search on the data thatI recorded on the first step. For my Parameter “app_name” I’m getting the “First Item” from the “Result of Step 1”
Change “Type of things” from Beanstalk to text… it’s because it’s looking for a value that is a list of Beanstalks. Your list will be a list of texts, so you need to define the Type of that list as a text. Right above the expression in your screenshot.
Would you mind sharing your editor link? I would also change Application_Name to a single text rather than a list of texts, but even with the list type, there should only be one name added and you should have multiple records, one for each text.
Few things… don’t bother the 2 Recurring Groups that I have there… I’m working with that as a plan B. Basicaly the text “Elastic Beanstalk” title is where everything is setup. The page that I’m working is “dashboard_beanstalk”
You have 2 (what looks like) identical API calls. I’m not sure if one of them was modified somehow, but the response’s “Applications” field wasn’t registering as a list of texts. It was coming through as one string, so I removed and re-added that call to your original workflow on the dashboard page and it’s reading it as a list of texts now.
When you first “Create Beanstalk” on the page, you needed to use “Add List” not “Add” in order to add multiple items to the list value. Before, it was only adding a single value (the entire list) as a single text, so that’s why the API Workflow was only running once and putting everything in the same field.
I added a Test button so you can see how it could work with a direct API trigger from the API call without needed to create a Thing first.
Hey @romanmg, sorry to tag you but I’m struggling with a somewhat similar problem over here:
If you have any guidance on the overall solution / approach as detailed in the first post that would be great but I’m now struggling with the “type of thing” options in the “Schedule API Workflow on a List” as my API Call doesn’t seem to be present…
Any advice would be greatly appreciated.