Gtm Operator, Lead Generator at 404Minds Technologies
Real User
Top 5
Mar 25, 2026
I'm using Make for integration with GoHighLevel, which is a CRM tool. I integrate data from Google Sheets or the GHL CRM to automate repetitive tasks. I use Make nearly every day for whatever task comes my way, including reconciliation of bills and transaction tracking in Google Sheets, as well as GoHighLevel work. When I receive leads from Meta, I integrate those as well. I have created an Airbnb scraper that extracts all details from Airbnb, including reviews and pinned locations, which are not very easy to obtain. I used Claude to create Python code, integrated it through Make, and used Apify. Make sends the command and prompt to Apify, which runs the code and scrapes all the details from Airbnb, then updates them in Google Sheets. Once any row is updated, Make automatically sends all details to every user. For example, when my name is entered in the Google Sheet, Make takes the name, email ID, company, and everything based on the flow I have configured, and sends the email automatically to that person. We have a company called Rental Abode, which is similar to Airbnb and we are building it now. I target them by scraping all details from Airbnb and sending it to them using Make.
My main use case for Make is mostly for marketing automation, including lead generation, lead integration, routing to sales agents, and for personal uses. I had a client who wanted me to retrieve every post being posted on a specific subreddit so that he could use that conversation or specific post and comment on it organically. This gives him a chance to warm up the client and sell his CRM product. I set up the automation by using the Reddit API to connect to Make and used the Google Gemini flash AI agent to summarize the post and the replies. One of our clients uses HubSpot as a CRM, so I connected WhatsApp automation and everything on Make. Whenever the lead status is changed on HubSpot, the automation triggers on Make, and a certain type of template that I have created on WhatsApp is automatically sent to the lead. An internal notification is also sent to the sales team.
My main use case for Make involves automating WhatsApp messages, website visits, and how to reply to them. I'm not using it very frequently, but it is a helpful tool. I once automated a few things with Make. If a client is onboarding and that person has some questions, I had submitted a few things, and accordingly, it was giving them a reply, and it was finally redirecting them towards my website. I chose to automate that particular process ideally just to save my time because I was getting so many leads and needed to filter them out, determining which lead is a warm lead, which lead is a hot lead, or something similar. I don't have anything else to add about my main use case or how it's helped me manage my leads. I think I have covered most of it. I will be using Make in the future, but as of now, I am using a lot of other tools as well.
My primary reason for using Make is workflow automation. When it comes to scraping data from portals like LinkedIn or any other website and then storing it on a Google Sheet, that is the most time-consuming task. I was able to create a workflow and automate it through agentic AI, which was a significant achievement for me.
I use Make for my personal use only as of now, and I am learning Make and automating things with it. Recently, I have created a scenario wherein I can automate the process to find me a topic, and based on that topic, it makes me a LinkedIn post and shares it with me on my email. That was a scenario I had created, but the only challenge is that this scenario is not yet perfect, so I am not yet posting those posts. I already shared one example of Make, where I have prepared a scenario wherein I spoke about the LinkedIn post. That is the only task I have prepared, and I think if I could give the perfect prompt, if I can enhance the prompt, it can give me a better output. Once that is successful, I will not have to search or hunt down for a topic every day to post on LinkedIn; Make will automatically help me research the topic and get me a scenario to post on LinkedIn. I use Make for my private use only; I have not used it for my organization.
The main use case is to provide automation, such as Google Sheet automation or anything that requires API calling to get data from external tools and send it to Google Sheets or a database. One specific example of an automation I have set up using Make is for a cab booking system, where I take data from WhatsApp, collect all the details, and call that using the Make webhook to send the WhatsApp data to Make, which then sends the data to Google Sheets. After gathering the data, I can trigger new API calls based on sheet conditions, such as whenever a row updates or changes, ensuring the automation works according to my requirements.
In that project, I used Make to build a real-time monitoring dashboard for internet of things devices using React for the front end and a FastAPI for the back end and MQTT for handling data streams. I used Make to automate workflows between the back end and external services, such as email notification systems and data storage endpoints. When specific events occurred, such as device data updates or threshold alerts, Make triggered actions such as sending notifications, forwarding processed data to other APIs, and synchronizing data for further analysis. Regarding the use case, Make helped us avoid writing custom integration logic in the back end and kept our system more modular.
My main use case for Make is that it serves as a perfect tool to interlace most of our API connections, syncing different environments together. Make enables us to connect apps that lack native integration, have limited API solutions of their own, or which do not meet our business needs. Whatever we needed, we could create in Make and remain satisfied about the performance.A specific example of how I use Make for API connections in my environment is integrating our CRM with a marketing application for data transmission and unity, GDPR compliance, and synchronization has been excellent through Make. Building scenarios for each specific language or location action has been beneficial. Managing certain actions and triggers based on links, some of the workflow solutions were not present in marketing tools, and we needed to create more complex processing in Make to meet our needs. Make is also a great tool that we use to build various automations, and it is excellent for connecting multiple tools together to send data. For example, at our company, we use Make to send new orders notifications from Shopify to Slack and also add the customer's shipping information to a Google Sheet for the fulfillment team. The best feature about Make that competitors lack is the option to connect rare and available apps via their API. It also allows us to get data from anywhere on the internet via GET requests. I have additional use cases for Make, as we use it to support a variety of internal and client integration projects. Everything from automating invoices from CRM orders to running recurring data pools from our database to client platform API connections for reporting has been excellent. It also helped us to connect platforms that otherwise would not connect while giving us the opportunity to code and customize these integrations for our specific use cases. Make has been used in my organization to start an automation process in the sales and marketing departments, closely followed by operations and human resources departments. Sales and marketing are automating all their initial contacts with clients from the first contact until the client is up and running independently. Operations are automating the tickets and follow-up to pending reports that clients submit. Human resources benefit from Make because they are integrating information streams from some of their departments using Make.
In our current company, we have a funnel workflow for the people who sign up. We do certain things such as creating database entries, creating our CRM entries, and then updating the information. If they book a meeting, we update those meeting booking details in the CRM as well. All of these parts are connected through Make. Make is working as the integration partner between the steps of our user workflows. We have been using a lot of interconnected integrations in Make. I see that as a very good use case for Make because it has thousands of interconnected integrations. We can basically make anything between all of those interconnected integrations. That is a very big use case for us. My main use case for Make is building automations.
Some of the very simple use cases that people use Make for is AI-powered content creation. That is where we help them out with different kinds of content creation and social media posting, different business process automations such as HR recruitment processes. Several of these cases have been implemented using Make.
As an entrepreneur and a freelancer who also runs my own agency, I use Make to set up automations for my clients. Recently, the most use cases are of AI agent or AI calling agent, but when I started with it, the most used case of Make was just to automate different platforms, moving one thing from here, from one platform to another.
We use Make to manipulate data, cut the numbers, take this line of code, and translate it to another line of code. SaaS products use XML, and other products use JSON. You need to translate to communicate between them. You have to make a transit code between them to communicate and take the backup between them.
Make is a robust automation platform that streamlines workflows, connecting apps to enhance productivity. Tailored for tech-savvy users, it offers dynamic automation solutions that optimize processes and facilitate seamless integration of disparate systems. At its core, Make empowers businesses to automate tasks through an intuitive builder with drag-and-drop capabilities. Ideal for professionals who need to integrate systems efficiently, it supports a wide range of applications, aiding in...
I'm using Make for integration with GoHighLevel, which is a CRM tool. I integrate data from Google Sheets or the GHL CRM to automate repetitive tasks. I use Make nearly every day for whatever task comes my way, including reconciliation of bills and transaction tracking in Google Sheets, as well as GoHighLevel work. When I receive leads from Meta, I integrate those as well. I have created an Airbnb scraper that extracts all details from Airbnb, including reviews and pinned locations, which are not very easy to obtain. I used Claude to create Python code, integrated it through Make, and used Apify. Make sends the command and prompt to Apify, which runs the code and scrapes all the details from Airbnb, then updates them in Google Sheets. Once any row is updated, Make automatically sends all details to every user. For example, when my name is entered in the Google Sheet, Make takes the name, email ID, company, and everything based on the flow I have configured, and sends the email automatically to that person. We have a company called Rental Abode, which is similar to Airbnb and we are building it now. I target them by scraping all details from Airbnb and sending it to them using Make.
My main use case for Make is mostly for marketing automation, including lead generation, lead integration, routing to sales agents, and for personal uses. I had a client who wanted me to retrieve every post being posted on a specific subreddit so that he could use that conversation or specific post and comment on it organically. This gives him a chance to warm up the client and sell his CRM product. I set up the automation by using the Reddit API to connect to Make and used the Google Gemini flash AI agent to summarize the post and the replies. One of our clients uses HubSpot as a CRM, so I connected WhatsApp automation and everything on Make. Whenever the lead status is changed on HubSpot, the automation triggers on Make, and a certain type of template that I have created on WhatsApp is automatically sent to the lead. An internal notification is also sent to the sales team.
My main use case for Make involves automating WhatsApp messages, website visits, and how to reply to them. I'm not using it very frequently, but it is a helpful tool. I once automated a few things with Make. If a client is onboarding and that person has some questions, I had submitted a few things, and accordingly, it was giving them a reply, and it was finally redirecting them towards my website. I chose to automate that particular process ideally just to save my time because I was getting so many leads and needed to filter them out, determining which lead is a warm lead, which lead is a hot lead, or something similar. I don't have anything else to add about my main use case or how it's helped me manage my leads. I think I have covered most of it. I will be using Make in the future, but as of now, I am using a lot of other tools as well.
My primary reason for using Make is workflow automation. When it comes to scraping data from portals like LinkedIn or any other website and then storing it on a Google Sheet, that is the most time-consuming task. I was able to create a workflow and automate it through agentic AI, which was a significant achievement for me.
I use Make for my personal use only as of now, and I am learning Make and automating things with it. Recently, I have created a scenario wherein I can automate the process to find me a topic, and based on that topic, it makes me a LinkedIn post and shares it with me on my email. That was a scenario I had created, but the only challenge is that this scenario is not yet perfect, so I am not yet posting those posts. I already shared one example of Make, where I have prepared a scenario wherein I spoke about the LinkedIn post. That is the only task I have prepared, and I think if I could give the perfect prompt, if I can enhance the prompt, it can give me a better output. Once that is successful, I will not have to search or hunt down for a topic every day to post on LinkedIn; Make will automatically help me research the topic and get me a scenario to post on LinkedIn. I use Make for my private use only; I have not used it for my organization.
The main use case is to provide automation, such as Google Sheet automation or anything that requires API calling to get data from external tools and send it to Google Sheets or a database. One specific example of an automation I have set up using Make is for a cab booking system, where I take data from WhatsApp, collect all the details, and call that using the Make webhook to send the WhatsApp data to Make, which then sends the data to Google Sheets. After gathering the data, I can trigger new API calls based on sheet conditions, such as whenever a row updates or changes, ensuring the automation works according to my requirements.
In that project, I used Make to build a real-time monitoring dashboard for internet of things devices using React for the front end and a FastAPI for the back end and MQTT for handling data streams. I used Make to automate workflows between the back end and external services, such as email notification systems and data storage endpoints. When specific events occurred, such as device data updates or threshold alerts, Make triggered actions such as sending notifications, forwarding processed data to other APIs, and synchronizing data for further analysis. Regarding the use case, Make helped us avoid writing custom integration logic in the back end and kept our system more modular.
My main use case for Make is that it serves as a perfect tool to interlace most of our API connections, syncing different environments together. Make enables us to connect apps that lack native integration, have limited API solutions of their own, or which do not meet our business needs. Whatever we needed, we could create in Make and remain satisfied about the performance.A specific example of how I use Make for API connections in my environment is integrating our CRM with a marketing application for data transmission and unity, GDPR compliance, and synchronization has been excellent through Make. Building scenarios for each specific language or location action has been beneficial. Managing certain actions and triggers based on links, some of the workflow solutions were not present in marketing tools, and we needed to create more complex processing in Make to meet our needs. Make is also a great tool that we use to build various automations, and it is excellent for connecting multiple tools together to send data. For example, at our company, we use Make to send new orders notifications from Shopify to Slack and also add the customer's shipping information to a Google Sheet for the fulfillment team. The best feature about Make that competitors lack is the option to connect rare and available apps via their API. It also allows us to get data from anywhere on the internet via GET requests. I have additional use cases for Make, as we use it to support a variety of internal and client integration projects. Everything from automating invoices from CRM orders to running recurring data pools from our database to client platform API connections for reporting has been excellent. It also helped us to connect platforms that otherwise would not connect while giving us the opportunity to code and customize these integrations for our specific use cases. Make has been used in my organization to start an automation process in the sales and marketing departments, closely followed by operations and human resources departments. Sales and marketing are automating all their initial contacts with clients from the first contact until the client is up and running independently. Operations are automating the tickets and follow-up to pending reports that clients submit. Human resources benefit from Make because they are integrating information streams from some of their departments using Make.
In our current company, we have a funnel workflow for the people who sign up. We do certain things such as creating database entries, creating our CRM entries, and then updating the information. If they book a meeting, we update those meeting booking details in the CRM as well. All of these parts are connected through Make. Make is working as the integration partner between the steps of our user workflows. We have been using a lot of interconnected integrations in Make. I see that as a very good use case for Make because it has thousands of interconnected integrations. We can basically make anything between all of those interconnected integrations. That is a very big use case for us. My main use case for Make is building automations.
Some of the very simple use cases that people use Make for is AI-powered content creation. That is where we help them out with different kinds of content creation and social media posting, different business process automations such as HR recruitment processes. Several of these cases have been implemented using Make.
As an entrepreneur and a freelancer who also runs my own agency, I use Make to set up automations for my clients. Recently, the most use cases are of AI agent or AI calling agent, but when I started with it, the most used case of Make was just to automate different platforms, moving one thing from here, from one platform to another.
We use Make to manipulate data, cut the numbers, take this line of code, and translate it to another line of code. SaaS products use XML, and other products use JSON. You need to translate to communicate between them. You have to make a transit code between them to communicate and take the backup between them.
I am using Make for things I cannot do with Zapier.