nithinrdy
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
No problem! I'm not sure if discord allows it, but could you please edit the title of this thread to something like "Formatting the Workflow Output", should allow other users to stumble across this thread if they're facing the same issue.
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
Either way, I'll see if this can be improved.
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
Hmm, I see what you mean. In the workflow logs, you should find an entry that's just a random id string (UI requires a bit of improvement), instead of a node label.
That's the only place I can think of that would contain trigger related logs (the id is that of a trigger).
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
You should be able to see output logs in the workflow logs section, it should be the last entry for every workflow log (assuming the workflow contains an output node).
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
Right, it would certainly be easier to separate the output into two properties. So one for status code, one for the response body. Then you can simply select these variables in their respective fields in the workflow output section.
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
ah, i think i see the issue. in your json string, you've got a colon instead of a comma after
"error"
Could that be the reason?33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
Ah, in this case you'd need to parse the output property within the flow output, since the string you're trying to parse is assigned to the output property within the flow output
are you able the select the
Output variable inside the Flow Output variable, from the variables menu? If so try parsing that.33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
The flow output is, by default, an object. You shouldn't need to parse it, and should be able to destructure the flow output directly, sorta like so:
and then
flowOutput.statusCode for your status code.33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
In other words, the workflow output section of a trigger acts as one final step (that runs after the workflow's output node, and before sending back the response).
The section lets you format the workflow's output (pick and choose which properties you want to send back, and so on).
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
33 replies
BBuildShip
•Created by Chris on 11/23/2024 in #❓・buildship-help
Formatting Workflow Output in API Call Trigger and setting HTTP Status Code
33 replies
BBuildShip
•Created by dbrwk on 11/18/2024 in #❓・buildship-help
In one of my production workflows expressions does not work
Hey @dbrwk, could you please clear the expression, try switching to "JavaScript" using the dropdown at the bottom of the expression editor (where it currently says "Text"), and add the expression you want again and test it to see if it works?
7 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
I believe this isn't currently possible, no. The triggers on v2 workflows work a bit differently, and handling endpoint API specs on V2 workflows is something that's still in the works.
11 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
cheers!
11 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
Holding down space allows you to drag using your mouse, sorry for missing out on this detail @jeff_sss
11 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
no problem!
11 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
To move around in the canvas, you'd have to rely on scrolling (vertically and sideways) just the way you did back in V1 (Edit: you may also hold down space and drag the canvas using your mouse).
Zooming in and out can be achieved by holding down ctrl (or command) and using the scroll wheel, both at the same time.
I presume the other features (the connect tab, testing, etc.) are showing up fine?
11 replies
BBuildShip
•Created by jeff_sss on 11/17/2024 in #💬・general
jeff_sss - Hi team, I have upgraded to V2, howe...
In case you're unable to see the new features even after creating new flows, do let us know
11 replies