<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rahul David Mondal</title>
    <description>The latest articles on DEV Community by Rahul David Mondal (@rahul_david_mondal).</description>
    <link>https://dev.to/rahul_david_mondal</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3987797%2F5360bf8f-4eca-469c-9e8c-b0983e07e357.jpg</url>
      <title>DEV Community: Rahul David Mondal</title>
      <link>https://dev.to/rahul_david_mondal</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rahul_david_mondal"/>
    <language>en</language>
    <item>
      <title>Everyone Starts With Zapier. Here's Why I Switched to Make.com Before Paying a Cent</title>
      <dc:creator>Rahul David Mondal</dc:creator>
      <pubDate>Sat, 27 Jun 2026 19:19:39 +0000</pubDate>
      <link>https://dev.to/rahul_david_mondal/everyone-starts-with-zapier-heres-why-i-switched-to-makecom-before-paying-a-cent-1pce</link>
      <guid>https://dev.to/rahul_david_mondal/everyone-starts-with-zapier-heres-why-i-switched-to-makecom-before-paying-a-cent-1pce</guid>
      <description>&lt;p&gt;I came to automation the same way most people do. A repetitive task was eating up too much of my workday. As a full-time SEO Content Specialist, researching and creating a content brief for an article took half a day. So I Googled "best automation tool" and clicked the first result. That result was Zapier.&lt;/p&gt;

&lt;p&gt;I signed up for the free plan, opened the builder, and started exploring. I had a real workflow in mind: connecting a Google Form to OpenAI to generate content briefs automatically. A multi-step sequence involving data transformation, a custom API call, and a Google Docs output.&lt;/p&gt;

&lt;p&gt;The Zapier free plan stops you at step one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the Zapier free plan actually gives you:
&lt;/h2&gt;

&lt;p&gt;For starters, Zapier's free plan does not allow multi-step workflows.&lt;/p&gt;

&lt;p&gt;You get one trigger and one action. That's the entire free tier. With the free plan, you can have 100 tasks per month, two steps maximum per Zap, no filters, formatters, or webhooks, and a 15-minute gap between each time Zapier checks for new data. I was fine with the 15-minute gap it takes to update the Zap, because it's the same with Make.com.&lt;/p&gt;

&lt;p&gt;But if you want a multi-step workflow and conditional logic (which I needed), then you need a paid plan. As of now, &lt;a href="https://zapier.com/pricing" rel="noopener noreferrer"&gt;the only paid option is $19.99/month for a single professional&lt;/a&gt;. There's no middle tier.&lt;/p&gt;

&lt;p&gt;So, instead of upgrading my plan, I went looking for alternatives. Then I found Make.com.&lt;/p&gt;

&lt;h2&gt;
  
  
  How I found Make.com
&lt;/h2&gt;

&lt;p&gt;Make.com came up in every Reddit thread and Quora answer. The consistent view I got was that it's harder to learn, but the free plan is actually usable.&lt;/p&gt;

&lt;p&gt;That turned out to be exactly right.&lt;/p&gt;

&lt;p&gt;Make's free tier gives you 1,000 credits per month and 2 active scenarios. Multi-step scenarios are supported from day one. You get routers, filters, HTTP modules, data transformers, all of it, without paying anything. For me, that was more than enough.&lt;/p&gt;

&lt;p&gt;The visual canvas shows you a diagram of your workflow, instead of a linear list of steps as shown in Zapier. This is helpful because when something breaks, you can see the exact module where the data stopped moving.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built on the Free Plan
&lt;/h2&gt;

&lt;p&gt;The &lt;a href="https://eu1.make.com/public/shared-scenario/A4RFWKect7x/content-brief-generator" rel="noopener noreferrer"&gt;content brief workflow generator&lt;/a&gt; I'd originally planned works on Make. &lt;/p&gt;

