Add new row in google sheet not working

:bullseye: What is your goal?

create automation where emails received is automatically included in google sheets

:thinking: What is the problem?

scenario is in green after run once, however excel sheet is not updating with the additional row

:test_tube: What have you tried so far?

tried sending a new email and restarting the scenario with no joy

:camera_with_flash: Screenshots: scenario setup, module configuration, errors

1 Like

Hello @Dammy_Faluyi,

Welcome to the Community!

The issue you’re experiencing is related to the trigger type you’re using.

The Watch Emails module is a polling trigger, which means it only checks for new data when the scenario runs according to its schedule- not in real-time.

You have two options here:

Option 1: Keep the current setup

Your scenario will work if you turn your scenario on, but emails will be added to Google Sheets with a delay depending on your schedule settings (e.g., every 15 minutes).

Option 2: Use an instant trigger

If you need real-time processing, consider creating a new scenario using the Custom Mailhook module.
You can forward incoming emails directly to the mailhook address, and the scenario will trigger immediately when a new email arrives- no polling delay.

Learn about triggers here: Types of modules - Help Center

Have a nice day,
Michal

2 Likes

Hi @Dammy_Faluyi ,

Please first check whether the Outlook – Watch Emails module is producing any output bundles. Confirm if the module is returning any bundles or not.

If it’s not returning any bundles, right-click on the module and select “Choose where to start” (please refer to the link

where I explained this step in detail for the Gmail module - the same approach applies to the Outlook module as well).

I’m also attaching a sample scenario blueprint that shows how the flow should work. Kindly refer to it and let me know if you face any issues.
[COMMUNITY] -TEST.blueprint(2).json (42.8 KB)

Best regards,
Msquare Automation
Platinum Partner of Make
@Msquare_Automation

Welcome to the Make community!

Polling Triggers & Empty “Check Runs”

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.

  • 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.

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,

Polling Triggers: Selecting Older Data Using Epoch Panel

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).


Above: A screenshot of a polling trigger module’s Epoch Panel

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! If you are still having trouble, please provide more details.

— @samliew

1 Like