Whats the Difference Between Web-based automation and API Automation (zapier and pabbly)

Whats the Difference Between Web-based automation and API Automation (zapier and pabbly)

Video


 

Step 1- There are three different ways to automate (1) Scrape a website (2) Browser recording (3) Via Apps

Notion image
 

Step 2- When we click on Browser recording it takes us to URL column. Put web address on URL to open the window in left. This capture the steps.

Notion image

Step 3 – First step get recorded

Notion image
 

Step 4- Now click on Apps for app automation – Click on New flow

Notion image
 

Step 5- Click on Trigger – Select Airtable—Either select New record or updated record

Notion image

Understanding the Nuances Between Browser and API Automation

In the realm of automation, the distinction between browser-based and API-based automations holds significant importance. In a recent discussion by Jeremy Redman from Task Magic, the intricacies of these two automation methods were dissected, shedding light on their functionalities and applications.

The Fundamental Differences: Browser automation, as elucidated by Jeremy, revolves around the ability to record actions within a browser window. This method allows users to capture and replicate their steps, essentially training the system for automation tasks. On the other hand, API-based automation, exemplified by apps like Zapier, delves into integration with external applications and services through predefined triggers and actions.

Exploring Browser Automation: The concept of browser automation excels in its versatility and flexibility. Users can perform various tasks within a browser environment, such as clicking, typing, copying, pasting, and navigating between web elements and tools like Google Sheets. It empowers individuals to automate repetitive actions, streamlining processes and boosting productivity.

Unveiling Web Automation: Web automation, a term proposed to encompass the essence of browser automation without the connotation of "recording," emphasizes the dynamic nature of interacting with web interfaces. By reframing the terminology, the focus shifts towards capturing steps and executing them systematically on the web, simplifying the understanding of this automation approach.

Diving into App Automation: Conversely, app automation, akin to platforms like Zapier, relies on predefined triggers and actions to facilitate seamless interactions between different apps and services. While browser automation thrives on web-based operations, app automation caters to specific functionalities offered by APIs, bridging gaps in integration and synchronization between multiple applications.

The Power of Choice: By delineating browser automation, web automation, and app automation, individuals are empowered to discern the optimal automation method based on their requirements. Whether scraping a website, automating tasks on the web, or orchestrating operations through APIs, the diversity of options provides a tailored approach to automation solutions.

Closing Thoughts: Through the explication of browser and API automation distinctions, Jeremy Redman paints a vivid picture of the functionality and applicability of these automation methods. By reimagining browser automation as web automation and elucidating its role alongside app automation, a clearer understanding emerges, paving the way for enhanced automation strategies and efficiency.

By embracing the nuances between browser and API automation, individuals can harness the power of automation to streamline processes, enhance productivity, and unlock new possibilities in digital workflows.

 

VIDEO TRANSCRIPT

Hey everybody, Jeremy Redman here from Task Magic. We still got to put these shirts on, but on a shop or something. But I wanted to get you this video here really quick. So this is just a bumper and a lead into this. During a build session that we had that we released a few days ago, there was a segment in there that described what I think very, very well.

The difference between a Zapier or a Make, where they have API based or app based automations. and browser based automations, which is what our magic is. The ability to, uh, record clicking, typing, copy, pasting, moving data between front ends of sites and Google sheets, things like that. So anything you can get to on the web, essentially, um, any data.

Any front end buttons, any clicking fields, typing fields, clicking buttons, fields, watch this. Let me know what you think, because I think this says it best. And you can only get to that level by talking with customers. So check this out. Let me know what your thoughts are on this. We're we're breaking it up into three different ways to automate.

OK, OK, OK. One is scraping a website. Browser recording is essentially anything a human can do on the computer you can do. And we're trying to teach people like, this is diff it needs to be this is difficult if you just go in there and want to do anything. You know what I mean? Cause you can do anything and automate anything.

The third way is via apps. Okay. That's what you're talking about. Well, that's what we're going to set up for you today. So that is build on here. Let me hide this. That is build automations. via apps like Zapier is that for? Browser recording is if you want to do things that are outside APIs. So, for instance, if you go to Zapier, right, and you go to Airtable, right, and Airtable has one action, or one trigger, and that is edited row, edited record, okay?

