Outputs

Terminal nodes that deliver results — notifications, database writes, file exports, dashboards.

Overview

The Outputs group holds terminal nodes — the last step in a pipeline branch. These nodes consume upstream data and deliver it somewhere useful: a notification, a database write, a file export, or a visual dashboard. Output nodes have no outgoing connections.

Nodes are organized into sub-groups: Display, Notification, Publish, Data Sinks, API & Action, File, and Generic.

Nodes in This Group

Display

Node	Description
Modal View	Displays upstream data in a viewer modal within the editor.
Airtable View	Displays upstream data formatted as an Airtable-style grid.

Notification

Node	Description
Notification Router	Routes a notification to one or more configured channels based on rules.
Email Alert	Sends an alert email when the workflow reaches this node.
Slack Alert	Posts an alert message to a Slack channel.
Linear Issue	Creates or updates a Linear issue from upstream data.
Push Notification	Sends a push notification to subscribed devices.
Send Mail	Sends an email using upstream content as the body.

Publish

Node	Description
PR Comment	Posts a comment on a pull request in a connected repository.
Social Publisher	Publishes upstream content to a connected social media account.
Blog Post	Publishes upstream content as a blog post.

Data Sinks

Node	Description
Database Insert	Inserts upstream data as a new row/record in a connected database.
Spreadsheet	Writes upstream data to a spreadsheet.
Dashboard	Sends upstream data to a dashboard widget.

API & Action

Node	Description
HTTP Request	Sends a final outbound HTTP request with the upstream payload.
Vector DB Upsert	Writes upstream embeddings/records into a vector database.
Webhook (Out)	Sends upstream data to an external webhook URL as the final pipeline step.

File

Node	Description
File Write	Writes upstream data to a file on local/persistent disk.
CSV Export	Exports upstream tabular data as a CSV file.
JSON Export	Exports upstream data as a JSON file.

Generic

Node	Description
Output	A generic terminal node for displaying or forwarding the final pipeline value with no specific destination.

Usage Tips

A pipeline can have multiple Output nodes

Branch a pipeline with a Condition or Switch node and attach a different Output node to each branch — e.g. Email Alert on failure, Database Insert on success.

Output nodes are terminal

Nothing can connect downstream of an Output node. If you need to both save data and notify a channel, use two separate Output nodes fed from the same upstream node rather than chaining one Output into another.

Frequently Asked Questions

What's the difference between HTTP Request in Integrations and in Outputs?

They behave the same way — both send an HTTP request. The Outputs version is positioned as a pipeline-ending action, while the Integrations version is commonly used mid-pipeline when you still need the response for further processing.

Does Modal View persist data anywhere?

No. Modal View only displays the upstream value in the editor UI for inspection — it does not write or store data anywhere. Use a Data Sinks node if you need persistence.