No-code Talk #3

[00:00:00] Aron: Connor.  

[00:00:01] Connor: Hello, Aaron. It's nice to be back for another  

[00:00:04] Aron: one. It's been a, it's been a while. I feel like this. Uh, I haven't been behind the desk. I haven't been streaming in the past couple of weeks, so, um, I might be a little rusty here, but I mean, I'm excited to have you back. I'm excited to  

[00:00:17] Connor: be here. I know.

And a lot has happened since the last stream. So they have announced these speakers for the no code conference. And I know you are. I didn't  

[00:00:30] Aron: apply to. Yeah. So, so before we, before we do that, I want to know who's in the chat. Who's heard of no code comp. Uh, so let us know if you've applied to be a speaker, if you're, if you're signed up.

So I'd love to know. I know that there's like a lot of news around no code conference. I'm super excited. I think, uh, you know, I'm kind of, uh, uh, can't wait for it to happen. So let us know in the chat, if you've kind of. Uh, and Connor, how about we start with like our experience of no code come from a couple of years back.

[00:01:04] Connor: Yeah. So we actually met at the no code conference in 2019. I actually was very lucky to get a spot to speak there because that means that we follow paid for my flights to San Francisco, which at the time was like a real big help being in New Zealand because you know, it's not like flying over there.

Yeah. I mean, exactly. I mean like, you know, the closest country to fly to from New Zealand is Australia and that's four hours away. So you can imagine what a mission it is to get to San Francisco. But, um, yeah, flew over, um, had a blast obviously, um, got to meet a lot of people there. So a lot of the people, um, in the no-code community, like, uh, Ray Raymar, pixel games, The fence, wait, people you been from mega pad, got a chance to meet all of them and had a very, very fun time.

I actually  

[00:02:05] Aron: remember meeting Colleen who's in the chat when the first folks I ever met as part of the no code conference or just no code, generally, I think it was just a Twitter community in 2019. So, uh, I'm you know, I remember meeting you, I think over a year. And I think you probably had a few more after I left and a good time was had by also folks.

Uh, uh, uh, yeah. So do go sign up. I know that they've made it free. It's online only for this year. So even though it's online, I'm sure folks are going to have a, an amazing time. I'm sure what flow is going to put on a great, great show. And, uh, I know you, Connor applied to. Uh, so give us, are you, are you speaking, given the.

[00:02:55] Connor: Yes. So I am going to have a session at the NOCO conference and intern in 2019, I did a talk on how I built the unicorn factory, where we put your table in Zapier. And, um, this year's talk is going to be along those lines with some updates and improvements. So at the time when I. Hawk in 2019, I was really just like getting started with those tools.

I didn't even really know that there were like a lot of other people out there that use like similar tools to build online platforms. But since then, um, I've um, Done a lot with the UNICOM factory, but I've also worked with a lot of other people have used the same tools to build their own online marketplaces and own online platform.

So in my talk, what I'm going to be doing is going over some use cases for the web, for, at your table and Zapier stack. And then also give a quick little rundown on where I think you should get started if you are starting at absolute zero. So I'm looking very forward to that, but. Heron. I know you applied.

[00:04:06] Aron: Yeah. So it's been a, it's been tough not to tweet over the past, uh, two weeks to let folks know that I'll also be speaking at no-code conference. And, you know, it's probably one of those, uh, those moments where you think back for me personally, uh, you know, uh, two years ago, going to the conference, meeting you all and kind of, that was my introduction to the no-code community.

And I thought it'd be like, Opportunity to, to give back to the community and frankly, just show how I run, automate all the things. So, uh, but in a more, not if you want to stream every week or do things like that, but really talk about how you can use air table and web flow together to create and repurpose content in an efficient way.

And the reason it's kind of full circle for me is that, uh, this is now my job, right? So at air table, I create content. And obviously I use air table and I repurpose that content. And so my life has kind of become what I am going to show. So I'm like super excited to provide resources to folks who are just like, Hey, we're thinking of using air table to create content.

