What is Zapier Transfer? with Taylor Halliday | AATT #65

Zapier is getting into the syncing game and Taylor Halliday is here to show us how to use it.

Resources

Transcript

Aron: Hey Taylor, welcome to "Automate All the Things". We're so excited.

Taylor: And thanks for having  

Aron: me. Yeah. So, uh, I'll let you introduce yourself. I'm really excited that you're here. Uh, I've been, you know, such a Zapier fanboy for so long, and I feel like I talk about Zafira every single stream. So I'm so excited that you're in particular, you're here to kind of talk about something new that you've launched,  

but before we kind of get into it, uh, how about a quick introduction into yourself, Taylor, and what you do at say.

Taylor: Sure that'd be great. Uh, so my name is Kayla holiday. Um, I, uh, run a new product, zap your, uh, call transfer. Um, you know, we've been working on a transfer maybe kind of in and out for about the past year or so. Um, you know, uh, more recently we really start to, you know, make a big push towards. Bring it to market and kind of productionalized in a meaningful way.

And that's kinda what we'll jump into and, uh, you know, the kind of life before that was really spending a lot more time, as they closer to our R and D functions, really testing the waters with I'm gonna transfer things like it, can't help capabilities and really have pressing the envelope on, uh, Zachary's existing, um, offering and trying to figure out where we can add additional value.

Aron: Yeah. Yeah. So I think, uh, so Hey Coleen, Hey Joel. Just saying hi to folks. If you're in the chat, let us know, give us a little. Um, you know, I I'm, obviously I've spent a lot of time in Zapier and I remember, you know, Zapier, when I first touched it, it kind of like blew my mind. Right. I was like, insulating, this is going to change people's lives.

And I think Zapier has brought in a whole new echos, not ecosystem. Is that the right word? You created this whole new thing, then now everyone replicates. Right. And that there's a huge competition around it.  

So maybe for folks who aren't as intimately knowledgeable or used to the tool as we are, can you give a quick intro into what Zapier is?

And then second, like where does transfer kind of fit in to zap years general?  

Taylor: Totally. Um, so taking a step back, uh, Zapier is, uh, you mentioned, uh, very, um, you know, widespread automation tool. And so now what does that mean? Uh, typically, uh, the world in which we operate is that there are, you know, events, we call them triggers and those events, uh, kick off a downstream series of actions that is kind of vanilla, um, use case if you will.

And so like, you know, materially, what does that mean? It could be as simple as I have a new contact that appears in Salesforce. And I really would like to get over to MailChimp. Zapier is perfect at doing those types of things. Uh, you can blow that complexity way out and make a much more largely on business use case out of it, such as get Adam to MailChimp, you know, kickoff or add the multiple CRM and have a bunch of bells and whistles go off.

Uh, really that's where, um, you know, another huge piece there of have acid as equity comes into play, which is, um, our breadth of integrations where, uh, I think we're at 4,000 plus at this point. Um, but yeah, so there's a large, large, um, kind of surface area and things that you can automate was happier and ever-growing as well.

And then, um, second part of the question kind of where does transfer fit into this whole mix? So, uh, Nine 10 years now in operation. Um, again, the paradigm is very much been, uh, like an ad hoc automation style platform. Uh, but since then, There has been constant inbound about, Hey look, you know, Zapier's great.

I have productive. My example. I have a new, um, contact that appeared inside of Salesforce. I want to get them over to MailChimp, but Hey, I already have a hundred contacts in Salesforce. What do I do with those? How do I get them over? Right. Um, and to be Frank this entire time, we kinda, the attitudes. Makes sense, the use cases there, um, you know, but that said, like we're really focused on the automation aspect of this workflow.

And so, uh, we hear you here are some workarounds. You can go back there and try to export a CSV and, you know, see if they have an import CSVs and other things. There's a few different ideas, but really we're of, you know, the, the view up until recently, it was like, this is a tangential problem. And probably outside of our purview effectively, um, you know, we're happy to help, uh, to some degree, but, uh, you know, there are other workarounds and so.

More recently we've been kind of stressing or pressing like that assumption, trying to figure out, you know, is there something actually there for us, you know, workflow sense. And so that is really kind of what born, uh, the original Genesis of the idea of transfer is kind of like if we were to add, um, you know, not just ad hoc, you know, at the moment, uh, automation, capabilities and trends to exactly what.

Uh, start to look at, like, what does that your look and feel like with the ability to like, look back at your existing data, your historical data, um, does that open up kind of new possibilities with how you, you know, create workflows? Um, and so again, that was kind of how the Genesis trends were kind of started and then as we'll hop into it, uh, this is, uh, uh, pat first manifestation that'd be world or of that, um, exploration.

Aron: Yeah, no. So I remember, uh, You know, seeing transfer and having like an expectation of like, obviously that's like a, such a natural next step, right. Because you know, when we think of automation, you've got like, if this happens, then do this right. So those kinds of trigger and then actions that you've been so focused in.

