Step 5. Set up the trigger

at this step, you'll set up your google sheets trigger to watch for new rows in your spreadsheet you'll specify which spreadsheet to monitor and how many rows to process at once to set up your google sheets trigger select your drive from the dropdown menu you can leave the search method field at its default setting ("search by path") in the spreadsheet id field, click "click here to choose file" search for and select the "prospects" spreadsheet you created during step 2 select "sheet1" in the sheet name field this specifies which sheet contains the rows you want to monitor for table contains headers , select "yes" this tells make that the first row contains column names, which you'll use for mapping data later for row with headers , leave the default "a1\ z1" value this indicates where your column headers are located set the limit to 20 this tells the module to process up to 20 new rows in a single run you can adjust this based on your needs click save this saves your module settings, but not the entire scenario remember to click the save icon in the scenario builder toolbar to save your entire scenario it's good practice to save your scenario regularly as you build it in the choose where to start window that appears, select "all" if you accidentally close that window, right click the google sheets module and select choose where to start from the menu the "choose where to start" option determines which rows the module will process by selecting "all," the module will first process the existing rows in the sheet, and then any new rows added afterwards also, the module will track which rows it has already processed and only fetch the ones it hasn't processed yet your google sheets trigger is now configured to detect new rows in your prospects spreadsheet next, you'll test the module to ensure it works properly understanding trigger modules trigger modules like the one you've just configured can only be used at the beginning of scenarios they process data when specific events occur in connected applications there are two main types instant triggers start your scenario immediately when an event occurs in the connected application (marked with an "instant" tag in make) these are ideal when you need real time responses polling triggers (like your google sheets module) check for new data at regular intervals when your scenario runs the module remembers what it has already processed and only retrieves new items each time the google sheets "watch new rows" module you're using is a polling trigger, which will check for new rows each time your scenario runs