Uh, we want to create something that's unique to our way of working and we want to be really efficient. And that's really what I've been kind of. Over the last three years now at automate all the things and at air table. So I'm really, really excited to share that I'll be speaking at a no-code conference.

Uh, you will as well. And there's a huge lineup of amazing speakers. So we're both quite sad that it's online only, but I think that was the right message. That, uh, Webflow made to make it online only given, you know, the world and its state. Uh, but I know that both of us and the whole team there are going to do everything we can to make it a successful event.

Uh, and yeah, let us know in the chat, if we're gonna see you virtually, um, I'm hoping to meet as many people as I can, uh, even though it's online. So really excited about that.  

[00:06:10] Connor: Absolutely. And I fully agree. I mean, I think everyone was looking forward to having a new. In-person event and obviously part of conferences is that element for sure.

But, you know, there's always going to be a next year. And I definitely think that considering the circumstances, like it's a very good call to make, so we'll just have a blast online. I'm sure whip first got a lot of cool things in store and then hopefully next year we can do something in.  

[00:06:40] Aron: Yeah, amazing.

So, uh, let us know in, uh, we got, Penny's going to join calling as well. I'm sure everyone in the chats already signed up to no-code coffee. If you haven't already go ahead and sign up, uh, and you know, really excited to do this, but no goat pump. So, uh, yeah. Are we, are we ready for the question of the month?

Are we going to be talking about today? Yeah. So we've got a great question that was actually asked, uh, to me by Steve. Uh, who I actually weirdly had the chance to meet this summer. Uh, and then we're going to talk about why is, uh, which is a new plugin in the web flow ecosystem. I'm going to talk about care for you, which, uh, sorta is where I started working on air table as a, as kind of a consultant almost, and really kind of highlighting the progress that they've done over.

And then we're going to do some open Q and a. If you guys have questions about anything that we're talking about, feel free to drop them in the chat and yeah, let's kick this. Uh, right. Let me move. This is where I try to like be efficient or try to do this properly. So move the agenda. I'm going to go ahead and share my browser here and then I'm sharing it with you.

There we go. Almost there folks almost there. Uh, there we go. So Connor, can you see my screen as well? We're good. Yup. Amazing. Okay. So this question comes from, uh, uh, from Steven, which is how would you add validation to air table? So Steven came to me with this question, which I thought Stephen always comes to me with really good questions.

Uh, Hey Vinci. Good to meet you. Thanks for joining. Um, How do you add validation to air table? And he had a very specific use case, which is a workflow that is extremely reliant on the button field. So as everybody knows, I'm a huge, huge button field fan. Uh, it's just such a good, uh, call to action. Um, so if the stream is lagging, let me know.

I should, should be good. YouTube is telling me that it's fine. Uh, but let me know if there's any issues with the live stream. Um, and what, what people, the issue that Stephen face was that he had so many workflows that would trigger off of the button using Zapier web hooks, that people were afraid to press the button.

So I have an example here, and I'll kind of walk you through it. Let's say that when you have a project that's in progress, you want a button that creates. Right. So it creates task one, test two, test three. But when it's done, you want to go ahead and have a different button field that, you know, maybe sends an email to the project owner, letting them know that the project is done.

It may be, you've got, you know, 30 or 40 zaps that run off of that button. Now the issue is that people didn't want to cook it. Cause they were like, oh, you know, do I have the right status? What is this button going to do? And so I want it to provide kind of two options. Uh, for validation and I'm sure I know you, Connor are a huge button fan as well.

So let's go ahead and add the first one, which is just checking whether the fields that are filled out are actually filled out or that they have a specific value. So let's say we only want to create tasks when the project is in progress. So let's go ahead and add a button field. So create tasks, go ahead and add a button, and then we're going to assume that we're using a web hook, right?

So I'm just using create tasks. I know there's better ways of creating tasks within air table using air table automations, but I just want to use an example with web hooks. So let's say call this create tasks and then let's give it a PR boom button. Okay. What we want this button to do is only be clickable when it's in progress.

So let's say for now, I can just give it an empty and you notice that when it's empty, you can't click, right? Because empty is not a URL. So it's just not clickable. So we want to do is when the status is not in progress. So if status is in progress,