But I think what, you know, over the last 10 years has been so many flavors of that, right? There's been, you know, those kinds of scenario type situations, or, Hey, we're going to like really verticalize, you know, our. We're going to go so deep into this API, but we're only gonna have five connections that some of your competitors do.

And, uh, and we talked about this like ETL type transactions, right? So just, you know, if this, then that is huge. Uh, and I mean, in the workflow fund, not the company, uh, and, uh, Zapier kind of dominates that space. So transfers just seems like a natural next step. Now I'd love to hear from you. There's so much you can do around sending information from one place to the other.

And we're going to jump into actually demoing that in a moment, but places the transfer, where it is today into that ecosystem. So what, it's good for? What it isn't good for where you hope maybe that it's good for. So talk to us a little bit about where it sits today.  

Taylor: Yeah, for sure. So again, we will hop into it and kind of have some more, um, substance combo we're talking about and in a high level right now, but, uh, trans residents today, uh, we have, again, we've tried to answer the need of moving existing historical records, um, you know, with, through an automation.

And so what that means that you can go ahead and select an application, look at the records inside of there that you'd like to actually move manually over and transfers phenomenal at doing that, that checks a lot of boxes for a lot of use cases in terms of. The example of, you know, why I just gave, um, others as well, such as like, you know, migrations and some few more that we'll get into.

Um, and so we kind of decided to stop there, uh, put that one out there and try to check a box on those days and kind of see what came of it. And, um, as you, as you can probably imagine it again, if you're a one-time average user, That's probably no surprise to you that a Zapier can be, uh, take it, take an intern and twist it in a lot different ways.

Um, our users are incredibly, uh, uh, they Excel at, at, at, at bending Zapier in ways that we'd never thought possible. So one of the fun things about that is you get a lot of interesting use cases coming back and see that coming back. We also mentioned as well. Uh, we have a very vocal, um, user base who is very enthused about the product, which, you know, makes.

Uh, no shortage of find when you're working the product development side about path, um, ideas and smells about where to take it to. And so again, I wanna stick with this theme of ad hoc. And so right now, a transfer is very much an ad hoc tool. Like I said before. And that's we intentionally started is that to see where we kind of go with it, there has been constant, um, you know, like push or pull, if you want to say that around like, Hey look, you know, Zapier in itself is not necessarily ad hoc.

It's an automated tool. What does an automated kind of transfer. Um, and so, you know, to there there's a couple of different, like offshoots of it there, you know, potentially interesting, you know, you have that, you just said the ETL use case, it's a very popular class of tools. Um, distinction now ETL is very much a, uh, a class of tools that you would say, like live in enterprise land, um, you know, um, big distinction about, uh, ETL, typically that user base, uh, super familiar with it.

It's a large scale, you know, data kind of movement tool. It's it's, uh, the Marquis kind of things with ETL. Is it typically there to connect. Um, you know, very large data lakes, data stores, whatnot, and, um, you know, Zapier again, we can do that type of stuff, uh, is just not off. It's just a little bit off the beaten path for the typical SMB.

Um, you know, we have a perspective that we have. And so anyways, I'm not going to say that that's an interesting thing to us, for sure. Like, you know, how, how do you kind of automate this thing potentially, um, in like, you know, not a fully teal, but what kind of makes it look more like that? That's. Another option too, is, uh, you know, or a piece of feedback we've heard quite a bit is around kind of updated records, um, with, uh, uh, the transfer, having it be a little smarter about, um, moving things back and forth.

Um, and if you pair that with automation, uh, you start budding up against the Keno, this notion of how can sank as well. And so, um, that has been, it would be heard these not feedback around. Um, I think that's interesting as well. Um, That, uh, it's also being pressed on that transfer right now, spits itself, and tickets have separate, um, separate experience, separate tool by design and make sense.

Um, but we have a lot of folks asking for working on different ways to kind of integrate that with an existing zap. How do I kind of, you know, use transfer, um, in Panama better with some existing workflows. And so those are the things also we're thinking about.  

Aron: So I want to come back to what you said at the beginning where you said people are very innovative in twists, Zapier into ways you don't expect.

And just on behalf of everyone who watches and enjoys, "Automate All the Things". We'd like to apologize for that because we are those people, right? Where you, you know, you give us one thing and we twisted and turned it into something else. And I'm hoping that we're going to do the same thing with transfer and kind of come back to you with like, yes.

Sink in. There's so much we'd love to do with this, but just how do we take what already exists, right. Which is transfer one ad hoc way of moving data from one to the other, and then actually use that to kind of patch holes in our workflow. Right. So, uh, you know, I'm, I'm personally excited that there are more and more tools kind of thinking about like, yes, we did the, you know, if something happens here, let's send it over there, but that's just one larger piece.

Challenges of working in multiple systems, which is everyone's reality, to be honest, especially mine. Um, there's a question in the chat and I'll let you answer this one. Uh, what does ETL stand for? And I think more generally, what is ETL? So what would be that other layer that you kind of call ETL?  

Taylor: Uh, sure.

