Integration: Export to Google Sheets
The Export to Google Sheets node allows automatically adding data collected in your forms directly to Google Sheets spreadsheets, with no manual intervention. Every time a workflow instance passes through this node, a new row is inserted in the configured spreadsheet with the information you choose to map.
This integration is ideal for teams that need to accumulate a response history over time, consolidate data from multiple forms in a single tracking spreadsheet, or feed dashboards and reports that already exist in Google Sheets.
Since it is a SINGLE_OUTCOME type node, the workflow advances automatically after the export, regardless of the result. There is no success or error branching: the flow always continues to the next connected node.
Prerequisite: Configure Google Sheets Connection
Before using this node, you need to configure an OAuth connection with Google on the Hashdata platform. This connection authorizes Hashdata to create and edit spreadsheets on behalf of your Google account.
To configure the connection:
- Access the Settings menu in the side panel.
- Navigate to the Integrations section.
- Click New Connection and select Google Sheets.
- Follow the Google OAuth authentication flow: log in with your Google account and grant the requested permissions.
- After authorization, the connection will appear in the list of available integrations and will be ready to be used in any Export to Google Sheets type node.
During the OAuth flow, Google will request permission to create and edit spreadsheets. These permissions are necessary for the node to work in both available operation modes.
Operation Modes
The Export to Google Sheets node offers two operation modes, each suited to a different scenario:
Mode "New Spreadsheet"
In this mode, Hashdata automatically creates a spreadsheet in Google Drive on the first execution of the workflow. From the second execution onward, new rows are inserted in the same spreadsheet created previously, accumulating data from all instances.
This mode is especially useful when you want Hashdata to manage the entire spreadsheet lifecycle: creation, column structuring, and continuous data insertion over time.
Mode "Existing Spreadsheet"
In this mode, you select a spreadsheet that already exists in your Google Drive. With each execution, Hashdata inserts a new row in the configured tab. The spreadsheet must already exist and the indicated tab must also be created.
This mode is suitable when you already have a structured spreadsheet and just want to feed it with workflow data, without creating new spreadsheets.
If your goal is to build a history of all responses received over time, New Spreadsheet mode is the most practical choice. You don't need to create or configure anything in Google Drive in advance: Hashdata takes care of everything on the first workflow execution.
Configuration — New Spreadsheet Mode
When selecting New Spreadsheet mode, the following configuration fields are available:
| Field | Description | Required |
|---|---|---|
| Google Sheets Connection | Select the Google OAuth connection configured in the Space integrations. This connection determines which Google account the spreadsheet will be created in. | Yes |
| New spreadsheet name | Name that will be assigned to the spreadsheet created on the first execution. Supports fixed text. Examples: "Onboarding Form Responses" or "Orders 2025". | Yes |
| Destination folder | Folder in Google Drive where the spreadsheet will be created. If not specified, the spreadsheet will be saved at the root of the connected account's Drive. | No |
| Tab name | Name of the tab (sheet) within the spreadsheet where data will be inserted. Examples: "Responses", "Sheet1", "Data". | Yes |
| Column mapping | List of Header → Value pairs. The header is the exact column name in the spreadsheet. The value can be a workflow variable ({{field_name}}) or fixed text. | Yes |
In New Spreadsheet mode, the spreadsheet is created only once, on the first workflow execution. All subsequent executions add new rows to that same spreadsheet. This ensures all data is centralized in a single file, without creating duplicate spreadsheets for each new instance.
Configuration — Existing Spreadsheet Mode
When selecting Existing Spreadsheet mode, the following configuration fields are available:
| Field | Description | Required |
|---|---|---|
| Google Sheets Connection | Select the Google OAuth connection configured in the Space integrations. Must be the same account that has access to the spreadsheet you want to use. | Yes |
| Existing spreadsheet | Select the destination spreadsheet from a list of spreadsheets available in the connected Google account. The spreadsheet must exist before configuring the node. | Yes |
| Tab | Name of the tab (sheet) within the selected spreadsheet where data will be inserted. The tab must already exist in the spreadsheet. | Yes |
| Column mapping | List of Header → Value pairs. The header must match exactly the name of the already existing column in the spreadsheet. The value can be a variable ({{field_name}}) or fixed text. | Yes |
In Existing Spreadsheet mode, both the spreadsheet and the indicated tab need to exist in Google Drive before the first workflow execution. If the tab is not found, the export may fail silently or insert data in an unexpected location.
Column Mapping
Column mapping is the heart of the node configuration. It defines which data will be exported and to which spreadsheet columns.
Each mapping entry consists of two fields:
- Header: the exact column name in the Google Sheets spreadsheet. This value must precisely match the column header, including uppercase, lowercase, and spaces.
- Value: the content that will be inserted in that column. Can be:
- A workflow variable, in the format
{{field_name}}, referencing ancestor form responses. - Fixed text, such as a department name, a static identifier, or any other constant value.
- A workflow variable, in the format
Native type behavior
- Numeric fields are sent as numbers, allowing Google Sheets to perform calculations directly on them.
- Date fields are sent as dates, preserving formatting and enabling period filters.
- Yes/no response fields are sent as booleans (true/false).
Mapping examples
| Header | Value | Result in spreadsheet |
|---|---|---|
| Name | {{full_name}} | Text with the name responded in the form |
| Submission date | {{submission_date}} | Date formatted in Google Sheets native type |
| Proposal value | {{proposal_value}} | Number ready for calculations and totals |
| Approved | {{approved}} | Boolean (TRUE / FALSE) |
| Origin | Sales Portal | Fixed text in all rows |
| Identification | Order #{{order_number}} | Combined text, e.g., "Order #1042" |
Positioning in the Workflow
The Export to Google Sheets node can be positioned at any point in the flow where there is relevant data available to export. Some common usage suggestions:
- After a collection form: immediately export the newly collected data to a control spreadsheet.
- After an approval: record the approval result along with the original form data.
- At the end of the workflow: consolidate all data processed throughout the flow in a final report in Google Sheets.
- In workflows with scheduled trigger: combine with the Scheduled Trigger for periodic and automatic exports.
Tips and Best Practices
- Name your columns clearly: use descriptive names in the headers so that the generated spreadsheet is understandable to anyone on the team, even without technical knowledge of the workflow.
- Prefer isolated variables for numeric and date fields: this preserves the native type and allows Google Sheets to correctly process data in formulas, charts, and filters.
- Maintain one connection per Google account: if you have multiple workflows exporting to spreadsheets from the same account, use the same OAuth connection to facilitate management.
- Combine with other export nodes: use the Export to Google Sheets node in parallel with the Send Email node to notify the team while data is automatically recorded in the spreadsheet.