That's when we want to go to zapier.com, that's where you would put your web hook, but otherwise we want it to be empty. So we can actually just do like this. So this is saying if the status is in progress, you know, send a web hook, do the URL, do whatever the button needs to do, otherwise do nothing. So what this adds is a layer of validation within the button, so that people who are kind of collaborators in the base are like, oh, okay.

I should create tasks. When the project is impacted. So you're actually adding validation directly into the button and you can even add a little description that says click this button only when in progress

to create tasks. Boom. Yeah. So I'll show the show, the formula again here. So that's one way of adding validation into your buttons, especially when you're triggering Zapier.

I don't know if I look at your face Connor and I'm not sure if you're like blown away or great.  

[00:12:18] Connor: I I'm actually, uh, kinda surprised that works as easy as that, because I have been using scripts to run web hooks or to trigger web hooks. So to see it work like that is actually very nice.  

[00:12:33] Aron: Oh, sorry. We're over.

Let me, let me move myself out of the way here folks. How can I, oh, I can just zoom out here. How's that. Thanks Coleen. So it's, if status is in progress, go to zapier.com uh, otherwise do nothing and then do nothing. Is what allows the button to not be clickable. Sorry, go ahead, Connor.  

[00:12:55] Connor: No, I was just saying, this is a really nice way to do it.

I actually didn't realize that you could trigger, um, web hooks like this because I was using scripts to trigger web hooks in the past. But knowing that this is a way to do it is actually.  

[00:13:09] Aron: So, let me, let me, this is actually kind of dovetails nicely with the second way. I want to show, which is much more precise or it gives you much more granularity.

So what you're saying is that you would run the script, uh, run the web hook from an air table script. Cause you're now an air table script expert is what I'm understanding. We're getting there. Um, so, and so let me, I'm going to distill what you're saying here. Connor says that instead of using the open URL, which you can trigger a web hook with, where you can do is run a script.

Now, when I'm selecting run script, what you'll notice is that there's no more kind of URL. There's no URL that we're pointing to or no formula field. It says, well, what script do you want to write? Right. So let's go, I've already written a script. So let me just go select an existing script and I'll show you what it does.

Why would you run a script? Is that it gives you much more control? Right? So one example was one we just did. We said there's only one URL we could trigger. However, with a script you can say, Hey, depending on different, you know, things that are happening, if two or three things are true, go ahead and run this script or pull this information and run this other one.

That's what's available when you run a script, so you can be much more granular and much more controlled, right? So let me give you an example of this. So let's say that our script, so I'm just creating tasks. What I'm doing here is I'm actually passing this record into the script. Let me just really quickly show you the outline of the script.

So it's going to input that's record into the. But then actually prompt you to say like, Hey, this is going to create tasks. Are you sure you want to do this? Right. So that's the first thing that this script does. And it adds a layer of validation, which is kind of answering Stephen's question, which is how do I let people know when they click the button what's going to happen.

Right. So you can actually write that in the script itself. And then you can also do the validation of like, oh, is the record in progress. Oh, okay. If that's the case. Go ahead and run the web hook. Otherwise tell the user like, Hey, your project is not in progress, so I'm not going to go ahead and create the tasks.

You can do this in a formula. But what I love about this is that actually prompts the user of like, Hey, this is going to happen. Do you want this to happen? Yes, no, you can create really cool logic. So let me, instead of just kind of talking through the script, let's run one. So let's say it's in progress.

We're going to go ahead and click here. Create. And it said, Hey, this script is going to create task. Are you sure you want to do that? Yes. Checks, if all fields are valid, project status is in fact in progress. And then it runs the web hook, which you can then send to Zapier, or you can even use the script to create the tasks.

You can do all that. But then let's say that the project is not in progress. Let's say it's done. You can create. And you can still say, Hey, are you sure? Yep. And it says, project is not in progress. So we're not going to go ahead and create the tasks. So this is two things. One it's prompting that user. Are you sure you want to do this?