So ETL, uh, acronym stands for extract transfer load. And I love the question. Like, what is it ETL has I, uh, from, from D from doing a decent amount of research and kind of talking with folks and doing user interviews, I told you about an inbound and questions about like this, you know, looking like an ETL and whatnot.

I can definitively tell you that no one has a consistent definition of ETL. Um, just from my experience from asking around quite a bit. Um, and so ETL describe it as, uh, again, like I said before, it's, it's much more of an enterprise type of, uh, classmates. Uh, it's typically already give a definition to it.

It's typically involved in moving data in and out of I'd say data lakes or large kind of analytical databases. They think of like Redshift big query or whatnot. If you're a large enterprise, um, you would get an ETL typically for me to have a use case here to, um, you know, um, seed your seed or like, you know, uh, move data from a customer, some of your business, um, databases, Postgres my SQL over to let's say like your Redshift and since on a nightly basis.

It could be a ETL type use case. Um, obviously there's those that use cases not really fall, uh, super within the cross hairs of your, let's say more micro SMB, probably not a ton of data lakes running around, but you can start to see where there's like some crossover there in terms of capabilities. We talked about how look back bulk records, whatnot.

I can kind of see where, um, you know, people have to have crossover  

Aron: and interest. Absolutely. Absolutely. So, um, so for folks, we're going to jump in here in a moment, but if that's a place, you know, zap your transfers, you know, folks of "Automate All the Things" and no coders in general, kind of have this like never ending list of tools that they want to try it.

Uh, so is Zach your transfers today is like I have data in tool a I want to moved it to. In a one-way fashion. Right. So one way and like ad hoc, right? So this is particularly useful kind of, as I'm looking at this, and as we talked about, it was like, I'm starting a new tool, right. I'm using a new tool. I have data here and I'd like to move it over there and inefficient manner, or maybe I have a recurring new pieces of information.

Right. And so the tool, the use case we're going to jump into is like, Marketing. And I don't know why marketing marketing always gets blamed for this. Like marketing sends me a report every Monday morning and in CSV and I need to move it to this other tool right. In an efficient manner. Right. And that's really annoying to have to copy paste, worry about formatting, things like that.

And so transferring. Zapier, which is not Zapier. The transfer by Zapier is that like, that's where it fits. I have tool information here. I want to move it there. I want to click a button and it does that for me on an ad hoc basis. Um, does that feel right for you as a way of like explaining where it is today before we jump into an actual demo and folks, if you have any questions, you know, shoot, go ahead.

Taylor: Yeah, no, I think that's. Um, and those are, you know, what look for these use cases. Um,  

Aron: yeah, amazing. Cool. Okay. Well, let's jump in folks and, and, you know, Taylor's here. If you have any questions, uh, feel free to poke and prod, and  

we're going to jump into our use case for today. One that I dreamed up, but actually feels quite close to reality, sort of that the way I've thought of framing, this was like, okay.

So imagine I get. Every, so I, you know, I, what does that movie, like the always be closing where they get like a stack of leads every Monday. So we're going to replicate that, but in the modern, uh, 20, 21 kind of environment where every Monday you get your 20 leads. Right. But, uh, you get these in a Google sheet, right.

And you are a modern. You know, knowledge worker. And so you need this information in air table, obviously. And so we're going to transfer this on an ad hoc basis from Google sheets into air table using transfer by Zapier. So folks, again, if you have a use case that you're wondering about like, oh, it does this.

Let us know in the chat, Taylor's more than happy to answer that. Uh, and if you have kind of things you wish or would like to do and wondering if you can do them, drop them in the chat, and we're going to have a bunch of time today, uh, to answer those questions. So cool. So Taylor, this is our starting point.

This is going to be our end point, right? So structured information here. I've got the name, the account, the email phone, some of this information. You know, lives here, some of it doesn't. So let's talk to me about how we go about taking this and migrating it over to irritate or to whatever system on an ad hoc basing using transfer by Zapier.

Taylor: Sure, absolutely. So first step, when is after.com left-hand side of CA uh, uh, but it says transfers or there. Perfect though. If you don't have one and you will see the screen, but feel free to jump in and let's make one.

Aron: So first question I guess, is, does this kind of already work with most apps that Zapier integrates with?  

Taylor: That's a great question. And maybe I should work quickly touching this a little more deeply. So they answered. Okay. Um, it does not work with, uh, I'd say even the majority of our apps. And so it's another thing that it's interesting about transfer with regards to Zapier, um, or globally is that, uh, I would say over the past, you know, however long, eight, nine years, um, you know, we've really encountered early on created a, you know, a good spec for what our integrations look do and feel like I'm stuck with that story for quite a while.

Um, and I say that if you were to go to Zapier and build integration for your application, um, or what partner way or whatnot, um, there's a certain set of API and whatnot and bindings that you can use a hook and your app into Zapier. And that's how we have our app platform, frankly, uh, without a set of capabilities, we would not be able to make transfer.

So in order to make transfer, what we had to do here is actually expand out this capability of our existing, um, uh, we've called app platform. Um, to allow us to go ahead and do things like historical look backs and paging and whatnot. And so, uh, this has been definitely a shift and probably actually the first major shift in the app platform that we had in, um, maybe since its inception.

