I am currently learning to work this Make.com and think that is a great alternative to Zapier. But there is one thing I don’t understand. Is there an equivalent to Zapier’s instant triggers? I can only see these triggers:
As far as I understand this, you only can run Workflows in Make manually (“On demand”) or at a specific event (specific day, specific time etc.). In Zapier every Zap is run through in the same moment when when your condition is triggered (for example in the moment someone books an appointment in calendly, something is done). As far as I understand Make’s triggers, this is not possible. Is this true? I think Zapier’s solution is far more convenient.
Did you forget to turn on your scenario? If it’s already on, then it might be a bug.
For quicker assistance with bugs and technical problems, you may want to contact support directly. They respond very quickly and update you frequently on the status of their investigation.
Hope you can share the resolution with us if you manage to solve this problem!
I defintely turned on my scenario. I tried this with two different triggers and in both cases I have to press run manually, even if the scenario is turned on.
I don’t think that’s true. It depends on the trigger and (if I’m not mistaken) on your plan. There are definitely instant (on demand?) triggers in Make…
Okay, I guess it has something to do with my plan. I am currently on a free version and it does not work as I want. So I guess you must have the premium version.
This is because the “Watch Cards”/“Watch Messages” modules are 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.
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.
All types of features are available on all plans – they are not locked behind a paid plan, except for one Premium app (Twitter/X). So being on the Free plan already allows you to try out most of what Make has to offer. For more details about features, see the pricing page https://www.make.com/en/pricing
