Sheets Row Repeater
This task will loop or iterate through the rows of a spreadsheet in Google Sheets, running the sub-tasks contained within this task for each row that is processed.
To add sub-tasks, drag and drop tasks from the task library onto this task. The sub-tasks are displayed as child nodes of the Sheets Row Repeater task.
Settings
Google Workspace Connection
Required
The Google Workspace connection to use. See the Connecting to Google Workspace article if you require more information on how to create/manage connections.
First Row Is Header
Required
Determines whether the task should treat the first row in the selected range as a header row. Defaults to False.
When set to True, the task won't include the first row in the output, but the values from it will be used as the column names. If a cell in the first row is empty, it will fall back to a default column name as described below.
When set to False, the task will output all rows in the selected range, and columns will be assigned a default name in the form Column1, Column2 etc.
Range
Required
Specify the sheet name and/or range of cells to export, using either A1 or R1C1 notation. E.g. Sheet1!A1:B2. Defaults to Sheet1, which will select all data from the worksheet called 'Sheet1'.
Spreadsheet ID
Required
The ID of the spreadsheet to export. This can be found in the URL of the spreadsheet.
Zynk Settings
Context Variables
For every row in the selected range of the spreadsheet, the values in each cell are available to the sub-tasks as a current variable. If the 'First Row Is Header' setting is set to True, the variable names will correspond to the values in the first row. Otherwise, the variables will be named based on the column's position e.g. Column1, Column2, Column3 etc.
The sub-tasks can access the values of the variables using razor, so they can be used in templates, or within task settings that support Zynk Objects. For example @(Context.Current["Column1"]) would be used to access the first value in a row when 'First Row Is Header' is set to False.
See Accessing Variables in Tasks for more information on using context variables.