Yes. Oh, in fact, you can't. Here's what you got to go ahead and do. Um, so I personally love this like double validation, especially as a kind of a hardcore button user.  

[00:16:48] Connor: That's really cool.  

[00:16:50] Aron: So, Steven, uh, let me know if this answers your question. So I'm already seeing some folks who are gonna use this. I'm happy to share the base just so you can get the outline of, uh, the script.

So I can go ahead and share that I'm going to drop that into the chat. I knew that Stephen, this would be a right up your alley. So there you go. You can go ahead and copy that and you'll get the kind of script outlined and should give you everything you need. Amazing. So I'm gonna, I'm gonna assume that this, uh, answers your question.

Amazing. Appreciate that. If folks want to ask questions, you can always either DME on Twitter or there's a form link that I'm not going to find now, and I'll drop it in the chat later. Um, yeah, this is for me, like I love the call to action. And I love the fact that it kind of has validation built in. So I'm a huge fan of this kind of workflow with scripting.

There are some limitations, unfortunately, you can't run an automation from a button. Uh, hopefully that'll come out. If that's the case. That would be amazing because then you could run the script in the automation, although you wouldn't have that like second validation. So there are some, some drawbacks here as well.

Connor, any questions before we move on to talking about why's?  

[00:18:17] Connor: Uh, no, I mean, I think a quick comment is, uh, so I've been, um, playing around with scripts for probably two and a half to three weeks now. And right at the beginning, I was kind of. And not, I wouldn't say intimidated, but like, we need to just look at the code, that kind of things like a lot to process at once.

But, um, I think if they're like very specific use cases that you're trying to solve, there are a lot of really good resources out there. I watched errands strain, um, that he did with what was his name? Geo. Geo. Yeah, so that was a really good starting point, but, um, I found some really good use cases to use scripts and buttons for.

And one of them is inside of Integra. Matt. One of the things I find very frustrating with Integra man is I'm like in Zappia where you have a trigger step, we have a Recode moves into new view. You don't really have that an integral mat. So an integral Matt, what happens is every 10 or 15 minutes or whatever, depending your planet is that.

Through all of your records that sit in that view. And if there is a record in that view, it will run the workflow. And that leaves a lot of room for mistakes. For example, certain records not moving out of the view as soon as the automation has run and a whole bunch of other things. So a way that you can actually recreate.

The new trigger in view trigger that sits inside of Zapier is actually by creating a button that you can then use to trigger a web hook inside of integral mat. And then, then that starts the workflow. So I've been using that a lot. For example, sending follow-up emails now, instead of having to manually move records into view, I can just click a button and that then triggers the workflow inside of, um, integrate.

And yeah, it's been a real game changer, so it's definitely worth looking into,  

[00:20:14] Aron: so I, I think we should rename, automate all the things to button plus simple scripts, plus web hooks like that. I think, you know, encapsulates the three things we talk about pretty much every week. So I'm glad that you're now at convert.

Welcome to, uh, the button plus script plus web hook. Uh, uh, so, um, uh, do encourage everyone play around with button, play around with web hooks, play around with, uh, web, uh, uh, scripts, simple scripts. And, uh, that's, that's pretty much all you need to know. That's all, this is what the stream is about is just getting people to use buttons, scripts, and Webhooks, for sure.

Awesome. Cool. All right, let's get to our second kind of topic today. You came to us with this, or you came to me. To talk about wise or wisdom. What are you calling it?  

[00:21:11] Connor: I'm calling it wisdom because it reminds me of, was it tree?  

[00:21:15] Aron: Okay.  

[00:21:18] Connor: I might be wrong. Um, but, uh, Yeah, I think I saw the wisdom in the chats. So maybe, um, whoever's in charge of that, um, account can let us know which one is right.

But yes, whizzed. So, um, I recently made a video on my channel, um, looking at a few different, um, tools that you can use to level up Webflow projects. And one of the tools that I reviewed was Wiz. So, um, I just want to say straight off the bat, I haven't had a full play around with was yet, but, um, I have watched beer demos on how to sit up if I think, and long story short, what was, is, is a way to build a backend for your web flow.

