Emmanuel - Hey, How can I pass the response fro...
Hey, How can I pass the response from an assistant node to another utility node when using email trigger? I do not see any data nor can I test the data? I am still new with buildship. pls advise thx
Solution:Jump to solution
Normally, Workflow Testing would be the way to go, but that's not quite supported for email triggers just yet. Of course, you could manually trigger the workflow by sending an email to see the result for yourself.
Apart from manually triggering the workflow normally, one thing you could do is this: Replace the email trigger with the "Rest API Call" trigger, which enables the "Workflow Testing" option for the workflow (you'll find the option on the top-right, next to the "Ship" and "Version history" buttons). But this would mean you'll need to change the variables you've used in your nodes (because of the new trigger), and then change them back when you reset your workflow back to normal. This could get tedious depending on how extensively the trigger variables are used.
Testing each individual node is also an option. You may do so by clicking on the "Play" button at the top of the node, on the right....
5 Replies
Hey there @Emmanuel, the output of a node within the assistant cannot be passed to other nodes manually by the user. Passing around node outputs (also called
tool_outputs) is something that the assistant node takes care of internally, using its own judgment. It makes these decisions based on the Instructions and User Prompt that you provide.
If you want to see the output of the assistant node as a whole, then you may access it in any node that is placed outside of it (as in, placed after the assistant node). Here's what that would look like (you can see the node sequence on the top-left for clarity):
Hope this helps.
Hi @nithinrdy Thank you for your response. This leads me another question how can I test email trigger workflows to see if it works accordingly?
Or is it best to test each individual node? thanks
Solution
Normally, Workflow Testing would be the way to go, but that's not quite supported for email triggers just yet. Of course, you could manually trigger the workflow by sending an email to see the result for yourself.
Apart from manually triggering the workflow normally, one thing you could do is this: Replace the email trigger with the "Rest API Call" trigger, which enables the "Workflow Testing" option for the workflow (you'll find the option on the top-right, next to the "Ship" and "Version history" buttons). But this would mean you'll need to change the variables you've used in your nodes (because of the new trigger), and then change them back when you reset your workflow back to normal. This could get tedious depending on how extensively the trigger variables are used.
Testing each individual node is also an option. You may do so by clicking on the "Play" button at the top of the node, on the right.
We'll keep you updated on the progress on Workflow Testing.
Thank you for the help, will play around to see if theres a work around. Looking forward to the update