Open app

DocumentationWorkflowsApps and services

Excel node

Read or write cell ranges in an .xlsx file on OneDrive. Uses the Graph Workbook API. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.

8 min readUpdated

What this node does

Read or write cell ranges in an .xlsx file on OneDrive. Uses the Graph Workbook API.

Use Excel as a clearly defined step in an anymize workflow.

  • Processes one input.
  • Provides one output for following steps.
  • Runs as a regular step in the flow.

Set up the node

  1. 01Open a workflow and add Excel from the node catalog.
  2. 02Select your microsoft connection. You can create it directly in the workflow if needed.
  3. 03Complete the required fields and map values from previous steps.
  4. 04Run the node with a small test record and inspect its output.
  5. 05Connect the successful output and activate the workflow after an end-to-end test.

Operations and modes

Choose the required function in Action. The panel then shows the relevant settings.

  • Read range
  • Write range
  • Append row to table

Settings

FieldMeaningArea
ActionChoices: Read range, Write range, Append row to tableStandard
File ID (optional)The ID of the Excel file. Drag it in from a OneDrive step. Or leave the field empty and give a file path below.Standard
Drive-ID (optional)Configure this value in the node panel.Standard
File pathPath to the .xlsx in your OneDrive, e.g. Reports/Q2.xlsx. Only needed if there's no file ID above.Standard
WorksheetName of the sheet (the tab at the bottom of Excel), e.g. Sheet1 or Revenue.Standard
Cell rangeWhich cells, in Excel notation, e.g. A1:C10 for the first three columns and ten rows.Standard
ValuesThe cell values. When writing a range, a table (rows × columns); when appending, exactly one row. You can also drag values in from a previous step.Standard
Table nameGraph needs a named table for "append". In Excel: select → "Format as Table" → name in the top left.Standard
Run once per itemOff (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry.Standard
If one item fails"Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file.Standard
Pause between items (milliseconds)Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes).Standard

Inputs and outputs

InputMeaningType
StandardReceives the complete result from the previous step.JSON
OutputMeaningType
StandardMakes the result available to the next step as JSON.JSON

This node can process lists item by item. Error handling and the delay between items are available in advanced settings.

Example and test run

Append row to report: begin with a small, recognizable record. Inspect the output and only map fields that are present there.

Test-run example

{
  "file_path": "Reports/2026-Q1.xlsx",
  "worksheet": "Umsätze",
  "table": "UmsatzTabelle",
  "values": [
    "2026-04-19",
    1250.5,
    "Alice"
  ]
}

Access and security

This node uses a connected microsoft account. Review the requested permissions and grant only the required access.

Store keys and credentials in the protected connection manager. Never paste them into normal workflow fields, test data or descriptions.

Troubleshooting

  • No output: inspect the latest run and confirm that the previous node returned the expected fields.
  • Empty variable: open the previous step output and use a field name from the real test data.
  • Connection rejected: reconnect the service and grant the permissions required by this step.
  • List processed once: enable per-item execution in advanced settings.

Related articles