So as we all know, workflow has certain limitations when it comes to, um, building backends, user accounts, processing payments, all of those types of things. And, um, what was, does is it allows you to create. A lot of the functionality that you might see in tools like bubble or even something like, um, why code to some extent and integrated directly into your web for project, meaning you can still use web flow to just build your entire front end, but then you can use wizard to basically build a back end, set up workflows, set up user accounts, process payments.

This toe looks very, very, very promising. So, um, I mean, in terms of how the setup works, it's pretty straight forward. Like with most third party, um, integrations, you just grab a code snip-it from their website, you embed it into your web flow project. And then what you can do is jump into Wiz and start seating up.

Workflows logic databases and connecting it directly to it. And the cool thing about it is Wiz has built this to look quite similar to web flow, which means that if you are a heavy whip flow user, you will be familiar with the interface. And so in a nutshell, it is going to be something that is going to potentially allow us to build more app like platforms inside of web flow.

Hmm. Um, there are two specific use cases that they have made little tutorials about on their channel. One is to build a task management app, which is phenomenal. And the other one is to build a client, um, project dashboards. So if you run an agency and you kind of want to let your, um, Customers know how your projects are progressing, then you'll be able to use Wiz to basically build the client dashboard.

And I'm really excited to see how this is going to work out. I'm going to start working on a little demo soon that I can show people. Um, but if you just want to get started immediately just watching these videos, um, is a fantastic place to start.  

[00:24:41] Aron: I am Connor to be Frank, a big, big fan of my current stack Webflow air table, Zapier member, stack parabola, if I'm being fancy.

Um,

and then there's like, there's, there's, there's a decision tree that is getting harder and harder to nail down. Like why code or member stack outset? How do you kind of navigate? Okay, I'm going to, I'm going to use wised. I'm going to call it wise. I think it's wised or wisdom makes no Wiz needs an H it would be w H I Z, Z E D.

If it was whizzed, it's definitely wise. But beyond that, um, how do you, how do you think about where this fits into that more broader equity?  

[00:25:34] Connor: Okay. It's a really good question. So obviously there are tools out there right now, like members' stack outsider. There are a few other ones out there that basically allow you to do a few of the things that you can do with this tool.

Um, and so. My main thought on the matter is there are a few things that wizard or wise to allow you to do, um, that you currently can't do with the main tools, for example, member, stack, or outsider. One of the things that I am very interested to play with is the IR table integration. So right now, um, the, you, if you want to build, um, like user accounts with the.

With like a link to a workflow. CMS, that's pretty much what you are limited to, um, inside of member stack. But even with that, there are significant limitations that come with only been able to use one particular collection inside of web flow. What you'll be able to do with Wiz is actually import an entire ear type.

Table and then filter it based on users. So for example, you can have a table that you just showed us for your project and associated with that is a particular customer. Now you can just embed that table into your project and then we've whizzed filter it out based on, um, whoever is logged in at the time.

And so. In short, what you'll see with a lot of these tools like member stack and outsider is they solve quite specific use cases. So membership accounts, you know, online courses, those types of things, but where is what. Think is happening with west or what I'm hoping to see from Wiz is that it's going to move a lot more towards a toll that gives you a lot more freedom in terms of the use cases that you solve for now.

I do want to say that it is still very early days. Um, so I am definitely not saying that one is better than the other. I think it's still to be seen what kind of usage. Are solved with this toll. But one of the things that I think is promising about it is just that it solved for Y the use  

[00:27:49] Aron: cases. So you're kind of seeing that this is maybe a layer of that, like app builder functionality.

That's not going all in with like a bubble. Right. But it's not solving for something vertical. Right. Which is like memberships or email. So it's kind of a in-between. And there's a great question from Kyle, which I think is like a really good one, which is, you know, what is the learning curve, right? How are you, how difficult is this to get started?

And, you know, do you see this as a good place to start for, you know, your MVPs or more for like, okay, this actually works. Let me build something more complex. Let me build, you know, build out with wised, which we're now confirming as the right way to.

