| |

Make vs. Zapier: Why I Moved

January has come and gone, and I’ve made the decision to fully move from Zapier to Make. I’m pleased with the functionality, the workflows, and the considerable cost difference1.

Here are my thoughts after one month with Make:

I really love the route building and general design of the scenarios better. The interface is much more intuitive. It’s easier to move things around, insert actions between other actions, create filters, and add routes.

MUCH. Easier.

You do need a little more know-how than with Zapier. Zapier has some tighter integrations with Dropbox and Google. For example, if you want to use your personal Gmail account, you need to spin up an API key for certain actions, instead of just authenticating.

It is a lot more secure though, as you’re not giving complete access to an app. You’re explicitly choosing the services you want the app to have access to.

Along what that know-how, you need to be mindful of how often your scenarios run. Since Make charges per operation, you can’t just let your automations run wild. I ended up hitting the 10,000 operation limit within 2 weeks.

Luckily, I was able to dial them back a reasonable amount and now I’m well within the limits of 10,000 operations per month, giving me wiggle room to add even more scenarios. And for what it’s worth, Zapier has this baked into their much higher cost.

The way to manage operations is to not have them run as often. The default is 15 minutes. I have some run every 2 hours, and some that run every 2 days. This is perfectly fine for me. They still run often enough that it doesn’t bottleneck my workflows. The hardest part was coming to terms with knowing they aren’t constantly running.

Make is much more affordable. I’d need to pay for around 90,000 operations to hit the same monthly costs as with Zapier. If I doubled my monthly operations, I’m still saving $55/mo on the billed monthly plan.

Finally, thanks to re-evaluating my automations, I was able to create more efficient actions, as well as move some automations to the native apps. For example, Vimeo has direct integration with Dropbox. I don’t need Make or Zapier as a third party anymore.

If you have any questions about Make, feel free to leave them in the comments!

  1. I got a few people tell me that the time savings is worth the month. My friends, the wealthy didn’t get wealthy by wasting money. And IMO, using Zapier over Make if you have more than 5 automations is a waste of money. ?

Similar Posts

  • |

    A Simple Solution to Selling Workshops

    While working out my income and project goals for this year, something I added to my list was more paid workshops and webinars. I want people to be able to sign up, get the workshop and the replay, and learn something tangible. And as a WordPress developer, it’s easy to think, “Oh I can put this whole thing on WordPress. But I’ve been actively deciding against WordPress for things like this. Here’s why.

    Get the bonus content by joining the Creator Crew

  • | |

    Switching to Apple’s Native Apps

    Since iOS 11 came out, I’ve been forming new opinions on apps and what I want to use on my phone. When I was an Android user, I would try not to pay for apps, and had reasonable success doing so. Call it the open source mentality, sure, but Google also had pretty great native…

  • |

    5 Functions You Should Consider Outsourcing

    In our daily lives, we outsource responsibilities and task management to apps. So when you want to find the time to grow your agency and create recurring revenue, why not outsource some of your business functions too? Here’s my list of the five functions you should be outsourcing.

  • How I Quickly Break Up my Podcast Audit Videos

    I have a confession to make, friend. I’m a little under water right now. Between sick, travel, vacation, and other summer things, I haven’t be able to write as much as I’d like for this newsletter. I plan on doing much more (including giving you those shortcuts I promised last week). Whenever I get under…