&lt;p&gt;A Google Form submission triggers the scenario. Make sends that data to the OpenAI API through a custom HTTP module. GPT-4 generates a structured brief. Make.com writes it to a new Google Doc in my Drive. All of this in under 15 minutes, for a brief that used to take me 2 to 4 hours. I wrote a full breakdown of that build in a separate article, including the part nobody warns you about. &lt;a href="https://dev.to/rahul_david_mondal/i-automated-my-content-brief-process-for-free-heres-what-nobody-tells-you-about-makecom-5ci6"&gt;Read here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foyy0dchi7gbzn777dmct.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Foyy0dchi7gbzn777dmct.png" alt=" " width="800" height="355"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;That part is the HTTP module. You're constructing a JSON body from scratch, mapping form field tags precisely to prompt variables. One misplaced bracket and the scenario fails entirely. &lt;/p&gt;

&lt;p&gt;That is a frustrating thing. I would recommend budgeting an evening if you haven't worked with JSON before. Validate your structure in JSONLint before you run anything. Check the &lt;a href="https://community.make.com/" rel="noopener noreferrer"&gt;Make community forum&lt;/a&gt; when it breaks. Whatever error you're seeing, someone has already posted about it and worked through it.&lt;/p&gt;

&lt;p&gt;After the content brief workflow, I built a second one. A &lt;a href="https://eu1.make.com/public/shared-scenario/Q1YvI7vargK/expense-tracker-telegram-bot" rel="noopener noreferrer"&gt;Telegram expense bot tracker&lt;/a&gt; that logs my expenses. I text it two words ("Dining 1200"), and it categorizes the amount, adds a row to my Google Sheet, and labels it under the right category. Same free plan, completely different use cases.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvgoqo8f09km7d046ku94.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvgoqo8f09km7d046ku94.jpeg" alt=" " width="778" height="1600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Both scenarios are still running on the free tier. If you want to see what the free plan can actually do, no card is required. &lt;a href="https://www.make.com/en/register?pc=rdmflow" rel="noopener noreferrer"&gt;Click here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;I may earn a commission if you sign up through my link, at no extra cost to you.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The Honest Comparison
&lt;/h2&gt;

&lt;p&gt;Zapier is easier for a first automation if that automation is two steps. The interface is cleaner for beginners, setup is faster, and the template library is more useful for simple use cases. If you need to connect two apps and trigger one action, Zapier gets you there faster.&lt;/p&gt;

&lt;p&gt;The problem is, there's no free middle ground. The jump from Zapier's free plan to the first paid tier is $19.99 per month. That's the price to unlock multi-step workflows, filters, webhooks, and conditional logic. Basically, everything you need to build something real is behind that paywall.&lt;/p&gt;

&lt;p&gt;Make.com's free plan has real constraints as well. Two active scenarios mean you'll upgrade eventually. The 15-minute polling interval means nothing runs in real time. But for me, the biggest issue was, and still is, that the 1,000 credits disappear faster than expected once your scenarios have several modules. And finally, the learning curve isn't short. For someone who has never done automation, this was difficult. It took me two days to figure out the nuances of the platform.&lt;/p&gt;

&lt;p&gt;The difference is that Make's free plan is a working tool. Not a preview of one.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who Should Start Where
&lt;/h2&gt;

&lt;p&gt;If you need a simple two-step automation between two common apps and want it running in ten minutes, start with Zapier. For that use case, it's genuinely the better starting point.&lt;/p&gt;

&lt;p&gt;If you need multi-step workflows, conditional logic, or a custom API call, Zapier's free tier will stop you before you finish building. Start with Make. You'll spend more time learning it up front, but less time hitting walls. In the long run, it's worth it. &lt;/p&gt;

&lt;p&gt;And frankly, if you want to learn about automation by actually building real workflows without paying first, Make.com is the only option between the two. &lt;/p&gt;

&lt;h2&gt;
  
  
  Final Takeaway
&lt;/h2&gt;

&lt;p&gt;I'm still on Make's free plan. Both of my scenarios are running. The brief workflow handles real client work. The expense tracker handles my daily logging.&lt;/p&gt;

&lt;p&gt;At some point, I'll outgrow two active scenarios and move to the Core plan at $12 per month for 10,000 credits. That's a reasonable upgrade for the amount of work and time it saves me.&lt;/p&gt;

