Make (Integromat) Review (2026): It Works — But Two Setup Traps Cost Us an Hour

We signed up for Make’s free plan (no credit card required) and built a simple real scenario: watch this site’s target RSS feed for new items, and send an email notification when one appears. This is a genuine building block for our own content pipeline, not a synthetic test.

Signup and builder experience

Onboarding was quick — a short wizard asked what we wanted to automate, which apps we use, and workspace size, then dropped us into the scenario builder. Adding the RSS “Watch RSS feed items” trigger and a Gmail “Send an email” action, and connecting them, took a few minutes. The visual builder is genuinely intuitive.

What actually went wrong (and the fix)

Getting the scenario to run correctly took about an hour of debugging, for two reasons:

1. A form validation bug that looked like a real error. Saving the Gmail module repeatedly failed with “Body type: Value must not be empty” — even though “Raw HTML” was visibly selected in the dropdown. The fix was re-opening the dropdown and re-selecting the same value before saving. This happened on two separate attempts to configure the same module.

2. Minimal OAuth scopes silently broke the integration. Following good security practice, we initially granted Make’s Gmail connection only the “send” scope, not the broader “view messages” scope. The scenario then ran with zero errors in the main execution log — the RSS trigger showed a successful checkmark, but the Gmail step never executed and no email arrived. There was no error visible anywhere in the standard run log.

The fix that actually surfaced the problem: right-click the Gmail module and use “Run this module” to test it in isolation, bypassing the trigger. That immediately returned a clear error: [403] Request had insufficient authentication scopes. The full-scenario log never showed this — it just reported the run as “completed.”

Re-authorizing with both scopes granted didn’t work on the first attempt either, because Google silently skipped the scope-selection screen on a second connection attempt (it appears to reuse a prior grant). We had to manually revoke Make’s access at myaccount.google.com/permissions to force a fresh consent screen with the checkboxes, then it worked immediately.

Takeaway: if a Make scenario “completes successfully” in the log but a downstream step visibly didn’t run, don’t trust the top-level log — right-click the suspect module and run it in isolation. And if you’re deliberately minimizing OAuth scopes for privacy reasons, expect some actions to fail silently rather than with a clear permissions error in context.

The free-tier trap that matters most

The free plan includes 1,000 operations/month, with no card required. That sounds generous, but polling triggers consume an operation on every check, whether or not new data is found. Left on the default schedule (every 15 minutes), the RSS watcher alone burns roughly:

4 checks/hour × 24 hours × 30 days ≈ 2,880 operations/month

— nearly triple the free allowance, from a single trigger with no actual output. Dropping the schedule to every 6 hours brings that down to roughly 120/month, comfortably inside the free tier. If you’re testing Make on the free plan, set the schedule interval deliberately before you forget about it — the default frequency is not free-tier-appropriate for a always-on trigger.

Bottom line

Make’s builder and free tier are real and usable — this wasn’t a paywall trick, and the automation now works correctly. But two things cost us real time: a UI validation bug on the Body type field, and the fact that insufficient OAuth scopes fail silently at the scenario level rather than with a visible error. Budget time for both if you’re setting this up yourself, and check your schedule interval before you walk away from a free-tier scenario.