[00:28:37] Connor: It looks like we were both. Right. Okay. Then it's like Zapier and Zapier, very conflicting. Um, to answer that question, Kyle, um, so I mean, it really depends on your starting point. So if like, I know my way around Mim the stack, I know my way around Zapier. I know. Both. Um, and there was definitely a learning curve involved with that.

If you are starting from scratch and you are not. Yeah. You are not familiar with, um, member's stack, then it makes sense to look into, uh, into a tool like this, if it solves your use cases. So with, in order for me to build a lot of the functionality that I have inside of the UNICOM factory, It involves a lot of hacking together, which I think is quite difficult to pick up if you're just getting into the tools.

So I use a bit of custom code. Um, I have also, um, managed to set up a few things that, um, I think are not very common ways of solving certain use cases that takes time to learn if you're starting from, but if something like wise, sorry. This use case straight out of the box,

more of the use cases in one is going to take less time  

[00:30:10] Aron: to learn.

Hey Connor, can you hear me? Hello? Hello? I think I cut out  

[00:30:18] Connor: twice.

[00:30:23] Aron: Hello. Hey, Connor testing. Can you guys hear me? Test, test, test. There we go. We're back.

Okay. Yeah. I,  

[00:30:36] Connor: I can hear you. Can  

[00:30:37] Aron: you hear me?

Hello, Connor. Can you hear me? I can. Hello, testing 1, 2, 3. All right. Sorry, folks. Connor. Can you hear me? I just had to reset my stream here at some of my wifi crashed. Hello testing. Can you hear me Connor? Yes. All right. Sorry about that folks. My wifi crashed. Uh, so we're back. Let us know, give us a thumbs up in the chat.

Sorry about that. Okay. All right. All right. Sorry about that folks. Uh, so folks you were answering what you would use. Uh, why's now whizzed, whatever it is, surface. Okay.

[00:31:27] Connor: Shall I sum up my answer again to, cause I'm not, I'm not exactly sure where I cut out.  

[00:31:32] Aron: Just give us a, give us a brief one.  

[00:31:35] Connor: I think you liked that from the memory, the summary for what stack you should learn. If you are already familiar with member stack, Zapier, stick with that for now, I'm definitely going to be sticking with that for now.

Um, because I already understand how it all works. If you're just getting started. Or you haven't chosen a stack at all? It probably works just, um, trying out something new like this, because I feel like it's going to solve a lot of use cases that, um, might save you, having to learn how to use Zapier and integral mat and all those other tools.

[00:32:10] Aron: But I'm so I'm going to stick with my stack. I'll be honest. I can't, I can't learn another tool, but if everyone, if folks use it and, uh, find really cool use cases, please let Connor. And I know I'd love to showcase a built-out project. Uh, we, you know, showcase one showcase one every month. So if you build something really cool with Wiz or wised, uh, let us know, and we'd love to showcase.

Cool. Okay. Let me share my screen with you. One more time corner. Let me do that, sir. Folks. There we go. All right. Okay. Sorry about that. Let's talk about carefree. So this is our project of the month. Uh, and the reason I picked carefree is that, um, carefree is actually, you know, close near and dear to my heart.

Let me tell you what it is first. So carefree is a, um, charity out of the UK. Uh, built by Charlotte, who I knew and what it does is that it takes hotel rooms that are unused. So, uh, the occupation rate, I used to work in travel for hotels, you know, on a good hotel hovers at 75%. So they'll have 25% of their rooms that are unoccupied on any given evening.

And so, you know, Charlotte had those great idea because in the UK, there's this, um, kind of concept that is Irish. I guess maybe not has a formal name for north America, which called carers people who take full time care of their parents or relatives who can't care for themselves either because of age or sickness.

And it's like a labor that goes unpaid and these people never take a break. Right? So they're taking care of their family. 24 7. They have worked just like. And she had this idea to connect these carers with unused hotel supply. So you, as a carer can say, Hey, I want to take a couple of days off. I don't have, you know, money or, or, or the ability to, so they'll help you find a free room that is not being used and you could stay there.