&lt;p&gt;If you want to try automation, join Make.com's free plan. No card is required.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.make.com/en/register?pc=rdmflow" rel="noopener noreferrer"&gt;Start building&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This article contains affiliate links. If you sign up through my link, I may earn a commission at no extra cost to you. I only recommend tools I use.&lt;/em&gt; &lt;/p&gt;

</description>
      <category>automation</category>
      <category>nocode</category>
      <category>make</category>
      <category>productivity</category>
    </item>
    <item>
      <title>I Automated My Content Brief Process for Free. Here's What Nobody Tells You About Make.com</title>
      <dc:creator>Rahul David Mondal</dc:creator>
      <pubDate>Tue, 16 Jun 2026 18:55:12 +0000</pubDate>
      <link>https://dev.to/rahul_david_mondal/i-automated-my-content-brief-process-for-free-heres-what-nobody-tells-you-about-makecom-5ci6</link>
      <guid>https://dev.to/rahul_david_mondal/i-automated-my-content-brief-process-for-free-heres-what-nobody-tells-you-about-makecom-5ci6</guid>
      <description>&lt;p&gt;&lt;em&gt;This article contains affiliate links. If you sign up for Make.com through my link, I may earn a commission at no extra cost to you. I only recommend tools I personally use.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I’m an SEO content specialist. On a full workday, I might be handling a long-form B2B blog, landing pages, case studies, some copywriting, and keyword research. All at the same time. That’s the job.&lt;/p&gt;

&lt;p&gt;The content brief is where I lose the most time.&lt;/p&gt;

&lt;p&gt;A good brief for a topic I know well takes about 1.5 hours. A brief for a B2B topic I know nothing about, like healthcare compliance software for enterprise teams, might easily take me 2 to 4 hours. This involves opening multiple research tabs, skimming articles, checking competitor pages, and compiling notes. By the time I have something structured enough to write from, half the day is gone.&lt;/p&gt;

&lt;p&gt;So I built an automation to handle it. On Make.com. In my first month of using the platform. Without any prior experience building automations.&lt;/p&gt;

&lt;p&gt;Here’s what actually happened.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the automation does
&lt;/h2&gt;

&lt;p&gt;The workflow starts with a Google Form. I fill in seven fields: blog topic, target keyword, target audience, word count, funnel stage, competitor URLs, and any notes I want the brief to address.&lt;/p&gt;

&lt;p&gt;Once submitted, Make.com takes that form data and sends it to the OpenAI API. GPT-4 processes everything and generates a structured content brief. That brief then lands as a Google Document in my Drive, automatically.&lt;/p&gt;

&lt;p&gt;Start to finish: under 15 minutes, for a brief that used to take me a morning.&lt;/p&gt;

&lt;p&gt;I first ran it properly on a real brief for a B2B healthcare SaaS client. A topic I knew almost nothing about going in. The brief came out detailed enough that I used it as the foundation for an article that ranked within four weeks. The full scenario is public if you want to see how it’s built; &lt;a href="https://eu1.make.com/public/shared-scenario/A4RFWKect7x/content-brief-generator" rel="noopener noreferrer"&gt;click here&lt;/a&gt;. For the case study, &lt;a href="https://heartfelt-dodol-a62b73.netlify.app/" rel="noopener noreferrer"&gt;read this&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;If you want to try this yourself, Make.com's free plan needs no card. &lt;a href="https://www.make.com/en/register?pc=rdmflow" rel="noopener noreferrer"&gt;Sign up here and clone both scenarios directly into your account.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmjzz77w26s7jyc8up3jr.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fmjzz77w26s7jyc8up3jr.png" alt="The full scenario in Make.com’s visual canvas. Each module handles one step of the brief generation." width="800" height="355"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What nobody tells you about building this
&lt;/h2&gt;

&lt;p&gt;The Make.com marketing will tell you it’s drag and drop, no code required. That’s mostly true.&lt;/p&gt;

&lt;p&gt;The HTTP module is a different story.&lt;/p&gt;

