The Output node is where a workflow delivers its result. One node, several delivery types: show the result on screen, save it to a database table, expose it as a shortcode or HTML, POST it to a webhook, or write it to Google Sheets or Google Drive.
What it does
- Displays the workflow result on screen.
- Saves the result to a database table.
- Exposes the result as a shortcode or HTML you can embed.
- Sends the result to a webhook URL.
- Writes the result to Google Sheets or Google Drive.
Output types and where they run
The output type controls both what happens and where it runs:
- Display and Webhook can run in Cloud.
- Save to database and HTML shortcode run on your WordPress site.
- Google Sheets and Google Drive run Locally only, using your connected Google account.
Configuration reference
| Field | Applies to | What it does |
|---|---|---|
| Output type | All | display, save, html, webhook, googleSheets, or googleDrive. Defaults to display. |
| Delay | All | Wait before delivering, in minutes, hours, or days. |
| Selected table, columns, field mappings | Save | The target table and how node inputs map to its columns. |
| Webhook URL, webhook keys | Webhook | The target URL and the key mapping for the payload. URL supports variable tags. |
| Spreadsheet, sheet tab, column mappings | Google Sheets | The spreadsheet, tab, and how inputs map to columns. |
| Drive folder, file name, file format | Google Drive | The target folder, file name, and format: txt, docx, csv, or pdf. |
Mapping fields
For Save and Google Sheets, each column maps to its own upstream field, the same rules as the Post node. For Display and Webhook, a single [Input from upstream] block is fine. See Data flow and variables.
Cost
The Output node costs 0 credits. It is a workflow endpoint, so it has no output of its own.
Related
- Save to Database and custom tables
- Post node
- Data flow and variables
Was this helpful?
Contact us