And so let me just quickly share their website here and I'm gonna drop it in the chat as well. So Charlotte, let me know that they're always. Kind of looking for volunteers. So if you guys want, are interested in carefree and the reason I thought it was appropriate for a no co-talk is actually because it's all built with no coat.

So Charlotte reached out to me, I think over two years ago and said like, Hey, you know, I have this idea, how can we make an MVP to create. This marketplace, not a marketplace, but like kind of a connecting between carers and the travel industry. And since then, it's completely blown up and it's still today all built on no coat.

So they have two areas. So they have a search, a stack, right. Which is finding unused hotel supply. And then another one, which is people referring carers. So finding carers, validating that they are in fact carers and then giving them. To that search supply. So member member, uh, maker pad shared, uh, an interview where they talked to their CTO and talk about all the different tools that they use.

So they've got front for communication type form for all, uh, um, you know, forms and things like that. Uh, some sub, which was cool, which I didn't know, which is kind of a way to validate user's identity. So if you want to make sure that people are who they say they are. Photo IDs and things like that, which I thought was really cool.

Big member stack users. You can see that I no longer participate because air table is not one of the tools mentioned. Uh, and that's probably because I started working at your table and then couldn't, uh, uh, spend as much time working with Charlotte. But do you encourage for that? Uh, you know, non-technical folks in have just using no code tools.

[00:36:17] Connor: Great, great. You just.  

[00:36:20] Aron: So, uh, there's some, so that's it. That's all I just want to, this is just a big, big shout out to you. Carefree, uh, shout out to Charlotte for all the amazing work that she does. And if you do want to help her or interested more in the stock, I'm happy to connect you with Charlotte. Uh, she is always looking for more.

And, you know, for me, it was actually one of the, the, my first, if you want consulting gigs or whatever, just really trying to get my hands dirty with no coding. It was a great way to start. So do encourage you all to check it out. So before we go, before we go, that was our last kind of topic. There are some questions from the chat.

So we've got a question from , hopefully I'm saying that, right. Which is a great question for you, Connor. Uh, let me try to find it. Here we go. Question confused between mat and Zapier. Anyone has a particular advantage over the other. I'm sure. Connor, you can spend the next 10 minutes talking to us about Zapier versus entanglement.

[00:37:24] Connor: Yeah. I mean, at the end of the day, both tools serve the same purpose. They allow you to automate certain workflows now. Um, there are definitely some advantages there. Zapier has over integral mat. For me personally, I feel that Zapier is a bit more reliable, um, from my own experiences, like I've had moments where certain workflows inside of NTT.

Did not work and, um, couldn't figure out why. On the other hand, integral, Matt has quite a few additional steps or toes that Zapier doesn't have. So one that I have discovered that is really good is called the. Iterate I believe. And basically what that will allow you to do is to cycle through an array of records that you might have linked inside of an ear table record.

And that is something that you can't do with Zapier. So in most cases, if you just want to do basic workflows, Zapier is a great tool to get started with. It's quite user-friendly, it's quite intuitive. As soon as you want to build slightly fancier things. Um, you're going to find yourself with a few limitations with Zapier and that's where integrity kind of fits into it all.

So, um, I think for most people just starting setting up workflows are definitely start with Zapier people who, and then as you evolve, you can then start using tools like integument to do more fancy stuff.  

[00:38:56] Aron: Yeah, I totally agree. So zap, you're usually more reliable. Sometimes, uh, less powerful than Integra mat.

The learning curve on Integra mat is a little steeper note. A lot of folks prefer Integra mat cause it's cheaper. You know, I'm more of the advice that like whether you're using Integra mat or Zapier, your time is worth more than whatever those tools charge you. So I usually try not to anchor too heavily on price unless you have a very, very heavy.

Task usage. And one example of that is the tweet 100, where the way I had built it, it checks every single tweet that a member tweets and then checks whether it's the first of the day, you know, that was thousands of tasks each day. So in that case, you know, integrity, that was better. So those are kind of the, the, the, the variables that you should think about when deciding between Zapier and, uh, integral Matt.

