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.
Automation Engineer at a tech services company with 1-10 employees
Real User
Top 5
Dec 28, 2025
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...
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.