I need to detect when a new row is created, obtain the information and with that create a Google Docs from a template.
Everything goes fine when I first execute the program, every single row is read and a Google Docs is created, the problem is once the first set of items are done, when I want it to work with a new Row created, it just wont detect the new row and will appear as 0 watch new rows result.
Hey @K_y_G_Eventos,
Have you looked into your scenario schedule settings? It seems that you are running it on schedule now, it should check every 15 minutes (or whatever interval you’d like) if a new row is added. Have you looked into this?
Also, note that this is an ACID module, for more information and understanding about it, I refer to Make Academy courses which are very helpful in understanding these modules.
Hope this helps - VDW Intelligence
Hi @K_y_G_Eventos Welcome to the community!
Ideally it should work but it will be great if you update the mapped sheet name again as when you change sheet name in google sheet, it might not work as it need to be reselected in Make.
Another way to do this is Using search row module with a status column in sheet. Like having status like GET to search new rows by default and DONE for successful execution. you can select GET in status column for every new row you add and at the end of the scenario once all tasks are done using update a row module with row number from search a row, update that row with DONE. So whenever scenario runs again, it will load all rows with GET status.
I hope this helps!
Best,
@Prem_Patel
I thought something similar, the rest of my program does that, removing the Row from the first sheet and transfering into another Sheet, deleting the first record. But it only works once and after that it wont do it again.
I tried your first suggestion about updating the mapped sheet and it didn’t help.
Found that if I right click the first module and select where to start “All” it will detect, is there any way to always trigger where to start “All”
I don’t think apart from Search Rows with a filter with any column value that exists can list all rows. You can try Apps Script to send data to make.com webhook when there is a new row. you can define conditions as well. But it is very unlikely that make can’t detect new rows added.
Make sure you are following these things:
Check if there are any hidden empty rows? If exists, delete those!
I think Make only lists new rows which are added just after the last row fetched which contains the data. Make doesn’t catch new rows which are added after an empty row. So make sure you are not having any empty rows in between the new rows.
Welcome to the Make community!
This is because the module is a POLLING trigger, and not an INSTANT (Webhook) trigger.
If you don’t see any bundles from the trigger module and operations on the rest of the modules, it means there are no new responses (empty output bundle) when the scenario ran to check for new items. This is called a “Check run”.
There are two main types of triggers, Polling (scheduled), and Instant (webhooks). Polling triggers can only run on a schedule. Instant triggers can be run as soon as data is received by the webhook.
The module you are using does not push changes — it’s basically a API request that Make has to occasionally “call” to fetch the latest changes/items.
To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make Help Centre.
If you want your scenario to only run when there is new data (and not on a schedule or timed interval), see if your app has an “Instant” or “Webhook” trigger in Make. If not, check if the third-party service has a feature that can send out a webhook when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.
If you want to re-run your scenario on older data,
Go to the Epoch Panel, by right-clicking on the trigger module (polling triggers only), and select “Choose where to start” from the list of options in the context menu.
If you select “From now on”, the next time the scenario runs it will only return new data (or nothing if there is no new data).
You can also select other old data to re-run your scenario with next using the “Choose manually” option. This will then show you a list of previous historical items you can select to process the next time the scenario is triggered.
For more information, see
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