I am. A article that a new newsletter that had written around integral versus parabola versus Zapier. Uh, so kind of thinking about how do you decide between the three parabola, less popular these days when they've raised their price in and much more e-commerce focused, but I think still a relevant article today.

So one more question, and I think we've got a question from VNA. Hopefully I'm saying that, right. Uh, which is. Will member stacks survive the announcement of web flow of their native membership platform during no code conference. So there's a lot of assumptions, I think in this question, which I think is great.

One is that there is a membership functionality coming out of web flow. We saw that with the pixel geek, uh, stream two, three weeks ago. I don't know, time is, uh, what is time? My, I don't know about you Connor, but my answer is like member stack will survive and will thrive. Right? Uh, I think member stack has heard, and Webflow has talked about memberships for years now.

Right. And if it was so advanced and so as, as good, if you will, as member stack, they would probably would have announced it by now. So I don't expect a web flow to release. Uh, super great membership platform that will rival member stack. And I think it's interesting. It'll push member stack to create more functionality, to go deeper to, you know, iterate more.

And I always, I'm a big fan of competition in terms of tools. So I I'm answer is no. And I'm excited to see how they'll compare.  

[00:41:42] Connor: Yep. My answer is no as well, only because. People sometimes forget that member sec, doesn't just serve web flow. They actually have a way wider community base in like actual people, people that actually code.

So I feel that overall member stack only makes up a smaller fraction. Um, all like, or at least the users of members only are not that many whip for use as we may think. So I think there'll be fine. I think the next thing is, is that. They've been working on 2.0, um, for a long time now, which I'm hoping will be done by this year.

And that will, um, probably be an improved product that will have a lot of feedback and learnings embedded into it that they've picked up over a year. So I think you kind of nailed it a bit. Like we don't know what flow is going to be launching with. Um, you know, when they launched with flow equals. That was very, very in VP.

And I know a lot of people who are waiting for really long time, but we probably eCommerce you ended up just sticking with, um, the Shopify integration or, um, with, I think it was Foxy was another tool that people were using. So I think will it make a dent potentially? Um, I think only time will tell. Um, but I think overall they're going to  

[00:43:06] Aron: be fine.

I have, I'm not a complainer, but I have a sh a gripe to share Connor. And I don't often do this couldn't products. Please talk no 2.0, I hate this idea of like two, 3.0. Or like we were on version. Not like we're, it's a SAS product. Just, just release, you know, just keep it. It's not like you want to make an announcement out of it.

I get it. You can stagger features, but versioning on the web makes notes. It's not, I don't want to, I'm not going to download member's stack. I think a lot of companies do this. Integra. Matt has been doing this, like just, just release the thing. It's okay. Don't have to number it. That's it. I'm excited for both of these no numbers.

[00:43:52] Connor: I think it's mostly code for, we are not going to ship any more product improvements until we've launched this really big update that we've been working on for you. Yeah. And I'm like,  

[00:44:02] Aron: just cut it, just release it into smaller pieces. Like we're all like, oh great. It's 1.0 is dead. Let's stop using this product until they launched 2.0, that said I'm not great.

I have to end by saying Dunkin. If you're watching this, I love you. I love the price. Just, just no numbers please. Um, that's it. That's it. Okay. I think that's a good place to end. Uh, no-code talk, I don't know if there's any other questions that folks had, um, apologies for a little choppiness today. Um, no, that's cool.

So really appreciate, uh, you Connor for joining. Um, I have a one small announcement that I will not be streaming next week and I have a very cool. Uh, streaming related, uh, announcement. That's going to come early next week. Uh, a T T 2.0 no, I'm joking. Uh, I will share more on Monday or Tuesday. Uh, you're going to see something pop up on the ATT calendar.

That's a little different than what you're used to. Uh, so it's going to happen next Thursday. I'm going to share more early next week. So no stream next week and back in. Okay, well, thanks so much for joining. Y'all really appreciate great to see your faces. Great to see your face Connor and we'll be back next month for NOCO talk.

Bye bye.

‍