This repository has been archived by the owner on Dec 13, 2023. It is now read-only.
Replies: 1 comment
-
Hi @Mishtir , One way to achieve this is to add HTTP task as the first task and invoke the API there. Now for subsequent tasks we can use http_task.output.resonse.body.status like that. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
can we pass workflow input through an rest api in conductor?
So I have a requirement to pass task input parameter from UI field , not hard coded in json file. How can we pass the input to task work through an api call.?
workflow input in json.
{
"movieId": "234232",
}
"tasks": [
{
"name": "movie_info",
"taskReferenceName": "movie_info",
"inputParameters": {
"movieId": "${workflow.input.movieId}"
},
"type": "SIMPLE"
},
I don't want this movieId input to be hardcoded in JSON. Instead it should be from Rest API call as a paramater.
How can we achieve this?
Beta Was this translation helpful? Give feedback.
All reactions