Gmail watcher

How To
1

I am trying to create a simple email watcher that will parse the text in the email and create variables. ( via regex) the watcher has a simple gmail filter from myemail@company.com

I have created a simple workflow but when i click the run one it seems to run through the e mail watcher step within seconds…

the steps i am taking are

  1. run once
  2. send test e mail

I cant work out why the first step runs and completes so quickly without waiting for the trigger e mail to arrive

any idea or help would be the great…

as a bit of context … the e mail contains details about a new starter. It should parse the content and then create a new user in google workspace

3

Hey there,

what type of trigger are you using?

4

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: Epoch Panel & Selecting 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.

260×187 11.7 KB

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

450×247 13 KB

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

So, for polling triggers, the item needs to be created first, THEN you can check for new data. Simply reverse the order of your two steps!

Hope this helps! If you are still having trouble, please provide more details.

— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!