[Music] hi everyone welcome to glad fast on air i'm colleen kelly marketing specialist at glide fast consulting and i'll be moderating today's webinar servicenow integration hub is the investment worth it for my organization before we get started we'd like to give you some information on glidefast glidefast consulting is a consulting firm dedicated exclusively to servicenow as an elite servicenow partner our expert team of developers and architects have worked on both sides of the table the customer side and the consulting side our company was founded by servicenow architects and we're proud to have a team of over 100 experienced consultants an average csat score of 4.8 out of 5 and more accolades as you can see here throughout the webinar series we're sharing our goal of raising fifty thousand dollars for the joe andrews foundation this foundation provides financial assistance to families battling cancer and the unexpected costs that come with treatment as a cancer survivor himself glidefast ceo mike lombardo has committed to matching up to 25k and glidecast consulting as a company will also match up to 25k for a total donation of 100 000 to help pediatric and adult cancer patients if you or your company would like to contribute to helping us reach our goal we'll send you a link with more information following the webinar with that said i'm excited to hand things over to our presenters chris sanford senior technical consultant and matt dumont service delivery manager please send in any questions as they arise and we'll do our best to answer them at the end of the presentation chris and matt you can take it from here thank you colleen um so hi everyone um let me start out by just outlining uh some of the topics that we'd like to discuss today that will hopefully help you to arrive at your own decision as to whether an investment huh an investment in integration hub is worth it for your organization so what is integration hub we want to start with the basics as if you don't already have a subscription to integration hub you may not have heard of it or know exactly what it is uh we also want to talk about some of the alternatives to integration hub because there are several other methods of handling integration data in the platform many of these have existed long before integration hub existed and many of them are still in use today by either legacy applications or even maybe some newly built custom functionality for customers that don't have an integration hub subscription uh we also want to talk about some of the benefits of integration hub so given that these alternatives exist and many of them do not require any subscription why would you want to use integration hub and then we also are going to go into talking about and demonstrating some of the technical capabilities of integration hub so we want to talk about the javascript apis because these are important to know as they can significantly extend the possibilities of how your integration hub spokes can be triggered um we also want to give a quick demo of uh seeing integration hub in action and seeing uh what it's actually capable of doing and then finally we want to talk about some of the new features that were added in the quebec release and then what significance they may have so what is integration hub integration hub is an application that's built on the flow designer engine and it really feels like a natural extension of it uh if you're at all familiar with flow designer then you know that actions are the primary building blocks of flows and if you've worked extensively with flow designer then you know that within actions you'll have what's called steps which are the black box components that you can use to achieve uh common business requirements with low or no code so integration hub really introduces and extends the flow designer in several key ways one of them is going to be introducing new steps for a lot of the common things that you need to do with integrations like rest and soap that that can be facilitated with these black box uh low or no code methods uh you also have uh steps for other protocols like sftp or ssh or powershell that you can do within a flow designer flow with low or no code you also have steps for things that can be helpful for integrations but also you might have use for them in other areas of the platform like for example parsing parsing out json uh you're going to use that a lot for receiving the payload from a rest integration but you might actually have a need to do that using json somewhere out somewhere else on the platform because json is pretty uh universally used all over the servicenow platform another way that integration hub complements and extends flow designer is with new input and output variable types you have uh what's like what's called dynamic objects so without integration hub and flow designer then you have to actually build out the the structure and hard code it for any of your object input and output variables so with integration hub you don't have to do that and you can make it more dynamic and then finally with integration hub you have spokes which are basically collections of flows subflows and actions and and also possibly data streams the the four big components of flow designer you'll have groups of them they're they're typically grouped by what system they're designed to integrate with and uh some of them come with directly with the integration hub subscription so you get them in the system as soon as you install an activate integration hub and some of them have to be installed from the store or individually as well but uh one thing that generally all of them have in common is that they're very quick to set up and many times all you have to do is fill out a form with connection data and then you're good to go with uh activating your integration so i also wanted to talk about some of the alternatives to integration hub and what some of them can do and what they are so the first big one that you'll hear about or that you may have seen if you've worked in servicenow for a long time is system web services and these are the traditional way of invoking outbound web services whether it's through rest or soap from the servicenow platform and you could set these up by just filling out a form in system web services if you're an admin uh with the necessary connection information including like the endpoints and any of the query parameters and the authorization information and uh if applicable the request headers and the request body as well and uh those are nice they can also be one of the nice things about them is you can parameterize them with variable substitutions so you don't have to actually hard code all of those parameters into the form you can make them more dynamic and then once you've created them in the system web services table you can access them in a script using the javascript apis either rest message v2 or soap message v2 if you were using soap and you can set any of those parameters that you defined in the script so you you can get variables in a script anywhere that's using a script whether it's a business or business rule or workflow or ui action and you can get data and pass it in to the web service that way and then the response body could be it could be either downloaded as an attachment or it could be returned as a string variable that could then be parsed using javascript so so obviously with that with these resin soap messages there's a lot of overlap here with what integration hub can do but i think the important takeaway is that integrations that you set up with system web services are likely to require a lot of scripting to properly parse the data and also handle more advanced things like pagination um another one that you may have seen uh if you've worked in servicenow for a long time is orchestration so orchestration for a while was kind of uh to the traditional workflow engine what integration hub is to flow designer so it introduced what was called content pack libraries and they would include these low code integration blocks that were packaged into workflow activities which are similar to flow designer actions uh they were kind of the building blocks of workflows and and still are today uh and generally the orchestration content packs they weren't nearly as extensive as far as the number of systems that are available to integrate with is what you'll see in integration hub but prior to integration hub this was by far the easiest way to facilitate things like power shell or ssh integrations through a mid server um without doing that um i wouldn't say it was impossible but it would require a really heavy level of scripting on the servicenow side in addition to the shell scripting you would have to do for the respective power shell or ssh um now with integration hub a lot of that i think has really become mostly obsolete when you have those uh those steps uh built into the flow designer now for for powershell ssh as well as uh a few other protocols that have also been introduced over the years um and and i i also think so so even if you prefer the uh traditional workflows to flow designer which i know a lot of people do i would still recommend using scripts and apis within the workflow to invoke your integrations whether that's through system web services or integration hub i would still recommend doing that over the the orchestration which i think is really slowly going to become more and more uh deprecated for integrating with external sources um well chris i'll just add to that that in newer instances orchestration is not even available anymore so they are at least the orchestration piece of workflow is something that they're working towards completely deprecating got it got it yeah so so yeah that that pretty much confirms it that it kind of in a lot of ways already has been deprecated and um uh but it's possible it might still be there if you're on an older customer but definitely not something that servicenow intends to continue building future developments with um so finally another integration hub alternative or another method of integrations that exists in servicenow is uh scripted web services uh so these were these were and really still are in a lot of ways the primary way to facilitate inbound integrations into servicenow from external web hooks especially when like the out of the box api endpoints can't achieve the desired functionality that you want so scripted web services are very flexible so you can build a script to manipulate the data that gets received by a web hook and do anything that you need with it in the platform that you could achieve through a javascript api you the most common use case is going to be updating the database but um then you could also do things like make a decision in what's called decision tables uh which is a more recently introduced piece of functionality uh you you could also trigger a workflow or flow designer just to name a few other things really anything that you could do with a javascript api you could do in a scripted rest api or a scripted soap api if you were so inclined um and the scripted web services are still uh very relevant i think for a lot of applications today uh including even out of the box ones i think you're you're gonna see a lot of scripted web services just because they're they're so flexible for handling inbound integrations this may change in the future as they did just release the ability to trigger uh flow designer flows from rest but for right now it's still very a very common method for for triggering a lot of things and like i said you could trigger flows through it so even before you could directly make that a trigger in your flow you could just create a system web service and invoke the api to trigger the flow uh and that's still necessary for things like uh if you have uh attachments in your payload in fact that was actually something that we ran into when we were trying to set up the the demo that you'll see later in this webinar okay so i also wanted to talk about um you know like uh what are the benefits of integration hub so given that those other alternatives exist you know like what are you really gonna get out of uh subscription to integration hub so i think the biggest thing is that you have out of the box uh spokes uh you know so that's that's gonna be a collection like i said of those flow subflows and actions and data streams and they're all built out of the box so you're not going to have to build extensive code to set up your integrations and manipulate the data they also have access to the uh the latest apis that are available in a lot of cases so so that means um uh you know apis are constantly being updated by vendors uh you know like like i know microsoft does that pretty heavily and mo just about every vendor is constantly updating their their apis and with integration hub you're automatically going to have those updated and you might even get access to uh like beta apis or things that are not even fully documented yet that servicenow might have some inside information on and being able to uh get that functionality working early and so you can see early access to do things that you might not otherwise know how to do uh or that it might seem isn't possible by looking at the documentation for uh for the vendors api uh so i think that the out of the box integrations is really that's a huge benefit and pretty much all of the new developments for out of the box integrations are all going through uh integration hub you also have some of the technical limitations that you saw in some of the alternatives that you can get past with integration hub one of the big ones is like the 10 megabyte limit on what you could store in a string in javascript so that that was really limiting when you had those larger payloads and there were ways around it but they were typically very convoluted and involved a lot of heavy lifting on the development side and might be difficult to maintain so with uh integration hub you have what's called data streams which are a specific type of action designed to handle pagination of larger payloads and to provide an easy way to cycle through them in javascript without having to store a huge chunk of data into into memory as a single variable um you you also have uh like pre-built look-up tables for handling things like uh what's called delta links uh i've seen those uh specifically actually in some of the uh azure integration so what what a delta link is is it will actually every time a particular resource accesses that api it will the the system will keep track of it and it will return in the response a link to be used the next time that same system is accessing that same api so that way it will keep track of what data was returned the last time and then it will only send data that's been updated or changed since the last time it was updated so like if you need to check uh group membership of uh like office 365 groups then you don't have to parse through the entire payload of all group memberships every time the api is accessed it will just automatically do those delta links return only the data that was changed since the last time you looked at it and then finally uh integration hub is low code which means there's less maintenance and so it's not completely codeless and you'll find when you're building actions with steps using integration hub that there's still a lot of places for you to put in scripts uh with manipulating data and getting inputs and outputs but i think you'll also find when you're using integration hub when you do have to do scripting it tends to be a lot more focused on achieving the particular goal that that one chunk of the step is meant for so you're gonna that means you're gonna have smaller pieces of code that are designed to achieve something quickly rather than having to build an entire you know script include with hundreds of lines of code to go through the whole process from beginning to end so with less code it's easier to maintain in a lot of cases all right so i'll hand it over to matt now to talk about uh some of the uh technical capabilities of integration hub thanks chris um i apologize in advance for my voice i'm just getting over a cold um okay so for what what chris talked about was uh sort of bite-sized code pieces uh that you can use throughout your flow i also kind of mentioned that you wouldn't necessarily look at this as a direct replacement for workflow but more look at it as a series of like plug-and-play code pieces that can be used all throughout the system and to that point there's a pretty pretty good list of integration hub and really flow designer apis that can be utilized throughout the system to trigger those flows and there's a lot of opportunity for handoff between flow and workflow editor you can trigger workflows from a workflow from a flow designer flow you can actually trigger flow designer flows from any of the normal scripting types like business rules and from other flows from anywhere in the system and then you can also using the scripted rest api interfaces you can trigger these flows from external sources which we're going to demonstrate in a little bit but that flexibility with the apis it kind of existed before with workflow editor but they're really they're really serving different purposes and that um flow designer gives you a much easier way to package up pieces of your code and then with when you add in the fact that there's all of the uh the pre-built uh spokes that you can integrate into those flows it makes it easier to just pick and choose what steps you want to apply and i'll also demonstrate a little bit of that in the demo portion so these are just a couple examples very simple ones there's a lot of different things you can do with the apis we i was going to demonstrate very quickly or at least show what a data stream uh flow activity will look like but that's one of the newer features i think as of new york within uh flow designer you can create activities that they refer to them as data streams and they're basically what uh chris was talking about they help handle large amounts of data from an endpoint so they're pre-built in such a way that you can set up your your uh rest call or soap call or whatever integration you want pull back the data and then automatically build in pagination and and account for different ways of paginating through data so this always goes back to that idea of it's not that you can't do these things through script and in fact servicenow still you know has ways for you to do that um but having come from a background of development developing custom apis uh a lot of you are probably familiar with that ongoing problem of every time a new integration has to be built you're going to have to look through all the standards for that integration you have to find the right api endpoints a lot of times the the customer or the team that owns the the uh product that you're trying to integrate with doesn't really know anything about the api set so they don't have a lot of documentation there's a lot of things you have to dig through for each integration and and what this does is it gives you the opportunity if you don't have a team of developers dedicated to this to uh take advantage of someone having done that work for you up front and then to very easily plug and play a lot of times these these activities and so for the data stream that that that is something that is has been expanded on over time because uh flow designer didn't really have a great way to support that large data set and this is a constant evolution in the flow designers these new features that allow for for things that you might not been able to do before and then things like the scriptable flow runner and the flow result are just apis that allow you to trigger the flows and um to receive a result from that trigger and actually in this special object that you can um cycle through and get all the information out of it that you need uh and then real quickly we'll just go over a couple things that are in uh quebec this is just uh just a sampling of some of the items that you can see on the release notes um but i'm gonna actually demonstrate i'm not i'm not gonna actually build a flow out but i am going to show you what the uh trigger flows from rest looks like because they have now added a way that you can even build out an api endpoint from the flow directly from flow designer and trigger the flow and it's essentially just a pre-built scripted rest api but it allows for a more data-based approach to building it out instead of writing in the scripts and having to know how to structure your api endpoint uh just another another thing a little addition that helps with making some things as chris said not necessarily no code but low code so that it's a lot easier to implement at a faster rate and then there are some added integration steps there's the jdbc step type which is a pretty nice addition um again you could do that through script but it just takes that extra leg work out sftp is another one that that is a nice addition and all these things are are being added as they come up and i'm sure that a lot of this is based on feedback from developers who looked at flow designer and said well that's kind of cool but it only supports this and i need to do this and uh so that i think i want to point out that that's one thing that's sort of an added benefit of using the integration hub as opposed to other methods because it is the recommended way to do integrations for servicenow they're working very diligently to to continue to upgrade and improve that set of options that you have uh and that includes the spokes there's constantly new integration spokes coming out as long as as the technologies come out and then there's additions to the actual flow designer and integration hub packages that are constantly improving so as far as upgradeability and you know staying on the cutting edge of the technology using flow designer and at least some portion of it integration hub can help you do that without um a lot of trouble when you when you customize these integrations a lot of times you build it and then within a few months or a year the apis that you accessed or deprecated or the things that you built into it or maybe not the latest and greatest way to do it um so this is just one way to kind of help with that uh and then the the last piece that we wanted to bring up about quebec was you may not be familiar with the process flows but one of the newer features as well in flow designer is these process flows that can be integrated with the workspaces and they're they're geared more towards question answer kind of steps that you can build actual automations into but it's it can be used for a lot of different things but one of the uh primary opportunities for it is in support where you're working tickets or you have you have a team that needs to be able to follow certain steps for certain questions or actions and you can build those into flow designer so this new feature allows for process sync process flow syncing across all of your instances if you have multiple environments it can make that a lot simpler process so those are just some of the cool things that are coming out with quebec if you dig through the release notes there's several things we weren't even able to get to uh that looked like they might be pretty cool additions as well but for now let me just give you a quick demo of some of the features we talked about just to give you an idea of what a simple integration hub integration can look like all right so what we have here is i am going to run a simple python script from my desktop that is just in the same folder as an attachment and we just wanted to really show how easy it is to to start building an integration out this functionality uses mostly flow designer for this piece of the demo but there's a a lot of places you could really benefit from adding in integration hub features that i'll and i'll actually demonstrate that very briefly after we do a quick test i'm just going to run import requests and this is just a really simple file that runs a arrest sends a rest message over to an integration endpoint that we've set up on our instance and attaches this file that was in the same folder so i've generated an incident and attach that file here but that doesn't really show you a whole lot so what i'm going to do is open up this the executions list for that flow and show what we actually saw in the background when we triggered this uh file on my desktop here all this file says to do is send a rest message over to this predefined scripted rest api grab this file and send it over in a uh sorry in a binary file so all the rest of the work is really being done by the instance and here i've just we've just created this scripted rest api it's very simple it says post attachment and in this case we just used the out of the box apis that we talked about and we sent um and then we sent the file over generated the attachment and moved it over to uh triggered this flow that then moved it over to the incident that we're going to create within the flow so when we said trigger flow it just kicked off this subflow that can be triggered from the api we created a simple incident record and then retrieved the record and moved to the attachment to that record some really simple flow designer steps um but just demonstrating that you can actually do some pretty cool things with even complex data sets like attachments and images um just using the outlet box flow designer but we're here to talk about an integration hub so let's take what we have here and very briefly we're going to do a quick addition to it just to show how easy it can be so before this demo i actually created a web hook for my um for my sandbox slack instance i'm going to pull this over here because that web hook has a has some information in it that i don't want to share just really quickly grab that um web hook information and drop it into the activity so uh what i'm doing here is i'm we we showed that it was very easy to just create an internal incident um but with integration hub the point of having the tool is to be able to integrate integrate externally without having to script out a bunch of work um and to send to another platform or to pull information from another platform so i'm going to just send a quick update to my slack using this web hook to let me know that that incident was actually created so i put my information in here i'm going to save and publish now the most of the legwork was on the slack side where i just had to build an integration app that lets me send generate a web hook and send a message directly to if it finishes publishing directly to my sandbox once the incident is created all right so now that we've got this published if i come back here and i run my same file i can go see that the incident was generated so i have the incident the new incident was created with the attachment and then just simply by adding that web hook step i was able to send a notification to my sandbox with the incident details and all that was pre-built all i did was provide it the web hook the uh authentication is all determined ahead of time with a shared secret that's included in the web hook among other things um and so all of that is done up front and then the point of having it within uh flow designer or with an integration hub is that that legwork can be done by your developers it doesn't have to be obviously it's not something that you would just hand off to a business user and say here go build out this integration but once that web hook is there once the the legwork is done for the code and it's as simple as dragging this over for anybody who wants to build a flow and these can be done within scoped applications they can be done um as you know by developers or by business users however you break down your the access but it's very easy to add something like that into a flow and and you know be off to the races so that's that's really what we wanted to conclude with as far as value out of integration hub it it's really down to what you need and what you want to accomplish but because they're so flexible in the way that they can be triggered you could do something as simple as saying that you don't you want to use a workflow for your change management process but you want to be able to let people generate change tasks once the change hits a certain state you can very easily set up a record trigger that checks the state and generates certain tasks that they've defined in that case and and then looks at a field like the the company to decide who's it is um and which tasks to trigger it could be as simple as that it could be as complex as doing a full powershell integration with uh you know some other environment that where you have to be able to run powershell to access it or if it's a legacy environment the point is it's it gives you a way to build these simple scripts and put them into flows very quickly and easily and that's really all that we're saying here is not necessarily that it's supposed to replace other functionality entirely or that it's it's the greatest option for everything but it if it is what you if it is for what you need then it can be very powerful so very briefly we'll go to questions in just a second i was just going to show you the actual some of these new features that we talked about there's a new additional trigger that you can select for your flows now called the rest api sync asynchronous and once you select that all you have to do is fill out the the basic methods the path um you can put some requirements for roll you can tell it what body type you need and what values within the body you can tell it to include query parameters and then as soon as you publish it generates that endpoint that's specified here and you're pretty much ready to go at that point you obviously need to make sure you have users with the right credentials etc but this is one another packaged way that you can actually generate those endpoints pretty quickly we talked about data stream data stream is just a way to process a lot of data quickly but it does allow you to go through and create your request information decide what type of step you're creating turn on the pagination and choose different types you can do parsing and mapping afterwards using some of the the standard types of libraries and functionality that you're used to and i can almost guarantee this is probably going to expand over time as as new requests and new standards come out so this is just another thing where they're just trying to make that job easier you could just as easily go create a rest message and try to you know do all that pagination and parsing yourself this is just another tool at your disposal and then the last one i wanted to show was the custom custom actions you can create um so you always have the ability to script within a flow designer flow without integration hub what integration hub gives you among other things is access to these different custom types that can be used within the flows which is similar to what orchestration did where you once you were past the orchestration wall you had access to a lot of these custom types of steps the process for building them is a little bit cleaner but it is it's a lot of plug and play and data pills and things like that um so these are just some of the things that you can get out of integration hub i'll go ahead and open it up for questions um and we can see if we can answer any of those great presentation and demo thanks chris and matt for um putting that together we did have a few questions come in for the from the audience so i will take some time right now to dive into those so question one does integration hub require a mid server to work yeah so i i think i can answer that one uh so it really depends on uh the type of integration that you're gonna be building uh you know uh mid server definitely if you're trying to connect to anything that's on prem or behind a firewall definitely if you're going to try to use anything like a power shell step or an ssh step you're going to have to get behind the mid server to actually be able to access those host machines that the servicenow platform as a sas is not going to have direct access to but generally if you're going through like a rest or soap or a web service that is accessible over the internet without any firewall restrictions you can do that without a mid server so so it really depends on the type of integration that you're building but uh you don't need any sort of extra subscription to set up a mid server and it's really pretty easy to do thanks chris another question we have in here is what is integration hub etl and is it licensed separately from integration hub yeah yeah so that's that's another uh good question uh and so it is uh actually completely separate from integration hub uh despite the name integration hub etl uh you know it doesn't it's not that closely connected with integration hub uh integration hub etl is really like a uh a front end that servicenow has built for these uh what's called robust transformers it's almost like the the newer phase of of transform maps uh they work very well with cmdb integrations because they let you uh go through what's called the ire the identification and reconciliation engine um without a whole bunch of scripting like you'd have to do with a transform map that's really just designed to set up coalesce field as a primary key so uh integration hub etl has a lot of uses but you know maybe they call it that because it's oftentimes doing an etl off of data that's coming from an import set that may have been gathered with integration hub but besides that it is completely separate and it's actually free to install integration hub etl now you do have to be careful because there are a lot of uh like what's called service graph connectors designed to connect with specific systems and those are uh often those often do require licensing but it is completely separate from integration hub it's generally more closely tied to itom that said of course uh it's always a good idea to talk to your service now account rep to be 100 sure about any licensing concerns you may have but in general uh etl despite its name is completely separate from integration hub awesome thanks for that chris looks like we have one more question in here from the audience and that is how do i migrate legacy custom integrations into integration hub what i would recommend as far as if i were if i were to have to do that process the first thing i would do is go and sort out kind of organize what my legacy integrations are what types they are you know so press what are the standards what systems are being integrated and depending on how those group together one of the nice things i'll say one of the nice things about flow designer is that once you build actions you don't necessarily have to build them again because you can build them to accept different inputs the downside to coming from legacy is that there's there's not a easy way to just you know point and click move everything over that i've integrated especially if you're using a lot of scripts but what you can do is like i said if you if you determine that you have a lot of powershell scripts or you have a lot of uh soap messages that you're sending out you can find ways to standard standardize those into actions that are reusable so that you just create a set of inputs you package up those inputs and then they just change depending on what flow you're running or what your integration is and then your set as far as the grouping of code that you were using before to build out all that functionality and then you're just down to passing in inputs which is a much simpler process than trying to rewrite the code over and over again in each flow and for each integration uh i don't know if that answers the whole question because it is it really does come down to your organization and what your integrations look like and how legacy we're talking uh but i would say that's a place to start yeah and i would say just to just to add to that that if you do have legacy integrations that you're trying that you're thinking about migrating into integration hub you should be able to set that up in a non-prod environment even if you don't have a subscription and seeing if you're able to do that might actually be a good test as to whether an investment in integration hub is worth it for you or not uh because uh depending on the complexity of that integration uh it may be something that you can simply do with an out of the box uh spoke in integration hub and it may not be so it's definitely something that's worth looking into well we actually just had one more question come in um also i'll answer it live so you guys can see it here um are there any performance issues if there are multiple flow operations at a given time to put it simply is there any limit to the number of flow operations the system can perform without performance issues i can answer this one because i have a uh some experience with this in a particular implementation that we did there was a a series of flows that were running triggering on a table where inserts were happening constantly and there were thousands of flows running i would not i would say i would not recommend that but that's based on a pretty standard understanding of how system you know systems work in general i would i would recommend that you have some sort of gateways or or restrictions in place so that you're not running your thousands and thousands of flow at the flows at the same time that's not to say it can't the system can't handle it but anything that you have uh especially coming from an external source uh if you're doing to anything from you know external integrations or anything that you have triggering based on just an unverifiable number of records being created i would say put some sort of limitation on it and flow designer does have some of that out of the box there's options to say don't run concurrent flows so basically if one flow's already running on this record do not run another one you can have ones that say trigger this flow only once and those kinds of limitations are you can come up with your own just to make sure that you're not overwhelming the system because each flow essentially generates a scheduled uh activity that's using up a thread on your your instance and depending on how much resource you have allocated to your instance eventually too many flows could cause some harm to the ability of the instance to continue functioning so that's just that's just my general opinion on the subject chris you want to add anything yeah sure yeah and another thing i would add to that is if you find yourself in a situation where you're concerned about running too many flows in parallel i would say really question um whether it's really necessary to do it through running a whole bunch of flows in parallel like that or could you do it in a single flow because you might be surprised the answer to that there there's a lot of uh flow what's called flow logics that exist in uh flow designer that are designed for things like iteration or if it's something like pagination then that's really what integration hub is built to deal with so uh even handling huge chunks of data you might be surprised what you can actually get done in a single flow awesome thanks guys uh thanks martin for your feedback in the chat and it looks like someone asked if um where the recording of this will be so it will be up on our youtube channel and all the attendees will get sent a link to the recording following the webinar so it looks like that's all the questions we have for today i'd like to thank everyone for attending we hope you enjoyed if you have any more questions please feel free to reach out to us at info at gladfest.com check out our website to sign up for more webinars thanks everyone [Music] [Applause] you