Uh, and so it's all within the need also like creating experience in this app. You're trying to figure out, you know, are there habits, you know, again, more, uh, different use cases that we could actually go ahead and serve. And so. Again, circling back to your original question. No, the actual apps and actions are ones that we, um, most part handpick, there's some partners we worked with, um, not really, you know, a demo basis to have them incorporate these capable capabilities if you want their app.

Um, and so, uh, what you see here is really just an actual expansion of our existing app platform.  

Aron: Yeah. So it kind of has probably those core ones that you'd imagine that. Right as being important. And what you're, what I'm hearing from you is that you've actually changed your platform in order to allow others eventually to scale and have that same breath, you know, eventually on transfer is that kind of division as well.

Taylor: Totally. It's a definite division. Let's say transfer again. And we talked about, it's like, you know, a version of what we think of Zapier as having both capabilities look like, but there might be other off shoots as well in the future. And so, um, and the only other thing I'd say too, is that, uh, actually even today, uh, it's our developers able to modify their apps to, to accommodate COVID transfer  

Aron: capabilities.

Okay, cool. So folks are watching and your ability, you have an app, you can modify it and get it into transport, which is.  

Cool. So I'm picking Google sheets, which is our kind of starting point. And then we're going to go to this table and then I want to create record, right? So I want net new records from here to here.

So Airtable part is very simple based as I shared a template sales season. Uh, contacts are what I'm importing. I'm curious to see how this, uh, account linked record is gonna, cause I, I know that these are not existing, so we'll see how, how, uh, zap your transfer takes those. And whether it creates a new link wrecker, which I expect it to do, but again, we're projecting ourselves into the future here.

So we're going to take every spreadsheet row and create a net new record. And this is the example of like ad hoc. Boom.

Yeah. Google sheets. Boom. So not only does it, it seems to connect to existing apps, but it also takes those existing connections to those apps. Right. So if I've already configured my connections in Zapier to spreadsheets or Google sheets or Airtable reuses, those existing connections.  

Taylor: It's a good call out.

And so, um, not only does that, but if you're familiar with Zapier, what you're looking at right now is, um, part where you would actually load up, for example, like, um, you know, information from those, uh, uh, from those accounts. And so these are all very similar things you'd find in zapier.com. Um,  

Aron: yeah, so I think I need to reconnect my Google sheet.

No, it's okay. Let me just reconnect it. Okay. Let me go. This is on me. This is on me. Let me go, let me connect. Let me just reconnect, Mike.

There we go.

You want to allow that? I trust you guys. Okay. Thank you so much.

Let's see if this works. There we go. So new leads yet. There we go. And then the worksheet is probably sheet one because mock data perfect. Okay. So it's, uh, it's actually feels very much like you've given it a little refresh here. Cause I know that you guys are now kind of you're, you're reusing it, all those elements that I'm familiar with Zapier, but it's actually like a nice, fresh look.

Taylor: Thank you. Yeah, no again, I was trying to press that a little earlier that, well, um, this has a new capability transfer tab. That's app you didn't have before. Um, you know, we definitely, uh, have built. I use the term app platform before we, we, this is on top of other primitives or fundamentals, you'd find inside that platform.

So with that, you'd find very common things like you're going through right now, which is like an account slept, you know, um, what information said that account you care about namely, which base in your table or which sheet and your negotiate.  

Aron: Yeah, absolutely. That makes why, why rebuild the whole thing?

Right. So air table, let me see which base I'm in. I'm in sales, CRM.

Believe sales, CRM, boom, Abel

contacts. Now my expectation is that okay, there we go. So you're saying here, this actually is that step one. So this actually feels very much like a zap, right? Where in each one actually select. That table, what pulls up is each field. And it's asking me like, okay, when I transfer that information, what is our mapping from our columns in the sheets to, uh, our Airtable base.

And then my expectation is that you do this for every single tool. You know, you take data from one and you take, you move data to the other. Now, before I do this, I'm going to get a question in the chat, which I'm like 99% sure. If it's not already there is, can I edit the data between those two steps?

Right. So let's imagine I want to, you know, get the first name or use something like Zapier format or, or, you know, is it possible to kind of add a step between the two and if, no, that's fine. I'm just know that I'm going to get that question for sure.  

Taylor: Totally. So. Um, no right now. Okay. Uh, yeah, it's kind of funny though.

It does kind of goes back to one of the questions you had earlier, and I suppose that's how our climate mental cup, um, bridge effectively is mine was using this Lockie term ETL extract, transform, transform load. Um, that's kind of, it's not, you know, that, that realm actually, you know, extract, pull from Google sheets and we use Ascot transform, do something with it in the intermediary and then load isn't effective that fancy ever kind of funny way of saying, just send it over to.

Um, so yeah, that does again, has fit very well with feedback. We've heard such as, like, I want to do some intermediate transfer transmissions or filtering or whatnot, but those are use cases. Exactly.  

