Update row not working for google sheets after watch new rows trigger

How To
1

Hello

I am having a problem when trying to run a complete scenario.
The update row works when running the module individually. However does not work when running the complete scenario.

The trigger is working fine, but the update row does not work when a new row is added, when the scenario is activated.

Screenshot2
Screenshot2821Ă—273 18.2 KB

blueprint.json (35.6 KB)

I hope the attachment above helps

Thanks

2

This is because the module is a POLLING trigger, and not an INSTANT (Webhook) trigger.

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.

Polling means Make checks external service for changes (pull changes to Make).
Webhook (instant) triggers means external service calls Make when there are new changes (push changes to Make).

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.

So, when you manually “Run Once” on the scenario, there are no changes to be fetched. You need to add the new row first, THEN run the scenario (or wait for the schedule to be triggered).

To find out more on the different types of Trigger modules, see refer to Types of Modules and Webhooks sections of the Make help center.

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 webhooks when content is created/updated - and then you can point it to a “Custom Webhook” trigger in your scenario.

3

Thanks for the response

The trigger works.
The first module runs when a new row is added. This module is triggered when a new row is added to the google sheet.

The second module does not update the row when a new row is added to the google sheet.

4

Hello @John_Doe,

Please show the input and output of your Update a Row module after it runs.

Also, you can install the Make/Integromat Dev Tool and use Scenario Debugger to see what the module is doing to get more information.

1 Like
5

Hello Donald

Input bundle.txt (356 Bytes)
Input bundle.txt (356 Bytes)

I hope the bundles help.
They are from running the module individually.
I cannot get any input and output bundles when the scenario runs as the update row does not run.

6

When the scenario is run automatically
The following is from the google watch rows trigger that runs
input bundle:

Output bundle:
[
null
]