&lt;p&gt;The HTTP module is what connects Make.com to any external API. In this case, OpenAI. You’re building a custom API call from scratch inside Make’s interface. You have to get the JSON body structure exactly right. The field tags from your Google Form have to map precisely to the variables in your prompt. One misplaced bracket, one misaligned tag, and the scenario fails silently or throws an error that tells you almost nothing useful.&lt;/p&gt;

&lt;p&gt;I spent more time on that one module than on every other part of the build combined.&lt;/p&gt;

&lt;p&gt;This isn’t a reason to avoid Make.com. It’s a reason to know what you’re walking into. If you’ve never seen a JSON body before, budget an evening for it. Validate your structure with JSONLint before you test the scenario. And check the Make community forum when it breaks. The error you’re seeing, someone else has already posted about it.&lt;/p&gt;

&lt;p&gt;Once you get through it, the HTTP module is genuinely powerful. You’re no longer limited to the apps Make natively supports. You can connect to anything with an API. That’s a significant shift from most no-code tools that only let you work within their approved app library.&lt;/p&gt;

&lt;h2&gt;
  
  
  The free tier math, and where the cost actually comes from
&lt;/h2&gt;

&lt;p&gt;Make.com’s free plan gives you 1,000 credits per month and 2 active scenarios. Each module in a scenario costs one credit when it runs. A typical content brief run touches 4 to 5 modules, so Make’s credits are not the constraint here.&lt;/p&gt;

&lt;p&gt;The real constraint is the OpenAI API.&lt;/p&gt;

&lt;p&gt;When you call GPT-4 to generate a full content brief, you’re burning tokens. Those tokens cost money, and they come from your OpenAI account, not from Make. A detailed brief with competitive context and structured sections consumes a meaningful amount of GPT-4 tokens per run.&lt;/p&gt;

&lt;p&gt;For my workflow, 2 to 3 briefs per week is a comfortable cadence on a modest OpenAI credit balance. That’s plenty for a single writer managing multiple clients or projects.&lt;/p&gt;

&lt;p&gt;One thing worth understanding: Make.com itself is free to start and stays free at low volume. The cost variable in an AI-powered automation is almost always the AI API you’re calling, not the automation platform. Budget accordingly.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who this is actually for
&lt;/h2&gt;

&lt;p&gt;A content writer, copywriter, or SEO specialist who is managing multiple content formats and spending serious time on long-form blog research from scratch. Specifically, someone who is also the one writing the content, not just commissioning it.&lt;/p&gt;

&lt;p&gt;That last part matters more than it might seem.&lt;/p&gt;

&lt;p&gt;The brief this automation produces is a solid starting point. It is not the final word. A writer reads it, challenges it, and deviates from it where their knowledge or judgment says the brief is wrong. That’s how briefs work. They’re scaffolding, not scripture.&lt;/p&gt;

&lt;p&gt;If you’re a content manager thinking about running this and handing the Google Doc to a writer as a complete finished brief, stop. The writer reviewing and adjusting the output is part of the workflow. It’s not an inefficiency you’re eliminating. Skipping that step produces low-quality content and wastes everyone’s time, including the writer’s.&lt;/p&gt;

&lt;p&gt;The automation is for the person doing the writing. Not for the person managing the person doing the writing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The other thing I built: a Telegram expense tracker
&lt;/h2&gt;

&lt;p&gt;This has nothing to do with content work, but it says something important about Make.com’s range.&lt;/p&gt;

&lt;p&gt;I connected Telegram to Google Sheets. Now, when I go out, I text my Telegram bot: “Dining 1200” or “Rapido 70.” Two words. The bot logs it, categorizes it under Food or Transportation, and adds it to my expense spreadsheet automatically.&lt;/p&gt;

&lt;p&gt;I used to avoid tracking expenses because every app wants you to open it, navigate to the right screen, select a category, enter an amount, and confirm. My Telegram bot is just texting a friend.&lt;/p&gt;

&lt;p&gt;The same visual builder that handles a GPT-4 content brief pipeline handles this. Make.com scales from simple personal automations to complex multi-step AI workflows, and the free plan covers both. That range, at zero cost, is something Zapier does not match.&lt;/p&gt;