Aron: Yeah. So, uh, I, I, not to brag, but I know the audience quite well. And Amir already asked the question, uh, can I edit the data between the two steps?

I do promise I did not see that in the chat. When I asked you the question, I just, you know, I have this tingle in my brain that says, you know, someone's going to ask this question for sure. Uh, and Amir, I appreciate, appreciate you pulling through for us and asking that question. Um, And so, yeah, so I do kind of think, I like the fact that you're very clear on, like, this is not an ETL tool today.

And I think this is a good example of like between Google sheets and air table. Like, you can do a lot of not ETL type information, but if you just want the first name, create a first. Column here and then migrate that. So your kind of expectation today, it's like, we're only migrating the cleaned up data or the transformed data today in transfer.

And then we're just going to send it once. So here now it's more of a mapping exercise of like, okay. Name an organization. Uh we're, that's a, that's a formula field, so we're not going to fill it in, uh, because it it's a concatenation of others. Name is going to go ahead and pull. From name completely. I did a good job of lecturing mapping my field names.

There, there we go. Next is email. Hopefully it's called. Yep. There we go. And it's cool that you actually pull in a test one. I don't remember doing that. Uh, so appreciate you automatically pulling in a test, uh, RO uh, as someone who's used to working with tools that force you to test, this is a nice little.

Taylor: Phone, all credit to the transfer team on little niceties  

Aron: there. So, so this, this is where I'm curious about. So let's see what this does, right? So I'm currently inputting some text right from here, uh, which is, uh, the, the account. And now this is an array in air table. So I'm curious, uh, and we could do another test after if it, if it'll do multi reference fields or, or actually actual arrays, which I know a lot of folks are going to ask me about from transferring from Excel or air table to web flow, which I know is a very common task.

Uh, so LinkedIn is just a URL interactions as empty opportunities as a link to record, uh, at the name.

Interesting cause names at the end. And I post, I thought I'd filled it in at the beginning account. Oh, whoops. So account.

Okay, so here one second, I messed it all up. I went too quickly. So account maps to the word account, which makes sense. Name organization is a formula field department I don't have. Right. So, because that's a single select. So we can test that after I'm curious to see what will happen for a single cycle.

Let's actually go ahead and copy paste it. I'm curious to see what a single select will look like. And I imagine do I need to refresh to get this new, so let's call this department, let's call this HR and I'm curious to see if you'll create a new sync. I'm like testing your two hour live on. Yeah, fantastic.

So I'm curious to see if it'll create a new single select here. Um, and then let's go ahead save this. And if I reset up Google sheets, it's going to get the map mapping again.  

Taylor: They went to the back then. I wouldn't even gone yet. I was actually going to say on the dropdown, it's a little hard to see on the, on the, on the pitcher and pitcher for the podcast, but there on the, on the mapping steps for you originally to leave, we have a little more button, which would refresh that example or that sample, if you will, it might be running it by just kind of a little tough  

Aron: here,  

Taylor: connect to the sheets, drop, drop, drop down.

Any one of your, uh, mapping selections right now. Oh, okay. Kind of curious, is there at the very bottom of that  

Aron: as their load more, when you try to give one, uh, let me try to get one where I'm at the top of my screen. It doesn't seem like there's a, is this it  

Taylor: okay. Maybe not. Nevermind.  

Aron: Okay. Sorry. No  

Taylor: worries.

Products. Not some stuff might be in the works. Some stuff might not be  

Aron: that's going to be a refresh button eventually, right? Someone's working on it for sure. Um, no worries. That was actually a quick, so here we have department. Great. The department interaction link, record opportunities name should be named.

Okay. There we go. That feels about right. Okay. Name and organization, title opportunities. Those VIP is a true false. Okay. Next. Okay, good. So this is a good, good. I was just going to ask you, is there a preview? Okay. So this is saying I was giving me an example. Perfect. It's actually a nice,  

Taylor: thank you again, like all credit to the amazing team we have working on this.

Um, it is a fun opportunity. Uh, in several ways, one of them is kind of cake. How can we like, you know, test some assumptions and maybe campaigns and find new things that, you know, existing transfer Zapier doesn't have. And so this is one of the things we thought may be kind of cool. There's a, this would be more similar to, again, if you're familiar with Zapier, we have this kind of notion of like samples.

Like when you're building an app, you can kind of look at, and they test. This is a much more, it's a blown out, you know, um, camera find, look of that, uh, that experience if you will.  

Aron: Yeah. I really liked this idea of like, okay. I, I might not be clear on what every single, especially when I'm working for the.

Right. Sometimes folks are not like thinking of databases and they'll just be like, yeah, let me put a phone number here. Or, you know, some random number here. And that actually might make your transfer fail when it comes to air table. Right. Because if you're trying to input a URL into, you know, a single select field or things like that, or a bunch of numbers, uh, into like formula fields.

Right. And are going to be able to transfer that. Um, but this feels good.  

Uh, I'm like 60% confident this will work. Uh, not, not because of you because of me. Uh, so let's go ahead and looks good. And this is going to go ahead and transfer it over.  

