Interested in firing off a workflow via API call, to the server, but using the API call that fires off the WF to provide input data to the workflow.
Think:
Is this possible? I understand the use of the API to kick off jobs, or to use the developer tool to "scrape" data from an external API, but that's not really what I am looking for.
Check on the server thread - this should be POST though not PUT.
Thanks! I will check that out. And you are correct, in the verb. Typo on my end :)
When calling that, how do I map, in designer, the expected API data into my workflow? Should that be a download tool? Assuming the payload "questions" is what will be mapped as input to the WF.
When you call the API via the download tool, it will return a response. That response then needs to be parsed (may be as simple as just using the JSON Parse tool). Once parsing that, you can construct another call with that info in it.
This is pretty common when dealing with pagination on API calls, however in that case, the "follow-up" is usually an iterative macro, whereas in yours, it is just a continuation of the flow.