What is your goal?the default for a scenario seems to be a webhook whereas when I work in Zapier their default seemed to be a trigger
What is the problem & what have you tried?none
Hey @learn2 !
In Make, scenarios don’t really have a single “default” trigger the way Zapier does. The first module simply defines how the scenario starts.
Webhooks are commonly used because they allow instant triggering from another app. But you can start a scenario with many other trigger types, such as watching new records, new emails, new rows in a sheet, and so on.
If you add a module like “Watch records,” “Watch emails,” or similar as the first module, that becomes the trigger for the scenario. Webhooks are just one of several starting options rather than the default requirement.
Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard
very informative reply thank you. I’m developing an ecommerce automation, my first module is watching. the latest row in a sheet shall I upload the blueprint or send a screenshot
The default for Make is a trigger as well. The first module in the flow is the trigger and will have an icon on the bottom left corner showing what type of trigger it is.
Webhooks are a type of triggers and can only be triggers, but not the only triggers available.
I see what you mean it feels different from Zapier and it took me a little while to understand it. Zapier has a more strict “trigger”→”Action” structure, Make is more flexible and module-based. Many app triggers in Make are implemented as webhooks because of the efficiency.
It is important to note that as one of the replies has mentioned you can basically start a Make scenario with almost any action. Schedulers are more common starting points because they control when modules check for new data. It is less that Webhooks are default and more that Make has multiple ways of starting a workflow depending on how you want it to run.
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
— @samliew
P.S.: investing some effort into the tutorials in the Make Academy will save you lots of time and frustration using Make!
