Foliot vs Make: a simpler Make alternative

Make is a capable visual automation tool with thousands of apps and a low entry price. Foliot is much smaller and simpler: three triggers, nine steps, and one way to count usage. This page compares them plainly, including where Make costs less.

At a glance

Prices checked on October 15, 2026, on Make's pricing page (annual billing, at 10,000 credits a month) and Foliot's own. Prices in USD, before tax.

What a typical workflow costs

A webhook arrives, a filter checks it, then it adds a row to Google Sheets and posts to Slack, 2,500 times a month.

• Make: reading the webhook, adding the row and posting the message are one credit each. Make's filters sit between modules, so we've assumed they're free; even if not, that's 3 to 4 credits a run, or 7,500 to 10,000 credits a month. That fits Core at 10,000 credits: $9/month billed annually.
• Foliot: 2,500 runs, over the free plan's 500, so Pro at $12/month, with room for 7,500 more runs.

So for this workflow, Make costs less. The picture changes as workflows grow: each extra module adds credits on Make, and loops use a credit for every item they handle. Foliot's bill stays the number of times the trigger fires. If you value knowing the bill in advance over the lowest possible price, that's the trade.

When Make is the better choice

• Price at low and steady volumes. Core is $9 a month for 10,000 credits on annual billing.
• You need app triggers and ready-made modules. Make connects to 3,500+ apps; Foliot starts only from a schedule, a webhook or its own form, and reaches other apps through their APIs.
• You build large, data-heavy scenarios with routers, iterators, aggregators and data stores. Make's canvas is built for that.
• You want AI agents or AI steps in your automations.
• You need Python or longer-running code.

When Foliot is the better choice

• You found Make overwhelming for simple jobs. Foliot's steps are named for what they do (Send email, Delay, Only continue if…), and the canvas lays itself out.
• You want the bill to be predictable. One run per trigger firing, however many steps or loop items. No per-module math.
• You need frequent schedules on a free plan. Foliot schedules can run every minute on every plan (each run counts toward your monthly runs). Make's free plan runs at most every 15 minutes.
• You want code on the free plan. Foliot's Code step is on every plan; Make's Code App isn't included on Free.
• Your jobs are webhook, form or schedule driven and end in Google Sheets, Slack, email or an API call.

Switching from Make

There's no import; you rebuild each scenario. The main pieces map like this:

• Custom webhook → When a webhook is received; scheduled scenario → On a schedule.
• Filters → Filter; Router with two routes → Branch (a Yes and a No path); Iterator → For each (up to 100 items); Sleep → Delay.
• HTTP module → HTTP request; Google Sheets “Add a row” → Add row to Google Sheets; Slack and email modules → Post to Slack and Send email.
• Modules for other apps → an HTTP request to that app's API.

Point each webhook sender at the new Foliot URL, test each step, turn the workflow on, then turn the scenario off.