Integration: Export to Excel 365 (Microsoft)
The Export to Excel 365 node allows your workflow to automatically add data rows to Excel spreadsheets stored in OneDrive. With each workflow execution, a new row is inserted in the configured spreadsheet, consolidating information collected in forms and other previous nodes.
The behavior of this node is identical to the Export to Google Sheets node, but operates entirely within the Microsoft ecosystem: files are created and stored in OneDrive, and authentication is done with a Microsoft 365 account. If you already know the Google Sheets node, you will feel immediately at home with this one.
The Export to Excel 365 node works exactly the same way as Export to Google Sheets. The only difference is that it uses your Microsoft 365 account and stores files in OneDrive instead of Google Drive. All the logic of modes, column mapping, and output is equivalent.
This node has a single output: it always advances to the next step, regardless of the export result.
Prerequisite: Configure Excel 365 Connection
Before using this node in any workflow, you need to connect your Microsoft 365 account to the Hashdata platform. This connection is made once and is available for all workflows in your space.
How to configure the connection:
- Access Settings in the side menu.
- Click on Integrations.
- Click on New connection.
- Select Excel 365 from the list of available integrations.
- Click Connect with Microsoft.
- A Microsoft OAuth authentication window will open. Log in with the Microsoft 365 account that has access to the OneDrive where the spreadsheets will be stored.
- Authorize the permissions requested by Hashdata (read and write to OneDrive files).
- After authorization, the connection will appear in the integrations list with Active status.
The Microsoft account used in the connection needs to have read and write permission to the destination OneDrive. If the account does not have sufficient access, the node will fail silently or will not be able to create/edit the spreadsheet.
After configuring the connection, you will be able to select it when configuring the node within any workflow.
Operation Modes
The Export to Excel 365 node offers two operation modes, suited to different scenarios:
Mode: New Spreadsheet
In this mode, Hashdata automatically creates a new Excel spreadsheet (.xlsx) in OneDrive on the first execution of the workflow. In subsequent executions, new rows are added to that same spreadsheet, which accumulates all records over time.
When to use: Ideal when you don't yet have a spreadsheet created and want Hashdata to manage that for you. Just define the spreadsheet name, tab name, and column mapping.
Mode: Existing Spreadsheet
In this mode, you point to an Excel spreadsheet that already exists in your OneDrive. Hashdata adds a new row with each workflow execution, always at the end of the spreadsheet.
When to use: Ideal when you already have a spreadsheet with formatting, formulas, or other data you want to preserve, and want the workflow to only insert new rows into it.
Configuration — New Spreadsheet Mode
When adding the node to the canvas and selecting New spreadsheet mode, the following configuration fields will be available:
| Field | Required | Description |
|---|---|---|
| Connection | Yes | Select the Microsoft 365 connection previously configured in Settings → Integrations. |
| Spreadsheet name | Yes | Name of the Excel file that will be created in OneDrive on the first execution. For example: Sales Form Responses. The file will automatically receive the .xlsx extension. |
| Tab name | Yes | Name of the tab (internal sheet) where data will be inserted. For example: Data or Responses. |
| Destination folder in OneDrive | No | Path of the folder in OneDrive where the file will be created. If not specified, the file will be saved at the root of the connected account's OneDrive. |
| Column mapping | Yes | Defines which data will be exported and to which column. See the Column Mapping section below. |
Choose a descriptive and unique name for the spreadsheet, especially if you have multiple workflows exporting data. This makes it easier to identify files in OneDrive.
Configuration — Existing Spreadsheet Mode
When selecting Existing spreadsheet mode, the configuration fields are:
| Field | Required | Description |
|---|---|---|
| Connection | Yes | Select the Microsoft 365 connection previously configured in Settings → Integrations. |
| Spreadsheet | Yes | Select the existing Excel spreadsheet in the connected account's OneDrive. The list displays available .xlsx files. |
| Tab | Yes | Select the tab (internal sheet) within the file where new rows will be inserted. |
| Column mapping | Yes | Defines which data will be exported and to which column. See the Column Mapping section below. |
In Existing spreadsheet mode, the spreadsheet must have a header row in the first row of the selected tab. Hashdata uses the column header names to identify where to insert each piece of data.
Column Mapping
Column mapping is the heart of the node configuration. Here you define the correspondence between the spreadsheet column headers and the variables available in the workflow.
How it works:
Each mapping row represents a spreadsheet column. You define:
- Header: The exact column name in the spreadsheet (must match the existing header, or will be created with that name in New spreadsheet mode).
- Value: The workflow variable that will provide the data for that column. Use the
{{field_name}}syntax to reference form responses or other data available in the flow.
Mapping example:
| Column header (spreadsheet) | Value (workflow variable) |
|---|---|
| Customer Name | {{full_name}} |
{{email}} | |
| Product of Interest | {{selected_product}} |
| Submission Date | {{response_date}} |
| Observations | {{free_text_field}} |
Available variables depend on the nodes that precede this one in the workflow. Answered forms, approval data, and other previous nodes feed the set of accessible variables.
In New spreadsheet mode, columns will be created in the order you defined them in the mapping. Organize the mapping in the order you want the columns to appear in the spreadsheet.
Differences from Google Sheets
For those already using the Export to Google Sheets node, migrating to Excel 365 is straightforward. The differences are only platform-related:
| Aspect | Google Sheets | Excel 365 |
|---|---|---|
| Authentication account | Google account (Gmail / Google Workspace) | Microsoft 365 account |
| File storage | Google Drive | OneDrive |
| File format | Google Sheets native (.gsheet) | Excel (.xlsx) |
| Connection configuration | OAuth with Google account | OAuth with Microsoft account |
| Operation modes | New spreadsheet / Existing spreadsheet | New spreadsheet / Existing spreadsheet |
| Column mapping | Identical | Identical |
| Node output | Single (always advances) | Single (always advances) |
| Cumulative behavior | Yes, rows added at the end | Yes, rows added at the end |
The operating logic, modes, and column mapping are completely equivalent between the two nodes. The choice between one and the other depends only on which productivity platform your organization uses.
Usage Example
Imagine a lead registration workflow where a form collects information from potential customers. After submission, the workflow can:
- Send a confirmation email to the lead with the Send Email node.
- Export the lead data to an Excel spreadsheet in OneDrive with the Export to Excel 365 node.
- Notify the sales team via Send Teams Message.
With this flow, your sales team has access to an always-updated spreadsheet in OneDrive, consolidating all leads captured by the workflow automatically.
Node Output
The Export to Excel 365 node has a single output. It always advances to the next connected node, regardless of the export result. There is no separate error output in this node.
If a problem occurs during export (for example, loss of connection to the Microsoft account or insufficient permissions), the error will be recorded in the workflow instance details. Check the execution history tab to diagnose any failures.