Different ways to use Zapier and Make.com
By connecting AWS lambda with Zapier and Make.com
When we started to use Zapier and Make.com, we quickly found out that we could integrate with services like Google Sheets, Slack, Dropbox, and many more. But some services required us to run custom code. The most commonly used example is the integration with Google Analytics. It requires you for example to create a function in AWS Lambda, and then Zapier or Make.com can trigger your process.
Choose "Webhooks" as the trigger
Paste your AWS lambda URL into the "Payload URL" field
*By using Google cloud functions *
Google cloud functions are a great way to run your code in the cloud. You can create a simple webhook triggered by Zapier or Make.com and then use console.log to write to the function console. If you are not familiar with what cloud functions are, they are a way to create a function on the fly on the Google cloud platform.
This is a serverless computing solution where you can run code triggered by events from Zapier or Make.com You can also deploy your code on a schedule or on-demand from within the Google Cloud Console. This function will be triggered by an event, like an incoming webhook on Zapier or Make.com or even an SMS message sent to your Twilio number.
A practical example of this could be that you send an end-of-day report to your accounting software every night at 5 pm. So every time someone triggers the Zap, which sends this report, Zapier will call your cloud function, which will trigger the sending of the information.
Cloud functions are a great way to run code without managing servers or setting up an entire application. You only pay for the time, or you use them, and you don't have to worry about scaling issues because Google handles that for you.
By using HTTP Post Method
The easiest way to run code in Zapier or Make.com is by creating Zaps using the HTTP POST method. This is useful if you are using any of the following applications:
If you want to create a Zap with HTTP Post, follow these steps:
Go to zapier.com or make.com, Create a new Zap Set up Action Step 1 (Webhooks) Set up Action
Set up (a Web Service) in which you will pass your data Select POST method in Action
Choose RAW in Action application/json
*By using Pipedream *
Pipedream is a low code integration platform for developers that allows you to connect APIs remarkably fast. Pipedream is focused on making it easy to integrate APIs to get ideas into your application more quickly.
It is also an automation service that allows you to take actions from webhooks and send them to other apps. Pipedream will enable you to integrate Zapier and Make.com with any application easily. This means that you can run scripting code in any programming language.
What's excellent about Pipedream is that it abstracts the API calls away from the developer. That way, you don't need to worry about API calls and can quickly test your scripts.
Best Solution: Using 1SAAS prebuilt API
Add our API to your Zapier or Make.com and integrate and get yourself free from all other hectic methods. With our API, your code will run in a very smooth and fast way, and this will boost the productivity of your work.
Zapier is a web automation tool that allows you to easily create connections with hundreds of different app types, including APIs, tools, payment gateways, productivity apps, social media sites, visualization apps, and more. It works across platforms and devices, so everyone in your team can work off the same schedule without having to lift a finger. Integromat is a platform for creating processes in automation systems.
The system involves the implementation of the rules engine along with Connection Manager for integration with external services via API or Webhooks. It also offers the ability to create custom integrations for users' internal business processes.
Among the methods mentioned above, the easiest and flexible one that I will suggest is using 1saas's API because it's easy to connect with Zapier and integrate. It's also a high-speed and time-saving method.
Cloud Integration, iPaaS, SaaS, BPA… Ough, hard to keep track of all these terms. They are currently used frequently (and increasingly) in the context of automation, and it is sometimes difficult to make a clear distinction and distinction. We have already written blog posts on the terms iPaaS, SaaS and BPA, but we’ll take them up again here to make the difference.
But let’s start with cloud integration, because that’s the central umbrella term in which we embed all the other technologies in this blog post.
To illustrate these advantages, an example is suitable that we know well from our everyday work as an automation agency:
The central data to be used here is the data of a major customer. This can be the simplest information, such as the address. This address is required in numerous but completely different processes in the company: on the one hand, for correct invoicing in accounting. On the other hand, in the CRM system, where all the data of the large customer is also stored. But the address is also important in sales, for example, when employees go to the sales meeting on site.
Now the customer announces that the address of the company has changed after a move. This information will reach you by e-mail. There are now two options:
01. The e-mail is forwarded to all affected departments, accounting, sales, customer service, marketing… All persons open their corresponding program, CRM, accounting software, marketing tools (such as newsletter marketing) and change the data already stored there of the customer. This means that in multiple applications, different people do exactly the same thing: change one address. 02. But there is also an alternative: By connecting your applications, thus by integrizing them, the customer’s e-mail, or rather the information it contains about the address change, is automatically passed on to all affected applications: CRM, accounting, marketing, ERP. This does not require any clicks, because the cloud integration detects a trigger, i.e. address change, and thus automatically starts the process.
What sounds unimpressive in a single process becomes more effective when such a process occurs several times a day or weekly. Because there is a lot of data that is available in different applications and should always be correct. If these applications are cloud applications they are suitable for cloud integration.
But cloud integration doesn’t just happen. There are now a variety of applications that enable and implement this. Such tools usually allow us to link the relevant cloud applications on a central platform and define clear rules on when, how, where, how much data should be passed on and what happens to them.
IPaaS, SaaS, BPA, ABC – who can still see through it?
To realize cloud integration, there are various applications and technologies that are sometimes used interchangeably.
Cloud integration cannot be done without SaaS, iPaaS and BPA
Cloud integration is rather an umbrella term that includes numerous technologies, such as SaaS, iPaaS and BPA, and this is also absolutely necessary. Cloud integration is a concept that is made possible by appropriate technologies.
However, all terms share the commonality that they are cloud-based and thus offer enormous potential for growth and scaling. In addition, they are often cheaper to implement and maintain because changed requirements are easy to implement.
As an independent automation agency, we implement cloud integration according to your requirements. We use a variety of SaaS tools and iPaas (strictly speaking BPA) software. Together we find individual solutions that are flexible and scalable.