Taylor: I'm not quite hit the button. Mostly it happens.

Aron: Oh, okay. So I can filter on the backend.  

Taylor: Yes. Yes, yes, yes. Um, again, so ad hoc, but you can go ahead and filter, uh, you know, which ones you want to go ahead and transfer over at the stage of the  

Aron: game. Also buy by like some, so let's say I want email. Oh. And then I could search by that. But I can't say like only I can't filter here and say like, only send those.

You know, maybe if I have a deal size that are over a thousand, this is just saying out of these ones, which ones do you want to? I want all essentially.  

Taylor: Uh, yes. Uh, but I mean, these are all, these are all, again, like pieces that of feedback we've received. There is, as you can tell a light filtering stuff, Uh, whether or not that filter is doing exact thing, a partial now fuzzy match, like it's doing right now, or like you mentioned, we had like a greater than 500 million for a deal size, for instance.

Right. Um, you know, we don't have that yet, but it's, uh, it's going to match definitely fits within the realm of stuff. We've heard as feedback as well. And so, um, but yeah, so right now, what you have, I could say it, it's very simple filtering if you will,  

Aron: but yeah, you're planting the seeds. Taylor, I have to say a lot of people.

You can see where this is going and are extremely excited about it and just where it is today. I'm extremely excited about it. So let's, let's sync this, this looks good. I selected all of them and saying, boom, boom, boom. Oh, it was gonna take one minute. Interesting. I look how  

Taylor: I love how the fact that you.

I, I, we, we rented situations in the, in the earlier versions where folks just didn't grasp how many records they were about to send. And so this is more of like a, Hey heads up, you know, you have 29 other people might have 10 thousands, you know, I might want to double check that one that they really meant to send 10,000.

So that was kind of more better confirmation for that.  

Aron: And so they're, they're here. They have arrived. Great work. Cool. You know, uh, I think we have that. Right here. So let's see the first one. Let's try to find the first one and then better is the first, let me go here. Boom. And I, so I think, congratulations.

I think we can do, we can do some confetti, those some great work. We just transferred 20 records really easily.  

Taylor: Uh, we already had a game.  

Aron: Yeah, exactly. Exactly. Oh, do I not have my confetti? Okay. There we go.

All right. Easy transfers. So there's some questions in the chat that I want to get to you, but, um, just before we get into it, it seemed like in the backend, you're kind of using that struck that you you're creating these records one at a time. So what I see as you're kind of using that existing API structure to say like, okay, we're going to fit this into the existing integration that you already have with us of just like, we're going to pick your API 20 times, essentially on a scheduled way.

Taylor: As it is now you  

Aron: are correct? Yes. Yeah. Okay. Love to see that. Cool. So one other thing that I think is really, really cool that I do want to bring everyone's attention to, is that it properly mapped that single line text into an array for air table and sent it as a linked record. Right? So this allows us, if someone kind of creates our counts, In Google sheets, one of the challenges, like you're going to have an accounts table and it's going to be a mess in, in, in Google sheets, but you've properly, or maybe our API does that or air table's API.

Does that, uh, maps that into a new record? So if I go into accounts, I should have somewhere. Yeah. You can see these new, these new, uh, records, right? Because you have to associate it to something. It couldn't find an existing. Or D D existing account. So it created a new one, but that also means that if you create a new account or an existing account, it'll find it it'll match it to your existing structure, which I think is just speaks to like the intelligence of the tools that we're using.

That it'll do that. And instantly kind of do that transfer. Um,  

Taylor: it's been, it's been fun. I was going to say, yeah, so different data types of cleaning testing. The transfer is, uh, you can imagine the complexity blows out quite a bit. There. Um, but yeah, to your point, whether or not this was taken apart was handled by, um, some gracefulness on our side and transfer or if the graceful, and this was, you know, picked up in the integration itself or maybe an air table TBD, but there's a lot of, uh, fancy  

Aron: stuff.

Yeah. And, and, you know, as a, as a no coder or someone who's not actually in the weeds of it, I'm just happy that it's graceful. And I appreciate that. So thanks. Thanks for making it easy for us. You know, and I think a second point here is actually you also map new single select fields, right? So this is an example where if someone in the sheet uses HR instead of human resources, sometimes that would actually make air table or some tools fail.

Right? Because it doesn't recognize that existing. In this case, it will create it. Uh, and what that does is that you might want to sanitize it here, right? Such that you're not creating new single select fields for errors and how people are writing, but they're relatively easy to catch here as well. Cause you can just be like, oh, that feels weird.

Let me just actually remap this to, uh, human resources and then delete that right there. Um, last question, I'm curious who. Okay. Interesting. So, uh, last note here, and this is just because I'm an irritable geek, is that, uh, it says that I created via API because it is your Xavier's connected via my API account.

Uh, and therefore, you know, from air table's perspective, I'm the one creating these via Zapier API, uh, which totally makes sense, which would be the case. If I created these via API myself, Um, cool. So I think one more thing I wanted to show off is, okay, well, our use case here was I get these every week, right?

So I'm imagining that if I get this the new week, like the next following week, you know, a new leads, number two,

