The New Spreadsheet Row trigger reads the data in each row of a given Google Spreadsheet and passes it to the next stage of your integration flow.
Input field | Required | Description | Example |
---|---|---|---|
Spreadsheet | true | Spreadsheet which will be used for data reading | MyTestSpreadsheet |
Worksheet | true | Worksheet of spreadsheet which will be used for data reading | Sheet1 |
Dimension | true | The major dimension of the values | ROWS , COLUMNS |
Use first row/column as header | true | You should specify Yes if your data has a header in the first row/column and you want to use these values as json key in the output message. If you specify No, json key will be taken from row/column index according to A1 notation. Se example below | Yes |
Select All Data | true | You should specify Yes if you want to fetch all spreadsheet data whenever step starts. If you specify No, a step will be emitting only delta changes (lines which were added after last step runs) | No |
IMPORTANT: Using
Use first row/column as header
feature, you must be sure that header values are unique.
Values from spreadsheets return as UNFORMATTED_VALUE
type
First, the system reads all the rows from a given Google Spreadsheet and processes it further along with your designed integration flow. It will also create an initial state of your spreadsheet, we call it a snapshot, in order to have something to compare with after your data is updated.
After the initial read, any further requests for an update will be compared to this
snapshot and in case any changes are detected they will be passed along with the integration
flow as well. If Select All Data
configuration property has value Yes
, the system will read all the rows from a given Google
Spreadsheet whenever flow processes the message.
After a trigger execution, data will be extracted from the table above and the following message will be emitted:
ROWS
, Use first row/column as header: Yes
{
"FirstName": "Tom1",
"LastName": "Smith1"
}
{
"FirstName": "Tom2",
"LastName": "Smith2"
}
-----------------------
{
"FirstName": "Tom10",
"LastName": "Smith10"
}
ROWS
, Use first row/column as header: No
{
"A": "FirstName",
"B": "LastName"
}
{
"A": "Tom1",
"B": "Smith1"
}
{
"A": "Tom2",
"B": "Smith2"
}
---------------------
{
"A": "Tom10",
"B": "Smith10"
}
After a trigger execution, data will be extracted from the table above and the following message will be emitted:
COLUMNS
, Use first row/column as header: Yes
{
"FirstName": "Tom1",
"LastName": "Smith1"
}
{
"FirstName": "Tom2",
"LastName": "Smith2"
}
-----------------------
{
"FirstName": "Tom10",
"LastName": "Smith10"
}
COLUMNS
, Use first row/column as header: No
{
"1": "FirstName",
"2": "LastName"
}
{
"1": "Tom1",
"2": "Smith1"
}
{
"1": "Tom2",
"2": "Smith2"
}
---------------------
{
"1": "Tom10",
"2": "Smith10"
}
Trigger can emit maximum 1000 messages per one execution.
Trigger uses version 4 of Google Sheet API. You can find more information in the Google Sheets API Documentation.
Trigger is deprecated
- please use Get Spreadsheet Row trigger.
The Rows trigger reads the data in each row of a given Google Spreadsheet and passes it to the next stage of your integration flow.
In the beginning, the system will read all the rows from a given Google Spreadsheet and process it further along with your designed integration flow. It will also create an initial state of your spreadsheet, we call it a snapshot, in order to have something to compare after your data is updated.
After the initial read, any further requests for an update will be compared to this snapshot and if any changes are detected they will be passed along the integration flow as well. It is, therefore, imperative to provide a readable spreadsheet for smooth integration.
The nature of API that the platform uses to read the rows in Google Spreadsheets dictates the use of certain rules that it is useful to follow for a smooth integration of your data. In addition to the Minimum Requirements your spreadsheet must have:
STRING
values - Your data will be processed as a STRING
data type.VALUE
of that field and convert it into a STRING
data type.When any given row is processed by the system it receives a unique name or a unique ID so that it can be recognized by the system afterward if you want to make any changes to the values in that specific row.
In our system the row number in the Google Spreadsheet is taken as a unique ID to process through the integration flow.
Click here to learn more about the elastic.io iPaaS