ForwardThis
ForwardThisvsmake

ForwardThis vs Make

Make and ForwardThis solve different problems. Make runs scenarios you design on a visual canvas, and the same scenario fires the same way every time it triggers. ForwardThis has nothing to design: you forward an email, write what you need, and it happens. If your work repeats exactly and needs branching logic, you probably want Make. If it arrives by email and looks a little different every day, you want ForwardThis.

ForwardThis and Make, side by side

How it works

MakeYou design scenarios on a canvas: modules and routes
ForwardThisYou forward an email with instructions. Nothing is built

Setup

MakeEach scenario is designed and tested before it runs
ForwardThisNone. Sign up, verify your email, forward

Runs without you

MakeYes. Schedules, webhooks and watching modules
ForwardThisNo. It only acts on emails you send it

Pricing unit

MakePer credit: every module run of every scenario counts
ForwardThisPer action: one email is one action, back-and-forth included

Free plan

Make1,000 credits a month, two active scenarios
ForwardThis10 actions a month, every feature

Paid from

Make$9 a month (annual) for 10,000 credits
ForwardThis$15 a month for 100 actions

Apps

Make3,000+
ForwardThis145+

Undo

MakeNo undo for what a scenario has written to your apps
ForwardThisUndo for 24 hours on reversible work

Make pricing and limits checked 1 September 2026.

Which one fits how you work?

Choose Make if

  • You want automation that runs on its own: scheduled scenarios, webhooks and watched folders, at any hour of the day.

  • Your volume is high and identical. Ten thousand credits for $9 a month makes Make one of the cheapest ways to run the same flow at scale.

  • Your workflows need real logic. Make's canvas handles branching routes, iterators and error handlers that ForwardThis has no equivalent for.

  • You need an app ForwardThis does not cover yet. Make connects to over 3,000.

Choose ForwardThis if

  • Your work starts as an email, and it looks slightly different every time.

  • You don't want a canvas to design or maintain. There is no scenario to break, because there is no scenario.

  • You want messages held for approval before they go out, and undo for 24 hours on reversible work.

  • You'd rather pay for jobs done than for module runs. A six-module scenario spends six credits every run; one forwarded email is one action, however much it asks for.

What a single forwarded email does

The trigger is the email you forward. There is no editor and nothing to design in advance. This whole job is one email, and in Make it would be a workflow you build first.

You forward

Rowan Ashworth

Signed proposal attached

proposal-signed.pdf

Your instructions

Mark the Fenwick & Moss deal as won, file the signed proposal under Clients/Fenwick & Moss, and set up a kickoff task for Monday.

  • HubSpot

    Mark the deal won

    Fenwick & Moss fit-out

  • Google Drive

    File proposal-signed.pdf

    Clients / Fenwick & Moss

  • Asana

    Create the kickoff task

    Due Monday 7 September

You receive a confirmation email once complete, with an undo button that works for 24 hours.

Get started

Setup in 30 seconds.

What is ForwardThis?

ForwardThis is an ops assistant for your inbox. It turns email into action, without the hassle. Compatible with over 145+ of the apps you use every day.

  • Works with any email

    Compatible with any personal or professional email provider. Gmail, Outlook and more.

  • 145+ apps

    Works across all the apps you already use every day. With more being added every month.

  • Setup in seconds

    No complex setup, apps to install or workflows to build. Sign up, forward, done.

  • Secure & private

    ForwardThis only acts on the emails you send it, and no data gets retained after actions have been completed.

Try it with a real email.

Forward any work email to the address below and see what ForwardThis can do. No signup required.

Occasional product emails may follow.

FAQs

Is ForwardThis a Make alternative?
For work that starts in your inbox, yes: filing, logging, task creation and the rest of email-driven admin, with nothing to design. For scenarios that run on schedules and webhooks, no. Make is built for that and ForwardThis deliberately is not.
Can I use both?
Yes, and plenty of teams should. Make for the scenarios that repeat exactly, ForwardThis for the emails that need a judgment call. They don't conflict, because they never touch the same job.
Does ForwardThis have triggers?
It has exactly one, and it is the email you forward. Nothing happens unless you send it, so nothing runs overnight, nothing loops, and there is no scenario to maintain or debug. The trade is deliberate. You keep sight of every action, and you give up unattended automation, which is exactly the thing Make does best.
What is a Make credit, and how does it compare to a ForwardThis action?
A Make credit is one module run, so a six-module scenario spends six credits every time it fires. Make renamed operations to credits in 2025, and the maths did not change. A ForwardThis action is one forwarded email, however many things it asks for and however long the back-and-forth gets. High identical volume favours Make's model; varied one-off jobs favour ForwardThis.
Which one has more integrations?
Make, comfortably: over 3,000 apps against 145+ for ForwardThis. ForwardThis covers the tools most businesses run on every day, and the list grows monthly. If a niche app matters to you, check both lists before deciding.
Is Make the same as Integromat?
Yes. Integromat rebranded as Make in early 2022, with a new visual builder on the same idea: scenarios assembled from modules, priced per module run. Everything on this page describes the current Make platform, checked September 2026.