&lt;p&gt;The scenario for this one is public as well. &lt;a href="https://eu1.make.com/public/shared-scenario/Q1YvI7vargK/expense-tracker-telegram-bot" rel="noopener noreferrer"&gt;Click here&lt;/a&gt; to learn more.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffn5aezv54jwx1njsjs9w.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffn5aezv54jwx1njsjs9w.jpeg" alt="This is the mobile screenshot of my Telegram Expense Tracker bot that can simply register and categorize my expenses with just one simple text." width="778" height="1600"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Make.com vs Zapier: The Honest Comparison
&lt;/h2&gt;

&lt;p&gt;I tried both before settling on Make.com.&lt;/p&gt;

&lt;p&gt;Zapier is easier to start with. If you need a simple two-step automation, Zapier gets you there faster. The interface is cleaner for beginners, the templates are better, and the app library is larger. For quick, linear automations, it’s the right tool.&lt;/p&gt;

&lt;p&gt;Make.com has a steeper learning curve but a better free tier. 1,000 credits per month and 2 active scenarios versus Zapier’s 5 Zaps and 100 tasks. For a non-developer building multi-step AI workflows that involve data transformation and API calls, that gap matters significantly.&lt;/p&gt;

&lt;p&gt;The visual canvas also makes it easier to debug complex scenarios. You can see exactly where data flows through your modules and where it breaks. When an error happens, the visual layout helps you trace it back to the source.&lt;/p&gt;

&lt;p&gt;Also worth knowing: Make.com is around 47% cheaper than Zapier at comparable paid tiers. At the Core plan level, you’re getting 10,000 credits a month for roughly $9 versus Zapier’s 2,000 tasks for $20. If you eventually outgrow the free plan, the upgrade math is significantly better on Make.&lt;/p&gt;

&lt;p&gt;For a non-developer building genuine multi-step AI workflows on a tight budget: Make.com is the right starting point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pricing if you need to scale
&lt;/h2&gt;

&lt;p&gt;The free plan covers 1,000 credits, 2 active scenarios, and a 15-minute minimum scheduling interval. Enough to learn the platform and run light workflows at real volume.&lt;/p&gt;

&lt;p&gt;Core ($9/month) gives you 10,000 credits and removes most of the free tier’s limits. This is where most solo operators land when they need more than two active scenarios or more frequent scheduling.&lt;/p&gt;

&lt;p&gt;Pro ($16/month) adds full execution history search, which matters when you’re debugging a complex scenario that failed three days ago and you need to trace exactly what happened.&lt;/p&gt;

&lt;p&gt;Teams ($29/month) is only relevant if multiple people need to edit scenarios. Solo operators can skip it.&lt;/p&gt;

&lt;p&gt;One thing to know: Make.com switched from “operations” to “credits” in August 2025. The pricing structure is the same in practice, but if you’re reading older guides that use operations language, that’s what’s changed.&lt;/p&gt;

&lt;h2&gt;
  
  
  My verdict after one month
&lt;/h2&gt;

&lt;p&gt;Make.com is the most useful thing I added to my workflow this year. It costs me nothing right now beyond my OpenAI API credits.&lt;/p&gt;

&lt;p&gt;The HTTP module learning curve is real. I won’t pretend otherwise. But if you’re a content professional with genuine multi-step automation needs, that’s a curve worth climbing. On the other side of it, you can connect your tool stack to any API in the world and automate things that no pre-built Zapier template will ever handle.&lt;/p&gt;

&lt;p&gt;For a stretched content writer or SEO specialist who is losing mornings to research and brief work, this is worth a serious look.&lt;/p&gt;

&lt;p&gt;Make.com's free plan requires no card. You can start building today, and both scenarios I built are public and can be cloned. &lt;a href="https://www.make.com/en/register?pc=rdmflow" rel="noopener noreferrer"&gt;Try Make.com free.&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;If you've built anything on Make.com, drop it in the comments. I'm curious what workflows other people are automating.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Published by Rahul David Mondal, SEO Content Specialist.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>automation</category>
      <category>productivity</category>
      <category>make</category>
      <category>nocode</category>
    </item>
  </channel>
</rss>
