Output Node
The Output Node is used to return values from the workflow. The Output Node is a crucial component in our workflow logic, designed to handle HTTP response codes and return a value upon its execution.
Output node can be used analogously as the Return Node (previously).
Configuring the Output Node
We can configure the Output Node by selecting different options from the Use
dropdown. The Output Node can return values from the following sources:
Last Node Output
The default configuration for the output node is to return the Last node output. There's no need to configure this setting, as it simply returns whatever the last node gives as the output.
Most of the use cases generally do not require a specific structure for the response to be returned. This setting is very useful for those cases - makes building super fast.
Tip: You can always make use of the Flow Testing feature to see what's being returned by your BuildShip Workflow. You can always modify the responses from the output node. Just make sure to re-configure the returned items in your Trigger configuration.
Custom Response
We can switch the configuration to use Custom Output from the dropdown options. You can use this setting to return exactly what you need from the workflow.
FEATURES:
-
Use AI Autofill to generate values using AI. For example: return the current timestamp
-
Create complex javascript expressions leveraging the context menu variables, like inputs, environment variables, local variables, and secrets.
For example, in case of the BuildShip Chatbot Widget which requires the message (the response for the Bot to respond with) and the Thread ID (to main chat history context).
We could add two output fields as shown below:
And map the workflow outputs to the trigger outputs in the set up like this:
Advanced Options
The Output Node also lets you set advanced configurations for the returned data, like the Status Code and Cache Time.
Status Code
We can set the HTTP Status code to return when the Output Node is executed. Supports a bunch of status codes for successes, and also failures which can be utilized in branching workflows.
200
: OK201
: Created202
: Accepted204
: No Content400
: Bad Request401
: Unauthorized403
: Forbidden404
: Not Found500
: Internal Server Error
Cache Time
The Output Node allows us to set the cache time for the response in the cache-max-age
response header. This is used by the browser to cache the response for the specified amount of time. This means that the caching would be handled by the browser and the response would be served from the cache if the cache time has not expired.
Video
Need Help?
- 💬Join BuildShip Community
An active and large community of no-code / low-code builders. Ask questions, share feedback, showcase your project and connect with other BuildShip enthusiasts.
- 🙋Hire a BuildShip Expert
Need personalized help to build your product fast? Browse and hire from a range of independent freelancers, agencies and builders - all well versed with BuildShip.
- 🛟Send a Support Request
Got a specific question on your workflows / project or want to report a bug? Send a us a request using the "Support" button directly from your BuildShip Dashboard.
- ⭐️Feature Request
Something missing in BuildShip for you? Share on the #FeatureRequest channel on Discord. Also browse and cast your votes on other feature requests.