Using Webhooks to Transfer Data

Transcript

And we go going to next social press like so countries are actually able to move it to the next slide that work? Yeah, I am already on the speaker’s late introductions. You know, we seem to know most how point like in the remote area. No, it doesn’t go into prison mode. Okay. But we can go from this tense event, John here and be the moderator for today. So please, as we get started into the session later on, if you have any questions, answers, please add in security component which will enable and when needed. Interrupt our and Josh as we go through crickets are to me I’m a two time regular champion. Don’t create a few notifications but it’s them being the market architect working at expensive. Yeah, we worked in the space for, I think nearly 12 years now. You can give a quick intro, so. Yeah. Yeah. Thank you so much John Heilemann to start shall I work as a senior consultant at Deloitte? I started off my career with Marketo and then got five years and super passionate about Marketo marketing automation in general, and I am a two time market champion and champion of the year 2020, multiple times certified architecture expert. And I love integrating stuff, be it custom integrations, be it native integrations. I love, you know, managing thematics deck and ensuring that data flows from one system to the end of the system in a streamlined manner, be using rescue books, everything. So yeah, thank you so much for taking the time to join us in this session and I hope you’ll find the session insightful. Thank you all to you. Josh Sorry. My name is Josh Arrington. I am partner and Chief Marketing technology officer at Catterall. I’ve also been working with Marketo for 13, almost 14 years. So of course the beginning similar to our style. I love kind of the outside of the box integrations and solutions, so I work mostly on the technical side would be the webhook APIs and more recently self-service for startups. Excited to be here. So thanks Josh Thanks. Usher And just a quick agenda for today. So introductions have already done with I’m going to go through just a few quick housekeeping things for our meeting and then we’ll get on to the content that everyone is here for, which will be looking at APIs, how they’re different to webhook some of the basics about the web folks and how to set them up with configuration implications. Also important topic when we talk about how we get access, some use cases, some things coming there, the tips that Dashiell and Josh have come up with over the years of working with folks and also good to be aware of the limitations. And then at the end we’ll have a more dedicated Q&A session. But I have also enabled the Q&A now. So if you have questions as we get to the content of the presentation, please feel free to post your questions there. Quickly onto these housekeeping. And again, as you’ve been, if you’ve been to any other before. Same rule applies, but let’s try to keep the focus on the safe space. So no self-promotion in the mugs. And also, please don’t contact anyone else in attendance without their consent to that. And if someone does share a use case or something that’s a bit personal to either the company or the clients that they work with, please don’t share that further without their consent. This mug is also being recorded, so if you just let me know that it will be posted on both the page where you register for this and the YouTube channel from the market or user groups later on. If you’re not okay with being on the live recording for that, please feel free to leave the meeting now and then find the recording once it’s posted on one of those two locations. Also, if you want to stay up to date for any more artistic type, we’ve got a few more scheduled coming up at least once a month. The rest year. Please make sure that you are a member of the Adobe Deep Dive mag as well as maybe the local mag or any others that you are subscribed to that means you’ll get the notification when a new event is posted. There and just some quick other upcoming opportunities. One, there was a webinar last week, I think it was, that talked about how to become an Adobe champion. I think we all mentioned in our intro that we are very market oriented to champion this year how we got invited to present on this topic. So if you’re interested to follow in their footsteps, there was a great session presented by the program managers from Adobe on this topic last week. It tells you all about the program. What eligibility looks like, what’s involved with the minutes from your site. So you can watch that recording here as well or find it on the MAG website. In the past events, we also had a request from the adoption and Retention team. They’re looking at some user research to understand better the marketing practitioners and how you use Marketo. What’s working well, what what maybe challenges the pain points you’re facing. So two very quick ways that you can interact with that. We’ll put these up again at the end for those that want to focus on the content now. But one is just a quick survey and the other is if you’d like to have a lot more feedback you might want to share, feel free to author the other to our code and schedule an interview with the team. And very quickly looking at some of the other upcoming events that we have today. One couple is the one we’re at now, but there are a few more in North America based events happening. Mostly consider that for a time. So point of view, because I think majority of them are virtual events and you are welcome to attend any event that you are interested in. And we also have a few upcoming in outside of North America as well, including join here. Also launching the first ever Irish mug is going to happen in May. That’s quite exciting. We’re growing more and another exciting one for London, which will be hybrid. So you can join in, but it’s going to be a special one at the Masterclass. So Josh will be there over there that we think four or five of the champions as well, presenting. It’s a nice topic that’s going to be a longer session. We’re looking forward to that one. But now for what we’re looking for, for the deep dive session, I’ll hand over to Darko and Josh and we’ll start talking about how to use WebEx for data transfer context. Operator Thank you. Thank you so much. On and yeah, thank you so much again for joining and will be covering this topic and we will be exploring all about Web books and you know, why not? You know, when we are starting about WebEx, of course, we’ll be starting from the basics, will understand the use cases. And then you’ll also have some of the short tips and workarounds and some of the technical limitations as we saw in the agenda. But why not start with the like, one of the questions that I get, most of us from the users that, you know, what’s the difference between an API? So it’s, you know, probably start doing that. So basically, you know, WebEx are like they an entity or they allow you to communicate or make requests from market or engage to an external service and when you compare it to an API, call it like maybe a call is something that makes sense. So like it makes a request to market. So the direction of the call or the request that this made is kind of an important. So as you can see on the screen, it’s something that is so initiated. So so where are these know in this case market or it is something that is shifting the call to an external service. That is an EPA call you see on the screen. It is something that you know, it is initiated from the clients and from and it is made to the seller. And there are different use cases for each of them for this EPA call. But at any point in time when you differentiate between and any call, you can just imagine and like let’s identify the point and direction, the point, the direction in which the data is flowing and the way that you are calling, you know, making the call if it’s what is in a call from this server or like a system, a market system, then so that call or if it’s something that is audience these from the client end. And at this point also it is an EPA call kind of thing. So webhook allows you to integrate your services physically. So so if you want to pass any outbound data from Marketo to any of our services you would use, and I would call and it the like, it will define an API point like an end point and all of the other parameters in your verbal call. But the, the, the call that you make to that particular service would be via of Apple. So I’m sorry, kind of go into presentation mode thing is that it’s kind of small and yet you. Can now think. Of you know okay. This is going to the PowerPoint, the menu and things like that. So you just enlarge like going to presentation mode. It would be. A I can just I’ll try to present from my Yeah. I’ll, I’ll stop saying be. And I’ll just add they are separate web books and APIs, but they can be used together as well. So you can trigger a webhook that then calls a service that uses the API to take another action within Marketo so they can be used in conjunction to Oh, that’s much better. Yeah, great. Yeah. Thanks, John. So, yeah, I’ll, I’ll continue that. But I think to Josh for adding that and one more distinction is that deep ebooks are kind of a stateless entity. So when I say stateless, I mean that data is not presort from one call to another call Any data that is being used in a single call and the data that is returned as a response and that particular robocall remains in its entirety for that particular call. It can of course, be transitioned to and carried over to different biblical, but for that you would need to have some different configuration. It’s stateless compared to an API call. The the lexicon. You can have stateful as architecture. It’s a possibility. You can carry over the response that you got from an API call to a different or a subsequent DPA call. And there are workarounds when you know in when you can bring in the stimulus in the verbal calls. But there are certain workarounds and we’ll be discussing those towards the end. And one when another parameter is that like the verbal call it requires of a compatible service, the service that is listening for that call from a started, right, a system that is a marketing kind of system, you need to have that already in place. And another distinction is that the kind of, you know, the kind of activities that you can do from one end to be another. So that allows you to transfer or not have certain services performed by a third party services. Whereas for an API call you can post updates, you can create an asset. For example, using the market process, you can post delete, update, create, delete, etc. So those are some of the distinctions between verbal call and EPA call. And I am pretty sure that this distinction will get clearer when we discuss more in depth about webhook and yeah, in the subsequent slides. Yeah. So, you know, let’s, let’s start with some of the very basic slides. Like what, what is level. So when we discuss about where like was the word public, it’s composed of like words, so it allows you to create it’s a method through which you can, you know, hop multiple services together, you can integrate, you can connect the website. It was just to get. So for example, are you have you ordered will be Marketo to instance you have another third party service that is performing something like calculation manipulation of the data that is in your Adobe Marketo engage. So if you want that service to like, if you want to integrate these two platforms, you would make a call and output from Marketo. So that’s what the basic idea about that is. So the, the, the core requirement of the public is that the service must be a web compatible since it’s a web based service, it could be on the stupidest ops protocol. And so and of course, as I said, it allows you to integrate your order to remarkable engagement. As a matter of fact, any other platform but your third party external services, it allows it opens a wide array of possibilities, for example, data transformation or cross cross application communication and even advanced calculations which are not possible natively within Marketo. Engage. For example, until recently you were not able to like at course, like you can do so by a webhook and there are certain, you know, services, Facebook services and platforms that allow you to quickly create like using the basic JavaScript based code you can use that can perform those external services using that. So it is inclusive, of course, and any other sophisticated data processing that is, you know, needed by your use cases that you are not able to do natively within Marketo. You can do so by facilitating those via the third party services and you can call those third party web services and be calling your marketing page. Yeah. So, you know, like the first question is like how to use a web market. So in order to use the web market, we would want to go to the admin section. Then under the integration tab, you would want to select people. And if you are creating a new web, you would want to select the new web book options. And when you select the new web option, there are certain configuration items and a new dialog box that opens up that that isn’t the next slide. Can you move to the next slide? Yeah. Thank you. So, you know, this is the dialog box that you will see when you like. When you create a new bevel. You would be, of course, asked to enter a book name. So any, any name that loosely resonates with the service or with the kind of look that of those who can mimic. And of course that’s an there’s an optional description and then there’s a new order. And so this you all would be the point like it will be and point it will be pointing to the service third party service tool that you want to make a call from this particular rebel called flow step. And of course, in the subsequent slides you will see that you will recall the little step in the campaign. But apart from you are you would need to also add the payload. This is like if we want to send any outbound data to Marketo with this particular to this particular type of call. With this particular call, you are going to be adding that particular body parameters in the payload and then you have the request type. Up until recently, there were a couple of request types that you can that you would allow, that you can like build it on the web. But then Marketo recently, not very recently, but yeah, like a couple of years back they also had a select few more service types like request type. So you can now to delete, skip and post operations using purple calls. Then of course the encoding type. If you if you make requesting any Jason like symbol and quoting type, you’re going to be selecting that. And then the response mappings. So these are the things that you will see a little bit in detail in the later slides. But at a web call when you make a call and outbound call from Marketo, that service at some point in time will return certain response parameters. And if you want, you can map those or use those data that is written by the service maps, those to have like fields on the person record and those data get saved on the personal record. So you can do that in the response mapping. And there are also that optional custom you can configure with the web. For sending data in a as structured mentioned for simple requests, you can use, choose a get requests, and then just pass the parameters in the URL of the red book. In this case, you can use hardcoded values or you can use tokens when you have more data. And it probably makes more sense to use post or one of the other services available. Typically get in post are going to be your your number one things to use. In this case you can use JSON or extend. Both are accepted. Actually I you can pull whatever you want, but those are the typical ones. They’re in this case you can use all the tokens you would in for lead. So you can use all the records we fields. You can also use program fields, program member fields and program tokens. So the question is where which program are they going to come from? Whatever ever the program the webhook is triggered from, it’s going to pull the tokens from there and you have trigger system tokens available to you as well. So there’s a lot of data that you can pass out of there. And it also gives you the ability to make these very flexible. So say you wanted to send a out to a webinar service or some sort of event service and tell it which event someone’s registering for instead of having to create multiple web hooks for each event. Obviously there would be too much. You can just pass that as a token from the program or from the program member field. It’s things like that. And then next obviously is once you send it out, how do you get the data back? And that’s where field mapping or response mapping comes here. You can support Jason on our though there’s no limit on the number of field mappings that you can set up. So even if you have a very complex and a large amount of data coming back, you can map all of those. The properties are mapped with the dot notation and array notation. So even if you have nested values and JSON or X amount, you can get to them. Here you can see in the highlighted one an orange here name, dot last name. So if you had a name object and underneath that you had last name you could get to that with name, got last name and then to get to an array, a few other names, for example, you can use array notation, which is just your brackets, square brackets with the number of the item below to you can map to beat fields and also to program number fields. And this updates will only happen if the web service returns a 200 response code and we’ll get to that in the presentation. How to detect errors in their response, how to avoid them, and how to make sure you run smoothly. Yeah, thanks, Josh. I can talk a bit about the authentication with the books. So basically so so let me start with the very basics of a new I’m making a call to a third party web service. You would want to ensure that not everyone out there can actually make a call, as we call web service either way. So we didn’t get bombarded with a lot of requests. So you would want some sort of authentication, be very simple, like an API based like a very simple token based authentication to a very sophisticated or 2.0 authentication. But you would want some kind of authentication. You would not want to, you know, keep your cut party web service. I’d like the endpoint open, basically. So like there are certain, you know, authentication that you can use with books. The first one is the API based authentication. So it’s this is one of the pretty like one of the basic authentication where you have a static kind of an API based key that you added to your web calls. And this key is used for authenticating your calls to the third party web service. You would like quote, Like a lot of times you would like card quotas in Marketo. But since it’s just like these are like unless the unlike the access token that are like short lived in the or two point or authentication, these are not like dynamic and at the same point this is convenient, but they themselves can be vulnerable if compromised. And then there’s another authentication type that is the basic authentication. So and unlike the API based authentication in which you had a single like a string, the basic authentication has a combination of a username and password and you send details like these to parameters in the request headers and these are encoded in the base 64. So this is like a little bit more secure and a little bit more in all. Like it’s better than the API. Very simple authentication. However, it still has its own vulnerabilities since this is not dynamic. And instead next up is the over two point or authentication. So this is the default like authentication that Marketo is rest APIs used. So people who would have used marketers rest APIs, they would know that Marketo uses the or Proofpoint tool based authentication. Then you have your client data line secret of an API use that you use that to generate a Nexus token that is shortly before 60 Minutes and using that access token you authentic get your request to Marketo. So that is a gold standard, kind of like a pretty good authentication mechanism. So you can also have your third party web services use the or Proofpoint authentication, which says that alert. If you remember when I said that all of the books are like, they’re stateless entities, So the data that is that they respond to comes in verbal call one, you might have to do a second configuration so that you can reference that data nearby. Your call. So what that means is you can have a thing like the first call you can make to get the access token, and then you would need to see if that exists in your field and or any other field basically, and use that access token as an input for authenticating a second access token. So this is a bit like, of course, it allows you to have your calls very much secure. At the same time, when you when it comes to implementation, you would need a little bit of more setup campaigning wise to use this. And then there’s custom headers so you can add in certain headers that has the secret strings or tokens for verification. And of course this approach offers flexibility, but your first proper management of the secret is when. Yeah, so let’s talk about you can you know how you can use red book in the market or smart campaign so you can only use it like buy books call your books from trigger campaigns floor. As of now, trigger bad campaigns do not support DBA call and then there is a of a workaround that will do that we’ll be discussing in towards the end through which you can also call like making a call from a campaign and nothing but yeah. So yeah, like I also already mentioned that you can use the request campaign flow step from a batch campaign floor to colorable to call from a batch campaign or daisy chain, if you will. But in our later slides we also have a short list with a snapshot putting more to the next. Yeah, I let just talk about some of the use cases where, you know, you can use WebEx. For or so. Do you have a nonstandard CRM integration or if you have multiple CRM now you can only connect natively one CRM, a salesforce or dynamics. So if you have something like that, it’s it’s a very good tool for web looks when something changes in Marketo to reach out to the Sera so you can create a red book that goes to your service with all, all of the relevant data. Any Do you want to sync from the lead records to that service? It can also pull that which are a CRM or external service that you want CBP and then compare those records, merge and so they can also not only update the CRM, but also pass back any updates that CRM has for that record. You can do this bidirectional that way, or you could have any webhook that simply pulls the CRM and brings back any updates or doesn’t need to be CRM or whatever service pulls it and pulls back any the updates or I just push one. So just purchase updates for whatever requirement you have for the external system. You can build it that way. Next, we have event management. If you need to register people in a third party service, you can send out that they registered through your Marketo form or through your Marketo program. Send out that that registration has happened or vice versa. If you need to check within a third party system, if that person attended event, you can reach out and pull that event in e commerce. If you have an external ecommerce system, you need to pull in whatever product someone is interested in or has bought in the past. You can do that as a pull or need push. Maybe you need to push a product. I think your sales would happen in the ecommerce system, but occasionally there’s things where someone has shown an interest or something like that or initiated a refund or something where you could push it out to your e-commerce system and then cloud storage. If you have data that you don’t want to keep in Marketo or you want replicated or anything like that in a cloud storage system, same thing. You could set up a webhook where you set up that that payload where you have all the data that you need to store in your cloud storage and go ahead and pushed out through a webhook through that efficiently. One question again is the assertion mentioned that these APIs and workbooks are separate. Sometimes I get the question, Well, if we get data back from the workshop, does that count as an API call? We only have so many API calls. No, none of it can make that call unless you use the actual API content. So some more use cases are around marketing or lead generation. You can trigger marketing programs based on these actions. So whatever you need to push out. I’ve seen this for like PPC campaigns, things like that, where you need to promotions or you need to trigger something in another system to tell it. Someone took an action. You can go ahead and do that. Sales enablement. You can send sales alerts registered for semesters, things like that directly to our sales team, give them live updates about activities that are happening close to reporting. So oftentimes if you have a reporting system, especially if you have a live reporting system, getting that data back and getting it into that system as quickly as possible is very important. And then personalization, there are many ways to do this. We have print on demand, SMS, how many different ways of you have another system where you need to get at the specific data from the read record or the program member fields. You can set up a webhook and call it like. Yeah, thanks Josh, for covering the use cases. Now we have in us like a bunch of pro tips and some of the workarounds and as a result of the technical limitation of the event books that we would try to cover. So the first initiative that I personally have encountered while writing my usage of that books when I started with Marketo is like menu of data workbook, like when you already have a book and when you are like making updates to it. Once it’s created, then like those updates do not get reflected. So for example, you had a web copy, then you made something like used it in your campaign, you made a call, you were like it, written some data. And then if you want to make an update or like you were just testing, and then if you want to make an update, that update will get reflected still marketable even after saving the updated sample definition market would still call it make and call with the non still or the previous level, like the definition and the configuration. So you know, the like I hit talked to PMS and the one reason that I got from domestic Marketo, I know cache is the web definition, so it usually takes some time for web like definition for the cache to create out. But there are certain like I have seen use cases where that cache didn’t get cleared even after like two or three days when if I call the updated like the call I Marketo is making the same like with the stale book definition call. So usually what I recommend and what I do is like instead of, you know, making an update to the existing book, I launched an updated and then, you know, use it in my campaign that way. It allows me to also like do some portion control because this five they can get pretty complex complicated with like the second payloads. And of course if you are using some of the web calls we had you where you are using JavaScript as a language tool to execute certain commands in the payload, then you can also do version controlling and allows you to, you know, roll back or refer to an earlier version of the webhook pretty easily. So yeah, so if you want to update in web apps I like, I usually prefer cloning and then making an update instead of making an update to the existing repo because that you can risk, you know, where market is calling the stale web configuration. Yeah. So this is something that we covered earlier, like we touched upon when we when we were discussing about, you know, calling from the campaign so natively market only supports calling Rebecca Pebble from the trigger campaign. But if you want to make a call from the batch campaign, you can do so by having a request campaign to step in your patch campaign and then having Eric WESTERVELT campaign that is a campaign with campaign is requested trigger and it’s smart list. And of course, you can have something interesting to want in the campaign smart list and the that campaigns flow. You can make a call to the red book. So technically we are calling of from a trigger campaign. It’s just that that campaign is being requested from a patch campaign. So it’s a daisy chain kind of mechanism that you see there. But natively, if you call that book from a patch campaign, you will get an 1000 response for back and that call won’t be successful. So I guess in this case, the intention is that you may overload the web so it’s it’s not something you’d want to do for big bulk of audience and your destination person, what it can handle before you take this approach. Yep. I see a question in the Q&A and it says How can we replace my books with So those steps as well. Books have some limitations. This would be where you would do that because self-service close tabs send the requests in batches of up to 1000. So it’s asynchronous, so it doesn’t have a timeout limits. But this would be a specific area. Like if you’re already doing this and you have access to a deb team or tool where you can build self service or steps, I would push you in that direction, but it is possible if you are careful to do it this way. So they’re handling, as I mentioned, you want to make sure you’re getting 200 back. 200 is just an all good status. So what you can do is there is a filter. Once you start using the workbooks, there’s also a filter and a trigger. Here. You can use a trigger workbook is called and here you get the responses which you get the response. And if there’s an error, the error type, and here you can just filter out, see the errors you’re getting. If you’re getting an error, maybe what you’re going to alert to you or you want to trigger something to run again, this is how you set your trigger. You can run it as a trigger as it’s shown this way or as a filter that you run maybe daily or something like that. I also want to add one thing here. So, you know, in one of our earlier slides that I discussed, the authentication method, say just about the or two point authentication method where like you would want to make a configuration where you want to preserve the state, basically get the access token from the call one, call one and use it in the call. So this is something that you can just like in a regular trigger, you can say like that is called like the first Redbook is called and you get a 200 response. And then in this particular campaigns floor, you can make outbound call to like your subsequent verbal call. And since this particular trigger will only fire when the first 12 is successfully call and you already have the access token written like, like written from the system, and then you can use the Xs token to make the automatic request to the next DC service using like the access token basically. So that’s how basically you can not introduce or bring about these people less in the state, like using the statelessness nature of the weapons. So continue with their handling, handling predictable errors, set up decisions and processes to handle the buyers. As I mentioned and exceptions, you can use parameters to identify specific error messages that you want to set specific actions depending on what kind of error you receive. Maybe once in alert, but once a retry, you can go ahead and set them that way. Automate or recovery. Sometimes you’re able to, depending on the external service servicer using and you’re integrating with some errors can automatically recover from. So if it’s throttled or something because you’re sending too many requests if you did an A batch campaign. So it’s possible to just schedule retry. So schedule wait step or wait till later and schedule those again. And then, as I mentioned, set up alerts for unexpected errors. Anything that you can’t retry or fix. And then also you as the admin or whoever is responsible for that, gets the alert and knows it comes up. So you go in there and figure it out and make it work and then an investigation list as far as the as part of the error handling mechanism, you want to include the people who are responsible. Designated investigation lists, and that will be, you know, who’s responsible for specific actions, for specific items so they can go in there and take care of those items. And clearly mapping out all of your web hooks and backend services helps to do that. So as Tushar mentions, calling output is only valid and trigger campaigns, even though there is a workarounds, I don’t advise that’s I’ve seen some messy things. Some servers go down and then trying to figure out, okay, when which records did work, which ones and it can be messy in those cases. I would suggest self service those steps. Maybe some other solution where you’re running it in triggers, it’s one at a time execution. So web hooks are always called one at a time and they have a 30 seconds limit. So if your server doesn’t respond in 30 seconds, if you can do the action that quickly, you’re going to get a timeout or you’re going to lose data. So you may there may be a case where you are expecting a response back. And even though you started the process on the server, if it doesn’t get a response on spec to 30 seconds, it can take the ACT action. But Marketo never from Marketo reports it as an error, a timeout, but it actually happened on the other end. So I’m you have two systems that can be out of sync depending on what service you’ve set up. And so sorry I skipped over one at time execution means no because you’re doing one record at a time. Some, some of you, I’m sure, have some massive databases and made millions. If you are running even 100,000 records through something and it’s running one at a time, that it can balloon up, time that it’s taking to run, that that can slow down your system. Definitely crap pressure back. And so just be aware of that and maybe find other alternatives or be a little more strategic about how you employ workbooks if that’s going to be the case for fun. Q&A Great. Yeah. So that was it for the main theory of the book. And I put a question in just the normal that if anyone has used cases that they’re using workbooks, I think I’d be interested to hear how the community is doing it. But looking at the Q&A there was one question which was about self-service flow steps compared to webhook. I don’t know if you have any more points to cover on that. I would say. Or helping decide when to use, which is the right thing, the right approach. In most cases. WebEx, the what they’re going to give you is simplicity. You can connect to something like Zapier, to Microsoft Power, automate to Macomb or I think work out of that can be quickly set up. You don’t need a back end server, really just need it can be really quickly setup whereas self-service process they’re a little more involved to the setup, but they’re a little more durable. They run in bulk, they are a lot more reliable as far as you know, you don’t have any timeouts if it’s designed correctly. So there I have an article in the community which goes through all of the limitations and where self-service systems would be your best option. But in general, where, where I which is web hooks is simplicity. If I have something right now, I can just make one call and be done. My server is not going to take a long time to respond. I don’t need a response back. These are where I would just grab hooks and if you have access to a developer, you can use the template that Adobe has put out for Adobe IO. You can build it on any cloud service. I recommend using a serverless architecture. So like Microsoft Azure functions, Adobe IO, something like that. The one kind of code, this platform that I know has a specific self-service flow step option is Ricardo. There may be others, but that’s the only one that I’m aware. I think that maybe goes on to the next question, which was from April about when at what would be use case where you wouldn’t able to use a webhook, but would it be prepared to use a middleware like Zapier over a counter? I think that touches on maybe just about webhook Press API. But just to clarify, Zapier or work out could be used with a webhook that could be the service that you’re calling. But where to kind of put it in the self-service when you couldn’t use a webhook? If the response is going to take the reserve, the response is going to take more than 30 seconds. Absolutely not. So if you need to call OPENAI or an AI service and get a response back, it’s probably going to take more than 30 seconds. We’re not going to get in time. Or if you need to do things in bulk where you have hundreds of thousands of records that need to be processed. Those are the two that I see. Most of them are just too much for WebEx. Yeah, and those are great points. And to add on to that, you know, certain times like I feel that the middle man, if you look at what they kind of sat in on, helped simplifying integrating multiple platforms. So if we want to like compare that with a webhook so we would not have the ability to make an API call to a certain service, to a certain platform right there. And then from Marketo, like for example, that particular platform doesn’t have an accessible public key, like publicly accessible pain point for you to call from the Web, from Marketo. In that case. But however, if they have an API as an integration with that particular service or platform, in that case, you would not be able to use that. You would want to call that the middleware likes to appear on Google. So yeah, kind of adding on to that, anything like authentication wise. Yep. So you gave an example of how to use a lot, but a lot of cases you wouldn’t want to put your key is in there and it’s a little cumbersome to build. You can, but I would probably just put that into a third party and you can do that with a web still, but put it in the service or if you need to toggle into something like a VPN or something into a service, but you can’t authenticate directly through a book. Yeah. Yeah, I think it was. I remember a lot of people talking about it a while ago, and I was always noticed that they were using web books for the company to use Slack as well. So you’d get that and there was a certain failure, or maybe there was a lead that came in with data that didn’t fit the expected values from maybe country code or something. I found a way of doing some Googling three teams, everything like as a team. So I created a webhook that will send me a teams alert to a channel every time that there is a failure on a different hook that I have. So I have web hooks trading off webhook strategies for certain things, so it seems to work quite well. But I had it previously set to an alert and then it was just my inbox that got flooded or it was all on me to maintain. So that was the way that they made it. So the responsibility across the team that way. And yeah, I think other ways that I’ve used it in the past were also replicating a similar idea to interest moments, but storing them externally or using a webhook to post that through like a streaming endpoint. Or we can send off the data after we generate it based on like an example from earlier. If there was an event attendance or some form of content, download also making that thing available to CRM. So there’s a bit more of that marketing history available and, and something I’ve been looking at lately is the idea of not having everything in-market. And in cases where we have multiple systems of record calling a particular value like account manager at that time that may be in a commerce or a native tool or in CRM or those types of things, and calling real time depending on what value we need, rather than maintaining both regular. I think. Yeah, I think that comes to the end of the questions that we had in the Q&A. I do not see any. I got quiet today. Yeah, so that was great. Here we go to questions coming in from Mike. So let’s just have a quick look. The first one, he says, is when you use a web property to enrich a new person record such as pulling info from Zoom. So if people are added to the database in bulk from an important server to say over a thousand people, for example, what are the best ways to throttle the course? And you don’t overload the zoom info end? Oh, that’s a good question, Darshana. I guess I would definitely jump to a self-service one step for that one. Yeah. That’s what I was thinking. Yeah. Yeah, definitely jump to self-service for those steps that you can like better get more control then, because if you have a trigger campaign that is just calling like making it publicly available, that then, you know, makes the call to a zoom in for you would definitely yeah yeah. Flood your system basically with a lot of levels like WebEx also yeah I honestly would move to instead of this four steps if you are seeing you know a lot of similar incidents where you like you are importing records in bulk and then your system is getting slowed down or down, you would want to move to the sense that this rule steps in. So I would I would call that trout. Yeah. You know, instead of optimizing that particular trigger campaign, 4000 or 2000 or even 5000 recording faults, I would probably go to the self-service flow steps where my system would be at a better point and be able to handle larger list imports, because that’s that’s the point. But I would go. And I guess you could do like, hey, first of all, you could do the error handling where you kind of add people to a wait step where they get retried and things like that. You could do the the random sample and just whittle it down until with a smaller number and then process them all would be complex I think. Yeah. To single thinking random sample too. And it would be good for maybe one time when you have a thousand records and you break them to 300. But then if the next time it’s 10,000, but you have 3000, it’s not that at a super scalable rate. Did you have a second question? Might else if there’s no more questions, that we’re also almost that tight so we can collect again. So we’re always at time. So I will just quickly move this. As I mentioned earlier in the intro, the adoption and retention team have, if you would like your feedback and input on things. So if you want to have time to take a quick survey, please send it to our card on the left and show about him else. If you want to have a more in-depth chat, get some good feedback. Scan the QR code on the right and apart from that we are done for the day. Lots of nice compliments coming in. So thanks for sharing your knowledge. Thanks so much so far. Thank you. I have a group, just a few days. Thank you. Bye.