Pretium eget enim ut bibendum ac rutrum hendrerit risus vitae non morbi phasellus sollicitudin luch venenatis tortor massa porttitor diam auctor arcu cursus sit mauris scelerisque orci aliquam amet nascetur lectus tempus nunc tortor sed enim fermentum tincidunt quis erat nibh interdum cum tristique tincidunt cursus malesuada amet ac feugiat aliquam tellus non.
Mus mauris donec consectetur nisl ultricies. Malesuada integer augue sed ullamcorper condimentum malesuada mauris vulputate integer. Sit fermentum sit orci sit velit pulvinar sed. Nunc leo sed diam ornare felis magna id vitae urna. Scelerisque gravida eget at pellentesque morbi amet vitae elit volutpat. Pretium in gravida vel nascetur platea dictum parturient laoreet.
Sit fermentum sit orci sit velit pulvinar sed. Nunc leo sed diam ornare felis magna id vitae urna. Scelerisque gravida eget at pellentesque morbi amet vitae elit volutpat. Pretium in gravida vel nascetur platea dictum parturient laoreet.
Id integer amet elit dui felis eget nisl mollis in id nunc vulputate vivamus est egestas amet pellentesque eget nisi lacus proin aliquam tempus aliquam ipsum pellentesque aenean nibh netus fringilla blandit dictum suspendisse nisi gravida mattis elementum senectus leo at proin odio rhoncus adipiscing est porttitor venenatis pharetra urna egestas commodo facilisis ut nibh tincidunt mi vivamus sollicitudin nec congue gravida faucibus purus.
“Dignissim ultrices malesuada nullam est volutpat orci enim sed scelerisque et tristique velit semper.”
Id integer amet elit dui felis eget nisl mollis in id nunc vulputate vivamus est egestas amet pellentesque eget nisi lacus proin aliquam tempus aliquam ipsum pellentesque aenean nibh netus fringilla blandit dictum suspendisse nisi gravida mattis elementum senectus leo at proin odio rhoncus adipiscing est porttitor venenatis pharetra urna egestas commodo facilisis ut nibh tincidunt mi vivamus sollicitudin nec congue gravida faucibus purus.
If you are using Make.com for your automations, but struggling when there isn’t a built in integration, you need to learn how to use APIs.
In this article, I’ll show you the exact process I’ve used to connect any API in Make.com automations, plus I’m including the benefits of using APIs, and step-by-step instructions on how to get started.
APIs, or Application Programming Interfaces, are a set of protocols and tools for building software applications.
APIs allow different software systems to communicate with each other, enabling developers to add functionality to their applications without building everything from scratch.
But they also enable the power of automation. There wouldn’t be a Make or Zapier, if there wasn’t any APIs.
Make and Zapier provide a useful interface for creating and executing simplified API requests, but they don’t have integrations for every tool…
Sometimes you run into a situation where APIs are necessary in your automations.
Knowing how to use them can be beneficial when there isn’t a built in integration for the tool you are using, or when the functionality is not available for that tool.
For example, the Twitter API recently changed and the free version does not allow you to read the # of followers from a user’s account. This broke a lot of the dashboards I had built for clients, and I needed to find an alternative solution.
I used an API I found on RapidAPI as a workaround solution, and it worked great!
Using APIs in your Make.com automations is a relatively simple process. I’m going to walk you through the exact process I used to create the Twitter API workaround for my client’s dashboards.
You can use **any API that is available to you, but for the simplicity of this tutorial, we are going to use a website called ‘RapidAPI’.
Sign up for a free account at RapidAPI.com and use the search bar to find the API called ‘Twitter’ by ‘Glavier’ (the one I’ll be using in this tutorial, I have no affiliation).
Click on the pricing tab, and subscribe to the basic tier. This will allow you up to 500 requests per month, and does not require a credit card to use.
Go back to the ‘Endpoints’ tab, and select the API endpoint you would like to use. For this tutorial, we are going to the using the ‘User by Screen Name’ endpoint, which will allow us to collect a variety of information about a user.
In the ‘Code Snippets’ section, click the dropdown, select HTTP, then select HTTP/1.1. This will set the language to provide the example API request in.
Copy the information highlighted below into a word document.
This is all of the information you will need to include in the Make automation, as this is an example of an HTTP request.
Add an HTTP module to your Make scenario, and select ‘Make a request’.
For the URL, you might need to add “https://” to the beginning of it. Copy and paste the ‘Host’ (twitter135.p.rapidapi.com) from the information you saved, directly following the “https://”.
Make sure the method is set to ‘get’ (depending on your endpoint).
You will need to add 2 headers:
Both of these are in the information you saved from the example HTTP request earlier in the article.
When using APIs in your automations, it's important to keep in mind a few best practices:
Using APIs in your Make.com automations can help you add functionality and improve efficiency.
Why not give it a try and see how APIs can benefit your business processes & systems?