Name: Celigo Fall Platform Update
Uploaded: 2025-09-25T16:18:03.248Z
Duration: 1 h 8 s
Description: Celigo Fall Platform Update

Transcript for "Celigo Fall Platform Update": Hi, everyone. Thanks for joining. We're gonna give it another minute or so so we can wait for people to join, but we're excited to get started here soon. I see David is dialed in from California. I'm curious to see where everyone else is joining from, so pop that to the chat as we wait. K. Awesome. Looks like we got some great representation, Midwest, East Coast, West Coast. So we're excited to get started here. I'm Chris Ferraro. I'm on the product marketing team here at Celigo. I'm joined here, by Tony Curcio and Tyler Lamparder on the product management side. This is our fall twenty twenty five platform update. We'll we'll we'll share some new and interesting new features and capabilities from this Celigo platform. As a quick agenda, we'll cover some different areas of our platform from connectivity to some of the newer integration patterns that we support, like b two b manager and API management, and then we'll close out with some additional resources, upcoming events, and finish with a q and a. So if you do have any questions, please post them in the chat, and we will definitely get to them at the end. First, at Celigo, we believe automation isn't just about connecting systems together. It's about orchestrating your entire business, and that's why we built an intelligent automation platform that brings together all of your systems, teams, data, AI, all into one seamless flow. So on the right, you'll see just a few of the applications that our platform connects, Salesforce, Shopify, NetSuite, many more. Instead of siloed systems and manual handoffs, think of Solito as the central hub, making sure all of your processes are connected end to end. And that's not just app to app integration, that's across EDI, API management, and more, which we'll get into in a bit. And here are just a few of the accolades that we're very proud of here. We were named a visionary in the Gartner Magic Quadrant. So I think that's a testament to our product team's vision and forward thinking nature, and Gartner recognized that we were innovative and on the cutting edge within the iPaaS space. And then g two is also an awesome accolade because this comes directly from our customers. We survey hundreds of customers and prospects about their experience with Celigo from a product perspective and from a post sales perspective, and we were named a leader in the iPaaS segment for the last seven quarters. We were also recently, as of last quarter, named a leader in API management as well, which we are very proud of. So what does an intelligent automation platform mean? Well, for one, we believe that IT can collaborate with line of business or other citizens integrator integrators, through an easy to use experience and through the AI that we've implemented within the platform. But, also, it's one platform for every workflow that you have as it relates to connectivity. So application integration is the the space that we grew up, but also, b two b manager. So if you're exchanging documents with your trading partners, API management, if you want to expose an API to other lines of business or to customers or partners, and DI as well. So we have all the bells and whistles of enterprise grade iPaaS platform, SOC two, HIPAA, GDPR, high uptime, but we're also including, like, all of this functionality, all of these different integration patterns, all in a single unified experience and all in one platform. So you're not having to traverse different tools, stitch them together, and train teams on different skill sets. And I will hand things over to Tony now who's going to go through some of our product investment priorities. Awesome, Chris. Thanks. Yeah. Excited to be here today. I love, getting these meetings and just gonna share a lot of the work that we're doing here at Celigo. I thought it might be useful to just spend a minute on, you know, how we think about the the platform at a whole. There's really some driving forces about the way we wanna evolve our investments forward that we think are gonna be meaningful to our customers and our partners. And so, as we think about the top left of the, you know, four boxes you see in the chart here, enriching with enterprise grade capabilities, scale workloads harder, make sure we cover all of security if you're working together in teams across multiple parts of your organization. Just just a whole lot of investment in areas like that. And on the top right hand, improving user productivity and enhancing user experience overall. Of course, one of the reasons you come to automation integration technologies is because of the low code environment. But But it's not only the build time, it's also the manage, right, day two and every day onwards, making sure that I can respond to all the, operational information that I need to digest in order to take action as a to my business. Bottom left, our prebuilt integrations, one of those areas that really specifically Celigo shines that we've, gotten not just a bunch of templates that are doing meaningful things, but there are those sets of integration applications that we manage for thousands of customers that do very specific things. Not only remaining maintaining things like connectors, but we're maintaining the integrations that are changing over time as different vendors, make changes within those domains. And, of course, then we upgrade, as appropriate in those very specific business scenarios. And then finally, continuing our journey towards automation platform. So, over the last couple of years, we've made very specific strides in, bringing out API management, bringing out a next generation of EDI. One of the slides that we'll cover in the presentation today is, introducing ed effects support. And so there's a lot of ways that we look at the integration domain, and there's a variety of different patterns across it. And, again, we wanna continue to grow out to be able to help our customers, our business partners with all of those patterns. And so more to come on that. Very excited about our 2026 journey, but we're not doing roadmap today due to kind of what have we done in the last couple of months. So we're really spending that rest of the time today on, recent features. A lot of the presentation will be in the context that you see here. We think about the jobs to be done. Right? First, I need to connect my applications that I'm building where the integrations that are going to make sure my assistants talk to each other. And, of course, this is a continuous life cycle journey. A lot of the things that I monitor and I manage are informed, into things that I then want to go also build and maybe extend my business operations into. And so, this is a lot of the way you'll see the investments as we talk about them going forward. And then, of course, we'll drill into what are the very specific b two b thing and the very specific API things that, also sit within the platform. So with that, I'm gonna tap Tyler in. We'll get us started with connectivity, and we'll go back and forth and have a good time. Hopefully, you see a lot of value, with your investments with us in Salima. Thanks, Tyler. Yep. Thanks, Tony. Yep. So I'm Tyler. I'm part of product portfolio strategist here at Celigo. So let's go through connectivity updates here. Alright. So as far as, like, new connectors in Celigo, so we're constantly adding new connectors in. In this round, we've added over 45 new application connectors, all in the past few months. You can see here some large logos like SAP, Topalti, some Amazon updates, Bullhorn, stuff like that. And so we're constantly adding here to to our connector, database and making improvements on them along the way. And the next up are enhanced connectors. So these are ones that we've either maybe added more metadata to, or, you know, fixed how you work with them in general or migrated them to new frameworks. So we've got over 30 plus new, enhanced connectors here, whether it's Shopify, Acumatica, Bullhorn, Zendesk. A lot of these were, again, constantly updating these connectors so that we can maintain and keep up with, those API specs along with making improvements to make it easier for you to use them. And with that, I'll do kind of a shameless plug here of if you need a new connector, you can scan this QR code. We're typically able to add new connectors into the into the product, I'm told in two weeks. So we do sprints and two week schedules. So if you request this, it should be probably available within three to four weeks or so. So if you've got one that you've been wanting that you don't see in the list and you're using, like, a generic HTTP connector currently, just request it and we'll probably probably be able to add it, as long as you've got nice API docs that we can consume. Alright. And so on to kind of some functionality updates for connectors. So within the this was just released this week. So this is in the September release is some updates to HTTP batch handling. So historically, you know, some endpoints allow you to import data in, you know, tens or hundreds or thousands of records at a time in a batch method. And we have supported batch method for imports for a while now, but we typically expected the system to respond back with, you know, if I send it a 100 records, it tells me which of the 100 records failed. And so we required you to set a path to records in the response and that the the length of that response had to match how many records I sent. So if I sent a 100, I expected a 100 results back, basically. But that's not always the case for all endpoints. Some endpoints just say, okay, I got your request. Maybe they process it, later, or it's just, you know, maybe like a SQL query you're running and, again, it's just like an okay, I got your request. So with this update, we've made this path optional now that, to support those endpoints. And now, you can batch request against those even if your response doesn't match the link that you sent. In the next up, couple updates and deprecation here is, for NetSuite, we've added the, new WSL version for 2025 .1 and removed 2018 and '20 20 versions, and we've migrated people to twenty twenty three for now and we'll eventually migrate users to twenty twenty 5.one. So short update for NetSuite. And then for Snowflake, if anybody's using Snowflake authentication, which we know, a good amount of customers are, Snowflake themselves are deprecating the password authentication. We, in the platform, have deprecated, basic authentication for Snowflake. Any new Snowflake connection that you create will have to use key pair authentication. And the existing ones can still use password authentication, but you might be shut off here, basically, at any point once Snowflake fully deprecates password authentication. So it's best to migrate over into key pair authentication at this point. Alright. And with that, Tony will come back on stage and give some builder updates. Alright. Thanks, Tyler. Yep. We've been really pleased with the progress on adoption of the new builder UI that debuted in March. The, we've been monitoring feedback, working with customers and partners where we sense there maybe was something we wanted to tweak and improve. But, really, the response has just been so good. Somebody drew us one about a meme about it. So, we were delighted to kinda get that kind of feedback and other feedback. So, we are coming up on the, final deprecation of the old UI. So, if you're not familiar, there's been a little switch up at the top of the flow builder and API builder to allow you to go back and forth. Back in August, we flipped everybody forward. And, again, just to get one more sense and respond to anything that was coming up. But, old builder and and bubble shaped things will be going away. So, I just wanted to make sure you all are aware of that. If there is any final feedback you'd love to give, please drop it in the q and a here or reach out to us separately. Still time for us to respond if there's a a fit or finish that we need to take care of. But, there will be a maintenance update on the ninth, and, we'll say goodbye to bubble shaped objects at that point. Alright. Really excited about the work we've been doing in AI and the product over the last two years. We accelerated, code assistance in the product, flow generation, for descriptions, description generations for things like scripts, you know, the handlebars, the JavaScript. Again, all all of those, the knowledge bot. Been able to respond to questions. We're now starting the next level of that journey about in product help. And so, what you'll see in the update to this week, is that the Copilot interface or the knowledge about interface has been involved into what we're calling Copilot. It's capable of doing a lot of what knowledge about was already, but it's also context aware. So if you're on a particular screen and you're struggling with a field and you, you know, ask the question, what does this field mean? It will know where you are, and we'll be able to actually give you guidance within the context of that experience. We have a lot more plans for this in later in 2025 and in 2026, where it's going to be increasingly more and more capable. So, again, this is the launch of the context awareness of where you are and also a lot of format differences, remember some history, a little bit, better user experience when it comes to, Java snippets and, sorry, JavaScript snippets and things that it has within the experience where you could see that in its own box. So a lot of layout improvements. So hopefully you'll find the experience very helpful. And, again, with context awareness, it just kind of brings it up to the next level of, usefulness. In the, the prior release, in the summer, we did, improve the user experience for rules. So rules are, of course, things that you can build in branches and in output filters and various other parts of, the portfolio when it comes to selection criteria. We wanted to bring that up to the next generation of standards that we introduced earlier this year with Flow Builder, and so you'll see an improved user interface. And not only is it, you know, a face lift of sorts, but it also has usability improvements like being able to replicate the rules directly there. Some of the quirkiness that we had with getting warnings too quickly that things weren't set up correctly. Again, it's just a bit smarter. So you hopefully, you'll find it a easier user experience to work in anytime you're in input filters, output filters, branching. Again, it will have a value to all of those things. And I'll pass the time back to, Tyler. Tyler? Yep. Yep. And with this, September release and I think some of these are going into maybe post September and October, but we're introducing maybe 45 more handlebar expressions into the platform. So we'll have, basically, about a 100 plus handlebar expressions supported in Celigo here within, you know, September, at least, coming into October. Some of those some of those handlebar expressions, which have been long requested, are, like, pad left and pad right when you need to especially for, like, EDI transactions, where you need to add bunch of zeros to the left side of your transaction number. We now can just support that with the handlebar expression as opposed to making you go out into a script. So, ultimately, the end goal here is to get you out of building scripts as much as possible into just simple handlebar expressions. So we've given all these tools, here so that you can easily do these with handlebars as opposed to writing out the scripts. The next step are some form builder enhancements. So with form builder, we see a lot of people using form builder so that they can, you know, as a developer, you build out a form so that you can then have other users just manipulate the form for particular settings or maybe to retrigger orders that you need to to push downstream, and they can manage errors without, you know, know, you as a developer having to, manage those for them. So we've got a lot more flexibility and enhancements to form builder, so that we can now support bringing in native fields into your form your custom form that you build. So this helps, you know, if you're using if you're hiding away fields that we primarily will show you, you can show these native fields in your form itself. Conditional field controls, you can delete when certain things don't match the criteria you want. Dynamic references to handlebar expressions, so you can have, like, in my screenshot here, I selected my integration and now I can dynamically fetch the flows that are within that integration. So it's, fields that are related to each other can dynamically refresh against them. Type ahead, so if you imagine, imagine you wanna find, like, a file in Google Drive or something, right, and you've got thousands of files, instead of fetching all 2,000, 3,000 files, I would just type ahead and I would query Google Drive to fetch, you know, here are the files that match that name that I typed in. So and some other ones sorting and whatnot, but lots of form builder enhancement here in September release. And then next up, this one we've released a few months ago, but access to response headers and and transformation two dot o for lookups and exports. So this would be, sometimes you need the access to the response headers for your lookups and exports. A couple examples here being three p l central, where you need, like, the the e tag, so you can send it on later when you need to go update. SAP concur, if you need the file meta that's returned back in the headers to tell you, you know, what's the file name that I got, what's the file content so that so that, again, I can use that downstream to, pass in that MIME type as well so that I know, you know, what the file type is when I import it into my downstream system. So it just helps a lot access all the data that you potentially might need, downstream for integration. And then next up, we're going to run, in which case I'll pass it back to Tony. Yeah. Thanks, Tyler. It's nice we have such a good collaborative back and forth. Alright. So, export execution mode. We have a, massively scalable architecture, cloud native microservices. And, a lot of the ways that we operate on the back end is, that we can, you know, spawn up all of the activities in your flow. As records is coming through, we have data pipeline parallelism. Right? Data coming from the export, pager that goes to your next lookup or import. While that's actually happening, you're getting the next page and, you know, down the screen. Every one of these is actually happening in parallel. And then if you have concurrency, then it's also, you know, kind of partitioning, in in that way when it's running activities against, let's say, your back end system like Salesforce and maybe doing multiple of those, through data partitioning mechanisms. And so a lot of parallelism inherently in the platform. But one of the things we do uniquely at Twilio is that we have the ability within a particular flow to have a mix of of exports. So, not just, you know, a source of data coming from one place, but many places, and that could be not only batch there, but also real time listeners that are, all within the same flow. So if you have, let's say, 20 downstream steps, but it could be fed by a web, listener or it could be fed by a delta kind of, polling process. Again, you can stitch that together all in one place. When it came to, scheduled activities, let's say, where your export is, and you've got multiple sort of batch or micro batch activities at the same time, the default processing mode prior to August was those things would execute sequentially. We would do all of the export data from step one and all of them from export two and then all of them from export three. And so what we've done is we've really taken the handcuffs off on, now when you have a multi export flow, you know, flow that's taken from all the exports, All of those exports will be running simultaneously if you set this export execution mode to parallel. And so you may have reasons why you don't want that level of parallelism. Let's say all of those exports are running from one system and, you know, you're kind of, throttled with a number of connections, and it's just better if those things, take, place one at a time or, again, downstream where you wanna mitigate some of the downstream effects if there's too many things coming at once to some downstream system. But, really, that's all within your control now. So now the default going forward for any new flow will be that parallel. We wanna favor optimization and performance, but you still got the control that you can flip it back to serial processing if you want. But we're not changing the default behavior for anything you've created. Anything that's out there, you can we'll just run as it was. So, again, brand new feature, available this, this past summer. Alright. Next topic I'm very excited about is, multi instance flows. So there's a a few scenarios and we'll cover a couple of patterns where you may want, one flow to be reused that same logic in multiple cases. And a good example would be, let's say, I have three Shopify stores, and I want all of my work with Shopify and my ERP of choice to be just like this standard pattern. But because of the fact that I have, Shopify store one and two and three, I need, you know, three flows so they can run-in parallel on every five minutes each of them is scheduled. But the problem then with, you know we we make cloning easy. You can have lots of those and you can go into each of those flows and make changes. What if you have to make a change to your default logic across all three of those? That's where, you know, the ability to clone starts to break down because now day two and maintenance activities, I have to go make a choice. Do I update the Shopify store one and two and three? I'm using Shopify as an example only because, you know, it's multiple stores and and that's okay. So, or, you know, isn't there a better way to do this? And multi instance flows now is a better way to get to that level of scale. So what it introduces is a new, setting on your flow, where you can put this into multi instance mode. So any existing flow can be changed to the multi instance mode. There's no kind of special entry that is required. Once you do that, basically, what you'll be able to do is set up instances against that base flow. Each of these instances then can have any number of properties that are overriding the base. So if you'd like to say, I wanna override the connection in my example to, you know, this is for Shopify one and two and three is for three. That could be a thing. You could override the mappings. You could override properties, let's say, in Salesforce, the SOQL, statements, within your export, again, could be varied. And so there's really no limit to the number of properties that any one instance can be overriding. And, of course, you might have, well, first or one, I wanna do this additional tweak two. Again, there's no hard fast limit. It's like only a predefined set of properties. Every one of these instances can have variations on that theme. The only thing that they have in common is they all derive out of the same base and that they all basically override properties that were defined within that base. Otherwise, each instance can be independently scheduled and operated. You'll be able to then manage all of your errors uniquely for each one of these instances. And so what we hope this is is lets you get to higher levels of scales for your business solutions at a way that was really hard to do under old cloning models, in the past. So, and this is available for our enterprise customers. So launching within, that space. You can imagine, sorry. And when I say enterprise customer, enterprise plan under the platform licensing model. So, if you, you know, want to think about other scenarios that you might have, you might be a partner, you're hosting for various customers, and you were operating independently instead of, let's say, an integration tile with a 100 flows for customer one and two and three. Again, you might have that scale up problem for where every one of your customers need some very specific things. You might be a brand aggregator again doing similar patterns. And so, you might have the Shopify store example or another one similar to that would be I have files I'm picking up off FTP server one and FTP server two, and, again, wanting these things to operate independently as far as schedule and cadence, but also need to reuse that same base logic. Again, this is a great example of how you can get that scaled out. Alright. I'm gonna tap Tyler in, probably lean around a little bit. So I think we pass back and forth a little bit more. But, I think this was a turn on a point, Tyler. But, time zone. Time zone's a global phenomenon we need to address. Yeah. Time zones are everybody's favorite subject here. Time zones can be, of course, tricky to get right because time zones well, there's tons of them, and some of them change with daylight savings and some don't. So, we found, you know, typically, these things were set to GMT, which does respect daylight savings time. So, typically, if something was scheduled to GMT, you would, you know, offset yourself an hour whenever daylight savings time came around. But we found a lot of people, you know, maybe want actually UTC, which doesn't respect daylight savings time and then daylight and then UTC was not available in drop down menus for time zones. So we have now added UTC time support for all, time zone drop down menus. So you can select it for flow scheduling, user profile, and anywhere else there's a drop down. But typically, you could already use UTC for handlebar expressions and other other things for your data related activities, just not for scheduling and for your own personal time zone time zone preference. Alrighty. On to deploy. So we've made a few a few nice user experience changes here for in for flow cloning and integration cloning. So before, whenever you cloned a flow or cloned an integration, you always had to, you know, select which you had to select which environment you wanted to go to. You had to select when you whenever you got to the connections, you had to select which connection you wanted to, choose from. But a lot of times, whenever you were cloning an integration or cloning a flow, the vast majority of times, you just wanted to use the existing environment, use the existing connections that I already have. I just wanted to clone it and then modify it from there. So we made the cloning experience better. Whenever you go clone, we just default to choose the same connections that you already had, if they're available. And then if they if you, of course, clone it to a different environment, those connections aren't there and so it would default to, you know, choosing existing connection or create a new one. So just made the overall cloning experience, better here so you don't have to choose as many options when you're going to clone, just faster to do it. And then next up on to monitoring. So monitoring, we've got a a few improvements here. One being I'm sure maybe a lot of you have noticed in preview when you're building out, we now prominently show the trace key, for your particular record. And I'm not sure if everybody is super familiar with what a trace key is and where a trace key is useful here in the platform. So if I quickly go over a trace key, essentially, a trace key is a way that we can track what's the unique identifier for that record passing through Celigo. And what we do with this trace key is if you have auto resolution for auto resolving of errors on for your flow, which is on by default, we will auto resolve errors with the same trace key, if another error comes in later. So, for example, if I error out on import step three with trace key one and the flow runs again fifteen minutes later with the same trace key, it now, sorry, comes again with the same trace key. It will now auto resolve that error that happened maybe an hour ago or fifteen minutes ago to only show you the most recent error for that same record. Okay. So given that so that's why we wanted to show the provenance of trace key here because we always can't auto detect what the trace key is. You know, we try to do it if it's an ID field. Of course, we try to do it or if it's internal ID something something like that. But if we can't auto detect it, you can go override it in the trace key override settings and we show it here and warn you that, you know, trace key isn't, we weren't able to automatically do it so that you can go manually do it. Alright. And then this has great implications later on for some of the work that we're doing, that hopefully we'll be presenting in the winter or spring update. So Next up is redesigning email notifications. So if you guys have noticed over the past two months, we've redesigned all email communications, system email alerts that come out of Celigo. This has been a little painstaking for myself and docs and engineering to work through. There's been 80 plus emails that we've had to find throughout the system to get updated, but all these are fully updated, gives you context of which account, which environment it's from, which region it's from, and hopefully, these are looking a lot better for you. I know a lot of times the emails before kind of looked like spam, so So and you didn't know, you know, is this real email? Is this coming from Celigo? So now all these nice brand emails, they are from Celigo itself. I think with that, going back to Tony. Thanks, Tom. Yep. Part of the July release, you may have noticed, was a new user that's in every one of the user panels across the product. So whether you're at the admin level looking at the main user profile or you're within your manage tiles, you're gonna see a Celigo support entry right up at the top of the list. Don't worry. We don't it might immediately have, access. What we wanted to do was simplify how quickly we can set it up where you can enable a Celigo support representative to get in and help you out. We do find that a lot of our customers, you know, would like a support rep to get into their environment and help them triage, investigate something. And the old models were using password, token technology, and oftentimes, you'd have to get approval to use that kind of software within your environment. So we wanted to try to eliminate that from the handshakes that we'd have to do back and forth across organizations. And so, now at the administrative level, you don't have to have this enabled. You can have it turned off, and nobody in your environment can give access. But, otherwise, your admin can enable this functionality such that any user within your environment can give access. Now if I'm only a monitor user, I can only give monitor to the things that I have access to. So no user can give privileges to Celigo support more than the level of privilege they have. And so it's, you know, aptly, aligned to whatever privilege. And any user who has escalated privileges can give actually very low privileges to Celigo support and say, you know what? I don't want you guys managing anything, but I would like your help monitoring something. Again, you can set that up in the, the ensuing dialogue box. The other thing this comes along with is, time expiration. So you might wanna give this privilege for an hour for just the next call. We're gonna be working together or saying, oh, we just give it for a day, a week, however long, but it does set up by default to expire. So, again, we don't want these privileges when you don't wanna give them to us. We just wanted to simplify in those scenarios where it would be helpful that we make that process very clean and neat. So it was a great and we're already seeing the benefits of this so, customers can, again, work with our support team more more elegantly. K. And, Tyler, back to you. Yeah. Thanks, Tony. So we as part of September release, we've done a lot of improvements on the sign up feature, or sorry, on the sign up and onboarding for customers. So we didn't necessarily, in this in this update, go through all the sign up processes given that probably everybody here on this call already is in Celigo since you're on the call. So with that, a couple of the features that are you know, that you may notice here as current Celigo customers is a request to join feature. So whenever users now sign up in Celigo, we will bring them to we'll basically try to auto detect is there an account that already exist for them that they could request to join. So typically, as an admin, you may invite that user, but the user themselves, maybe they stumble into Celigo themselves or maybe they don't accept the invite in time, so it's expired. So now they come through the normal sign up process. There's a lot of ways that we've seen users actually sign up for Celigo outside of just the invite. So with this, whenever they do sign up, we will detect is there an account that already exists with that verified domain. So in my case, you know, I'm at soligo.com. When I sign up and actually verify my email, my domain is now verified. Now I can see here are the license accounts that match my email domain and I can easily just request to join that account here in the UI. This would send, an alert to the admins and owners in that instance where you could then approve that person to join, or you could deny them, in which case, they would get an email. Maybe they, at that point, create their own account or reach out to you via Slack or something like that. So we're hoping this simplifies the onboarding process quite a bit for a lot of these users so they don't end up making these orphaned accounts where they have to delete stuff and then join your account later on. The next up is account settings enhancements. For for some users where they're they are in multiple accounts, especially for, like, partners, it could be difficult to know where to update the name of the account. This company name setting was, on the owner profile, but typically, we recommend the owner profile will be a generic group email. So nobody typically would log in to that and you would you would never really know where to change it from. So we've made it super clear here. Now owners and admins can change this company setting, change the company name for their particular account. So if you do have to switch between accounts, you would clearly see, you know, here's the company name I'm going to, and here's the environment that I'm selecting. And then next, we'll go through some b to b updates. So quick update here is Edifact is now available for b to b manager. So this is super helpful for European region where typically they would be on Edifact document types as opposed to, North America x twelves. And so this is now now available for b to b manager. We've added EDI profiles specifically for Edifact, and all the relevant fields that you would need to set up an an Edifact trading profile. And then next up, a couple enhancements for EDI EDI dashboard. You can again, now that we have Edifact, you can choose between Edifact or x 12 between your trading partners, and monitor monitor those all within the EDI activity dashboard. And then we also have acknowledgement support for, enabled generation of acknowledgments and applies to Edifact as well. And then next, we've given you the ability to download those EDI files from the EDI activity dashboard. So this has been kind of a a feature that many have requested, but, now directly there within the dashboard, you can download that EDI file. So you can, you know, look at it, see it, you know, troubleshoot if there was anything that was going on, maybe that it was sent over wrong or something like that. You can just download that and easily see it. It'll be retained to your retention policy. So after your retention policy, which is tied to your, addition of Solito, it would be there or not be there after that policy. And then lastly, we've added tons of new trading partners. So just like the new connectors for AppTAP integrations, we've added tons of new trading partners for b two b manager, three m, Cisco, Orbis, I mean, tons of these. And then, again, shameless plug, if you have a trading partner that you that isn't in the list that you would like to be added, again, these can be added within two or three weeks. Just scan this QR code, fill out the form, give your EDI document to us, and we can probably get it available to you super quickly. I see, Tyler, with that, I don't know if you observed, but people will see if you have the BVD licensing and our standard licensing. You'll now see, I think it's a thousand connectors in the connector list. So nice milestone that we had over the summer. Yeah. Tyler, do you ever think this day would come? I think I remember us starting at, like, 200 and so. 200 to a thousand is quite a bit. Yeah. Yeah. And just because we have a couple extra minutes, we're running pretty good. But, yeah, like, part of the, one of the questions I saw come in was about our AI strategy, you know, and, of course, we're using AI within our organization to help us to get to higher levels of productivity as well. So one of the things that Tyler mentioned before about, like, if you do have a a connector request, in, you know, that organization has standard APIs or standard EDI documents for these or Edifact docs, definitely, again, reach out. Use those QR codes. We'll make those available. If you're not in our connective community, Tyler, what's the best way for them to find, you know, where to go in our connective community? Because I could also submit through that, venue. Yeah. The product feedback category in the community, it has the pinned about this category at the top of that category, and it's got the links for submission here. But you can also submit directly into product feedback and we'll take it as well. Okay. Yep. And if you have other types of feedback, of course, what we'll do is shameless plug for that as well. Yeah. Love to connect with you there. We're actively engaged, not just Tyler and I, but just a lot of folks on our product management team and other parts of our engineering design and research teams. And, it's been a great venue for us to get other feedback coming in for users who are in the product on a regular basis and the kind of things you might be facing are different than somebody else's face. And, again, just as much of that feedback as we can get is great. So, alright, so that's our well, maybe kind of intermission there. We'll move further into some, work on, API management. So, one of the things that we launched last year was our API management layer allows us to get to really full governance and things like, rate limiting enforcement for any of the endpoints you're building within the platform and you're exposing to external users. We have our portal. And so really scores high on not just things like, you know, the management policies for security, but also monitoring for who are my consumers and how much are they using, and how do I judge my partnerships by levels of activity, different ways that you could do security and governance around the, types of, security policies very specifically like JWT or OAuth. And so a lot of flexibility within that model. One of the paramount ways, though, that a modern API led integration strategy works is facilitating levels of reuse. So when I think about my ability to connect to any of these systems, of course, integration technology accelerates that. But now they start to move up the picture on the, slide we have here, start to then compose different ways that I'd like my, back end and systems to be used. So I compose APIs or composite services, stitching together some of the information from system a and system b, and I created out of that an API. And that was where API builder earlier this year really comes to shine because it allows you to use all of that connectivity, compose it in interesting ways. We built underneath our API builder a much faster runtime engine that doesn't optimize like flows for transaction guarantee and resiliency and recoverability will start. It optimizes for latency. And so, again, that that processes very quickly through all of the steps of your flow in order to get a request and response that can function quite quickly as you would expect from, you know, any API that you're trying to invoke. So that's a little bit of context for the next feature I wanted to get into, which is optimizing reuse. So, we've introduced it now on this release, the Celigo API connector. What it has access to is basically three different patterns within the product, which are the APIs you've built within your environment, whether using API builder or JavaScript, but also the things that are imports and exports, you know, any one of our flow steps or, you know, API steps step within builder immediately get an API endpoint of their own that you can invoke and go against those to, get response. So not only is it the API builder APIs, but it's also your imports and exports. You'll see now it's very quickly to in any flow say, yep, I'd like to reuse that as part of this flow. Within your connector list, you'll see the Celigo API connector, be able to pick any one of those endpoints as well as our standard APIs as well as listeners, where you can, actually interact with and maybe send data to. So, again, facilitating reuse is this is what this one is all about. So you'll see that in your list of connectors. And, hopefully, again, it just looks to accelerate that API led integration journey that you may have. One of the, other things that came out, I believe, in the August release was the ability to clone API that you built in API builder. One API builder shipped in March. It was under sort of a limited use license kind of preview model. It became a bit more formal in the, I think it was the May time frame. But as people were starting to adopt it, of course, we need to start managing life cycle across, not just within an environment so I can clone it there, but also promote it across environments. And so, you can now, use the cloning feature again as of the August release to do that integration life cycle management, promoting these things across environments. Alright. So, so with that, we, wanted to do a little bit of something special today. So, again, this is a recap of everything that we've had to date in the product. A little bit of a sneak peek that we did on some of the other handlebars that are coming up, But we have some very exciting things coming up in the fall, one of which we want to, give a little preview to. Tyler, did you wanna help intro at all? Well, normally, when people are in front of us, we can ask them to raise their hands and stuff. But, given that we're we're virtual, we can't do that. So I don't think so. Alright. So maybe you've got in that spirit of it raising your hand. One of the most requested features, for a long time has been one that we're again ready to start to get out. So, without further ado then, again, this has come from lots of customers asking this question, and, hopefully, you enjoy the video. Yeah. I think we've oh, there we are. No. There we are. We did a test Technical difficulties. Yeah. Yeah. I like that word too. Yeah. Dark mode right there. The power of dark mode. That's right. All encompassing. Yeah. But we did need to give everyone some time to digest that because of how important and how requested it is. Okay. Well, before we wrap up here with q and a, I did wanna make sure that you all know where to go if you'd like to dive deeper or get some extra help. So our builders hub is the place where you find blogs and short demo videos that can help jump start your projects. It spans everything from our API features, app to app, EDI, and more. Help center is your go to for, troubleshooting articles, detailed documentation. The connective community is something that Tyler helps to start where you can connect with your peers, ask questions from people who are in similar situations from you, and share some ideas on how you're using Celigo. And if you want something that's more structured, Celigo U offers free online training with courses and certifications and more structured learning paths for you to grow your expertise. Finally, there's office hours. So that's a chance for you to actually connect with our team if you have more of a a one off question. And then there is the more resources, section, within our docs page. And that's, you know, more that's additional documentation, more self serve on any of our integration patterns. And I know that you're probably thinking the product and product marketing team is so awesome. How do I actually get a chance to meet with them in person? Well, you're in luck because there could be a roadshow by you coming up. We just finished Toronto, but we do have Atlanta on November 5. It's a chance to not only meet with our team and meet with, other customers and prospects, but to envision different ways that Celigo can be used, within your organization. So we go through, all of our different integration patterns. We have a a b to b manager section for EDI. We have an app to app section for, more of our standard iPaaS use cases, and we have an API and an AI section. So it's more of an art of the possible, understand not only how you could use Huddl go now, but also in the future, regardless of, the direction that your organization takes and what integration challenges come your way. So we would love to have you there in person. You can go to soligo.com/soligo-connectiveroadshow2025 for more information or to register. And before no. I guess we can go right into q and a now. We have around ten minutes, and I know there were some burning questions in the chat. So, I can read through the first one just to kick start us from Jody. Do you have any plans to implement a publisher subscriber model, or is there one that I have missed? I could interpret publisher subscriber model in couple of different ways. So, Jody, sorry if I'm I'm missing it. Typically, that's either language with, respect to event streaming, where people kind of subscribe to eventing queues or it could be, subscribing to APIs. And so for for sure, in the API management, part of what we have there is the ability for your, API product owner to publish APIs out to the portal, and then subscribe. The API management, comes along with ability to allow self subscription where somebody goes in and can just sign up themselves or approval processes. So that's for sure, you know, in that part of the, the product API management. If that was more of an event streaming question, things we're looking at with respect to queue subscriptions in our 2026. You do wanna reach out, like, on this topic or any topic. Feel free to ping us out in the, connected community or email us directly, make our emails pretty available that way. So or or, Joey, put a follow-up, you know, question if I didn't quite hit your your question there. And that there's one here down here. We'll start from the beginning here. There's one for you, Tony dot ai. Can you walk us through the three tiers of Celigo AI strategy again and how they're showing up in the product today? Yeah. Sure. A on the back end, where we are doing things like the AI for error management, categorizing errors, understanding how to, allow things like rate limiting and retry mechanisms on the back end as well as in the lab, how we're doing things like the connector development that we talked about here. AI that you see in the product itself, like the Copilot, the code assistance, the flow generation description, so to improve productivity at that layer. The third tier, of course, is the how do we help you build Agencia workflows and AI agents. And today, that's been things like our AI connectors. Instead of the connectors that we actually launched over the last couple of months have been to things like Gemini, Omama. And so you find those connectors in the product to allow people to build the Genesys workflows. You'll also see in our marketplace that we have a lot of jump starts now for, working with vector databases like Pinecone, chat, OpenAI. We just wanna see chat with you OpenAI, to do things like summarizations and text generation, emails, so you'll find a a variety of those ways. Again, a lot more on the road map as you might imagine since everybody's investing in AI. But those three tiers sort of, the back end, the platform services, the user productivity, and the UI, and then the, building AI solutions yourselves, how we help you guys do that. Thanks. There's one here for, we run the same integration process across different a few different regions like North America, Europe, APAC. Right now, we're basically copying and maintaining separate flows for each based on what you're saying. I think multi instance would let us set up set it up once and just manage the variations instead of rebuilding everything three times. Am I thinking about this correctly? And the answer to that is yes. So, I we have this exact same use case internally where we sync over, you know, we have a North America and an EU region for Integrator I Integrator IO. If we need some of that data out of any of those regions and sync it over to whatever system, we always have to make, you know, two flows or we have to use two exports for the same flow. And so for those workflows, we will be migrating them to multi instance as well so that so that it's just one flow to maintain and you have an instance for each region. And that's a really, really easy use case because the only override or, yeah, the only override that you need for those instances is probably just the connection. So I just need the EU connection or I need the North America connection to be overridden, per instance. Alright. Next one, like, also a multi instance flow. If we currently have a flow for store one and a flow for store two, is there an easy way to create a base flow and set each of my current flows as instances? Or would I need to clone a current flow and build out the instance from that? Yeah. I can take that one. And so in the product today, there isn't a sort of morph into instance functionality. Your the first one, the base flow, just pick one. That's easy. You know? And, of course, if you had one that was cloned, I would pick the one that was the original. And then the really the thing you need to do is set up a really effectively an empty instance for your store one, and then, you have to figure out the deltas to store two. Now having said that, I have, some, code we've been working on that, is, what we call transmogrification. You know, like, kinda convert this thing over. If you, Craig, wanna be a, a test subject of something like that, reach out and, we we'll try to figure out the way to distribute that. That's some in some testing right now. I'm assuming that we'll have some customers ask for this. Like, I have a 100 of these things, and I wanna try and modify all of them. But, again, looking for some early adapters to just validate it with fewer flows in mind. So, again, happy to work with you on that. And the next one, are there any enhancements for cache application module? For that one, we'll probably ping you afterwards. Tony and I are mainly on platform and connectivity, and then, we have separate PMs that are always focused on integration apps and stuff. So, we'll check with them and see what the road map looks like there and email you out separately. Question from Todd. What was that about extensive? That was in regards to the access response headers. So, for extensive or previously three p l central, a lot a lot of times you needed the etag that was returned from a lookup or something like that, which you then needed to pass on to a subsequent, import step. So, now lookups can reference response headers, so you can easily just reference that response header and pass it along to the next step that you need. I have some ideas, but could you provide an example of something you would reuse with the API connector? Yeah. I mean, it could be really any core piece of functionality that you might wanna do. Let's say in flows, you wanna look up customer information, but you have two CRMs. It might be interesting to create an API that does these look up to get the customer detail in a very standard way against both of those. Maybe even optimize it. We know 80% come from this CRM. So let's do that look up first in the API, and then we could skip the second lookup, and then just return a conformed payload to any other flow or other API that needs that information. So that would be, like, the kind of scenarios where and if you wanna standardize the processing logic for any back end, thing that's gonna be reused one or more times across your integration stack, and that's a great example for one. Yep. Any update on the release of NetSuite REST connector? So this one, we actually, we're we have been discussing over the past couple weeks here, and hope to have something here. Yep. You can currently use REST API against NetSuite, using the generic HTTP connector. It does support o auth one, which you can connect to NetSuite with your tokens. If you do need to go that route because, for whatever reason, maybe you can't use our native one, I would request from your account manager or something that, you know, this connection is just to NetSuite. Can you have another endpoint to to supplement that given that we don't have a rest connector for NetSuite? So if you do need that, it is available currently just in the generic, and I would request your account manager to get that endpoint for you. Any plans to use AI or something else to help with GDPR compliance? It's an interesting question. Blake, let's follow-up on that one. I think, you know, we we do, as a SaaS vendor looking to operate, globally, you know, we do a lot of work to, be GDPR compliant ourselves in the way that we operate. I'd I'd be curious about the criteria that you're trying to, satisfy with respect to your use, and I would only have to guess, with limited knowledge. So, again, happy to work with you offline on that one. I think that was that, Chris. That was all the q and a that came in. Yep. I think we hit everything. So yeah. And we're right at time. Look at that. Perfect. So we are going dark just was to, like, fill a minute that we have. Yeah. It was all by design. Well, alright. Thanks everyone for taking the time to tune in today. I hope this was really helpful. And, yeah, we will see you again next time. Thanks, Phil Trump. Bye.