and let's give ourselves like 10.

Give it a second here to load

and let's just give ourselves five leads this week. I didn't, I didn't close any deals last week cause um, I have a YouTube channel. I don't do podcasting too much. Yeah, exactly. Exactly. It. I'm not on the phones, man. I'm not calling enough people. My deals are too small. They're not giving me leads, man. I'm they're not giving me leads.

Uh, so how would I go about being like, oh. Pulling in the new leads, just to reuse all the work that we just, that we spent like 15 minutes setting up that transfer.  

How do I reapply that existing transfer into like a new one? How do I, how do I be like, okay, I want to do this again, but with this new sheet that I have.

Taylor: Yeah, totally. So there's, there's kind of two options. If you go back to, uh, where you left off. Perfect. Right there. Okay, perfect. That you should have a transfer there. Okay. So hard-stop real quick here. So, um, we carried over the notion of persistence of like a transfer just as you find it, persistence zap effectively.

Right? Right. Um, and so, you know, if you were to look at, like, for example, your zap, your familiar Zapier, to your point, they opened up the disclosure, many needed a handful of things you can do over there. Um, one of them is, uh, you can edit it the existing zap, if you will. So let's say that. Yeah, you had a as that, for instance, and you want to go ahead as the configuration, he gets to do the exact same thing with the transfer.

That would be one option before we go there, though, just throw this out. Um, or for instance, let's say, you know, you, you went through and updated or you created a new sheet, right. Um, but there's, there's an instance where basically I've seen people having data dumps just basically required to just replace existing sheets.

So catch-all options they're equipped with. You didn't have to change any configuration, such as like changing the target. Uh, Um, it's a little tough to see if I believe there should be a run again, um, on disclosure or run transfer.  

Aron: Yeah. And this will assume that I want the same, you know, original source to the same destination.

Right. But on the end screen, I could say like, oh, actually don't transfer these 10 ones because we did it last week. Yep. Okay. They won't just run it.  

Taylor: Okay. , they'll bring you back to where you're at. Exactly. And so this is going to reload back out. Everything basically  

Aron: configuration you had. Yeah. Okay, cool.

Perfect. So that's the way I would rewrite it. Let's say that they just update this sheet. I would just say like, okay, great. Easy. Like, let me just run that again for these 50 records and then, you know, we're done and that's actually like a really thoughtful way of using an existing kind of, I guess. Idea of zap, which is somewhat unrelated to transfer potentially.

If I had, you know, if you had built it differently, but because I'm a Zapier user, this actually feels very intuitive to me. Um, but then how do I edit the sheet, but keep the structure,  

Taylor: uh, at the sheep and keep the, you mean? So edit the actual transfer that target the new sheet effectively.  

Aron: Yeah, exactly.

Exactly.  

Taylor: So no disclosure menu, you should be able to click edit.

Aron: Okay. So this is essentially taking me through the steps, but with kind of my, the existing information filled out  

Taylor: redefine you got it. Exactly. So if you're only changing one thing here, it might be a lot of clicking next, but on it's not.

Aron: Yeah. Boom. Okay. Great. So it gets the metadata and it says like, okay, if it finds that same existing information, let me just make sure I've got this  

Taylor: mapping over. Perfect.  

Aron: Boom. Well, so we're going to be done with our example. I do want to do MailChimp after, but I don't think we'll have time. Uh, we only got about 10 minutes left.

So folks, if you have a question for Taylor, I do see one question for Colleen. We're going to have a bunch of time for Q a. Uh, so, you know, go ham in the chat. If you do have questions about present or future, uh, transfer, but let me just go ahead and finish that zap with that said it looks good

or I'd love to know in the chat, like what, what are you hoping to use that. Great. I'd love some examples. If folks have like ideas already. And I would assume that my audience is like 75% paying Zapier users, so they have access to it right away. So my expectation is that they're all going to go ahead and use it right away.

Um, cool. So we're bringing in those two and then I want to select all, bring that it's going to cost me five.

Boom. And if we go over to that, these are the five that we created and now I'm really interested. So we see that it matched to the existing account. And then, yeah, we have some examples where there are two contexts. So it is, uh, that kind of, uh, ability to, if you have your database structure and you're coming from a sheet and you have linked.

Um, and I imagine that for folks who use web flow, this will also be the case, right? So if you have, um, in flow, this is like tailor way too niche for you, but, but a lot of folks work with web flow, bulk transfers. Uh, you're probably going to have to do an array of CMS IDs, uh, separated by commas. Uh, but it should understand that as a multi reference fields, The YouTube world will create a, how to bulk transfer multi reference fields into what flow soon enough.

Uh, if not, if no one can find it, I'll find someone to create that video. Um, so yeah, so that was Zapier, uh, transfers. So I'm going to do one more. I think it's another time for a little more confetti

I have to say, um, I'm particularly impressed with the elegance of this as like a starting point for transfers. And I love how you've reused a lot of the elements that folks are familiar with. So yeah, I'm really bullish on this. I think it's really exciting, um, questions from the chat,  

