REST API Open AI (Stream Response) Template issue
I have tried using the standard template, but it won't let me ship it with the Output Flow being an object which is how it is set from the AI Assistant Node.
I changed the AI Assistant Node output to a string, which allowed me to ship it, but may have impacted the functionality.
What am I missing, surely the template should work straight out of the box?
3 Replies
AI Support Bot Information
<@797926148549378059> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human!
Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers.
Please note: Team members will review and answer the questions on best efforts basis.
AI Response
It seems like you've encountered an issue with the output configuration of the AI Assistant Node in your template. When the AI Assistant Node output is set to an object, there can be complexities in shipping the workflow if it's not correctly handled by subsequent nodes. Changing the output to a string might impact the expected functionalities if those subsequent nodes are designed to process a structured object output.
Here are a couple of steps you can take:
1. Object to String Output: When you change the AI Assistant Node output from an object to a string, ensure that the downstream nodes handling the output are made aware of this change. They should be configured to parse or handle string outputs, which might require some nodes in the workflow to perform string operations or JSON parsing if you are still expecting a structured format.
2. Output Configuration:
- Make sure the downstream nodes are correctly configured to accept either a string or object, depending on the AI Assistant Node's output type【4:0†source】.
- If the workflow logic depends on object attributes, convert the string back to a JSON object within your workflow using parsing nodes .
3. Documentation and Community Support:
- Revisit the documentation for the AI Assistant Node to ensure there is no mismatch between expected and configured output types .
- For further assistance, consider joining the BuildShip community or sending a support request through the BuildShip Dashboard .
If altering the output did not fundamentally break expected behavioral logic in your workflow, ensure that changes are also reflected and tested downstream to maintain functional integrity. If these adjustments do not resolve the issue, I recommend reaching out for support directly via BuildShip's support channels .
BuildShip AI Support
Hi @Chris Wright | byc Design thanks for highligting this. We have updated the trigger, you can refersh the app and re-clone this template. It should now work out of the box :)