What happens if you want to do something in Airtable that's not edited record? You can't, you, you can use browser automation. Say you want to invite someone to a workspace. So that's like in your admin panel. So you got to log in. You got to click the workspace you want to invite them to, and then you want to invite them.

That is a browser action. It's you going at logging into your air table, clicking the workspace, right? So capturing that click. So it will click into the workspace, then click invite and then it will type it in their email and then hit send. That is a browser recording versus the app recording. Does that make sense?

Yeah. No, I understand the recording. Yeah. Um, okay. I didn't, I didn't, I understand browser as opposed to app, but why recording because you're recording it to run later,

you know what I mean? Like a browser, you're recording your actions. So like for instance, you are going to go in and you're going to invite someone to that workspace every time they fill out your form You are recording that action once and oh, you don't mean recording you mean documenting Yes, correct.

That's what that means. Okay. I think the word recording made me feel like I was recording my screen Okay, so do you think you well you are kind of recording your screen you're recording the actions inside the browser window You Aren't you just do you want Documenting it what yeah here watch here. Okay, so tips i'll i'll skip this right now Um, because that's something to do with whatever.

So here we go. Okay We are recording in this browser window here Okay, you're gonna you're gonna record it's opening up. So look so it's opening up this browser window. It says let's get started Okay. So first off you you go to a page right air table. Okay dot com. Okay Look, I just recorded my first step airtable.

com. Okay, it's it's recording in here Does that make sense? This browser window. What's, why would I want it recorded? Because you're capturing the steps needed to make your automation. Oh, so that I just then can go do the automation. Correct. Oh, so it's teaching me how to do it by recording it. No, it is training our system by recording it.

Oh, so what is a word that, so, okay, let's say, let's not call this recording. Okay. Right. Let's call it just browser automation. Okay. What would you, let's not pretend it's a recording. Right. Right. It does that help you understand it? Yes. Okay. So if I just called it browser automation. As opposed to automation.

As opposed to app automation, right? Yeah. Yeah. Does that help? Okay, because what you're telling me Jeremy is it can scrape For those that understand what that is. Yeah Is it is it work with browsers or does it work with the web as opposed to an app? Yeah, correct. Yeah, right. So it's not too much browser.

That's what I mean for my head. Yeah So maybe i'll just change it to browser Maybe I'll change it. I would say web automation app automation web automation app if it makes sense to you. Um, I want to make sure that's exactly what it is But when you described it to me when I saw you you said like zapier and all those they need Apps and they need APIs, but you've developed a way that you can actually use the web.

Okay. All right Yeah, so i'll change i'm going to change that to web and see what it looks see what it feels like to other people I think so web web based so we'll we'll ditch the the the recording Okay, right. So you're just capturing these steps. You're capturing your steps Okay, so and if we go to new automation, all right, yeah does let's we're just going to call this web, right?

Does that now make sense scrape a website web automation and app automation? So does browser does web automation make sense if you were to click on this? And then follow those and then do those actions. Does that make sense? Yeah Yeah, not browser. It would be because the difference is show me how it works on the app and show me how it's different Okay, so we go to apps now apps.

This is how it's different than browser recording or web right apps This is just like zapier Okay, so you go to new flow.

Boom. You can let's just do start from scratch for now select a trigger Okay Now say we do air table again Okay, we can only do these two things In the Airtable, we can only do trigger a new, new record or updated record. Does that make sense? Say that again. You can go back a second. I wanna see what the two things you can do.

Okay. You can only do triggers a new record. Record is added to the table or updating a record. Okay. I don't know where you're updating record to know what the record. Okay. So, okay. Great. Alright, we'll start another one. That's the point of all of this. Yeah. To watch. Okay. So we come back here. So if you don't want to use these two things, okay?

Changed. All right. Now let's, what is one that I know, um, I know Asana, but go back a bit. Let's just see. Okay. Asana. Okay. Do Asana. Okay. Trigger task. The only trigger you have in here is task added to project. Okay. Right. You've added a task. Okay. All right. Yeah. Now, the, the thing is, is like if I go to Asana in the web.

I can click and do anything and record anything and invite someone to a special one. I see. I see. Yep. I can do any, if I can see it on the web. And if I can click it and type into it, I can do it. Yeah. This is limited to APIs. I see. Got it. Does that make sense? That totally makes sense now. So that is the difference between apps, app based recording, or app based automation, and web based automation.

Did this answer your question?
😞
😐
🤩