Taylor: and I'm glad to hear that too.

It's going to say to, you know, like you kind of point out a few times about, you know, There's a thin line to be kind of herbicide between about how to kind of, you know, leveraging existing capabilities kind of makes me feels familiar to folks, but also introduce a new capability to assist them. And so, um, you know, it's a balancing act.

I'm trying to say, I suppose. Um, so anyways, long list way of saying, appreciate the, the praise on that, um, you know, set of decisions that were made there.  

Aron: So yeah, no, I agree. I think it would have been very simple to be like, Hey, well, you know, it's transfers this new world. You know, we're now an ETL company what's up, you know, but I think for most of your users, or even for me, like, uh, you know, I see Zapier as like this, this moving of information, right.

And this actually fits really nicely into that. And I could see it's like a really good starting point for potentially finding that. Area that Zapier can really Excel it, whether that's simple ETL, right. So adding some filters and maybe adding, you know, a timer on it to say like, Hey, you know, once a week do this thing, here are the configurations that I want.

But then, you know, some tools out there we'll be like, okay, yeah, we're full blown ETL, but it's really complicated to use. And so I think you've kind of really nicely thought about who uses. How can they use it simply and how can build on top of it? Uh, and, uh, you know, for, for more experienced, no coders, I'm sure it's, it's like a really cool thing to have in their back pocket as well.

Taylor: That's awesome here.  

Aron: Yeah. Okay.  

So one question from Colleen, which again, speaks to the types of folks who watch "Automate All the Things", um, is can, uh, let me just find it here. Can one use transfer would zap your storage. So move the data into Zapier storage and then potentially move it to somewhere else to be used in Zapier.

So when I said that folks are going to have innovative ways of using, uh, zap here. This is, I think, falls under that category.

Taylor: It definitely does because I don't know. the designation. You can have a shot. Yeah. A hundred percent. This, this goes back to some earlier comments about, you know, uh, the best thing about one of the best things about working on at Zapier is, uh, our, our users have extremely innovative ways of stretching things that we've built in ways that we didn't think possible before.

And I have not tested, transferred, going to Zack your storage, but, um, I will. Yeah. Uh, the notion of not persisting, um, pastime transfer has come up as well. And so, you know, big kind of, it goes into the areas and stuff. We're looking at two and we're thinking about here.  

Aron: Let me move the chat. I have a good you,

I pressed on the wrong thing. Sorry about that work in Betty, Margaret Fetty, but it confetti's right, right. So you can use storage by zap here, right? So you could imagine a transfer that says, you know, go from air table or from sheets into storage. Right. So set value, um, It would be, uh, a quite, I don't see why you would do it, but I'm sure someone will prove me wrong and find a really good use case.

So I don't know, Colleen, if you had one in mind, but, uh, you can, I don't know if you, Taylor could find a good reason you, why you would use storage by Zapier as like the sync destination.  

Taylor: Uh, I've taught my head. No, but again, I can repeat myself again. Uh, there's plenty of times that I had thought in my head, like, I don't see why someone would do XYZ thing was up here and then they come up with this great use case.

I'm like, okay. That actually makes sense now. Um, so  

Aron: cool. Okay. Uh, yeah, those are the questions we got.  

So, uh, Taylor, huge. Thanks for coming on. Everyone in the chat. Huge. Thanks to Taylor. Um, you know what I hope and Taylor, uh, what, when you maybe next year get more functionality. Oh, there was a question. So Coleen menu populate the data.

So I'm not sure if that's what you're thinking of using storage for. Uh, but yeah, it seems like Coleen's already got a use case. Well, once you've built it out, send a tweet to Taylor and let us know what you've built. And when Taylor comes back, we'll showcase examples of what folks have built. So, um, yeah, Taylor really appreciate you coming on.

Really appreciate everything you've built. I hope you'll come back next year and show us off your, the amazing. You know, 10 50 features you've added next year. Uh, and folks reach out to Taylor, uh, with examples of how you're using it. I'm sure you'd be curious to see how folks are using it and get feedback.

So really appreciate, uh, Taylor. Yeah. You coming on any parting  

Taylor: words for folks in pre-K?

You know, uh, you transfer a spin and take it for a drive. Uh, and you know, to your point, Aron, feel free to reach out to me personally, with any type of rants, raves, uh, concerns and or ideas. Um, you know, we're seriously interested and all the cool and fun ways that, uh, our customers and users use transfer.

So,  

Aron: so if it's a, if it's a, uh, if it's a rant, don't say you're coming from "Automate All the Things". If it's a rave, please, you know, please let them know you watch the video and you thought it was really. Uh, cool. Well, thanks everyone. I'll be back next week for, uh, some costs remain with Elif. His we're going to do some marketing use cases and we'll probably use Zapier then as well.

So even if you're in right here at Taylor, well, you'll probably be showcased on the stream, so that's it for this week. Thanks everyone for joining Taylor. Huge. Thanks again. And I'll talk to y'all next week. I tell her thanks for coming by. Y'all.

Key takeaways

Similar streams