And welcome to the Tray session at the enterprise integration summit, where we'll learn how to escape legacy integration trap and add modern automation and low code integration to your environment to reduce complexity and deliver projects faster.

We've got two great speakers for us this morning. Paul Turner, integration strategist at Tray, and Mo Naqvi, solution engineer. Gentlemen, welcome.

Great to be here, Vance.

Yeah. Thank you.

Yeah. We're really glad to have Paul and Mo with us this morning. Paul advises enterprise customers on integration strategy, and we're gonna get a lot of expertise in that this morning in terms of how to use Tray to improve your efficiency of integration for both complex app-to-app integration as well as in-app projects.

And Mo Naqvi is an experienced engineer who helps customers design and build modern integrations. He has significant experience in process automation as well.

And the session this morning is “Escape the legacy integration trap.” You know, automation and smarter integration are becoming priorities in 2023 as overworked IT teams look to speed deliveries and cut development costs. And I'm sure many of our attendees here can identify with these stresses.

In the session this morning, we'll see how Tray offers a modern integration platform and tool suite that lets IT teams update their legacy tools, revamp processes, and even receive easy-to-adopt templates. We'll also get a great demo, and Paul and Mo are gonna share some real-life examples. So great session, great demo in store. Let me quickly remind you that you could download today's slides.

Just click the big red button in the view screen. You'll also see some other valuable downloads and even access to a free trial just one click away. We invite you to take a look at those, and we love to get you to interact with our speakers. So to ask Paul or Mo a question, just type in the submit a question box.

And with that, gentlemen, let me turn to you and tell us about how to escape the legacy integration trap.

Hi, everyone. And, hey. Thanks for that, Vance. Hey. I hope everyone is enjoying the Enterprise Integration Summit. Welcome, and thank you for taking the time to join our session. As Vance mentioned, escape the legacy integrating trap, why IT needs to move to low-code platforms.

We've got some good stuff to cover in this session for you today. So my name is Paul Turner, integration strategy with Tray, joined by Mo Naqvi, automation expert with Tray. My background actually is in implementing data warehouses, analytics, and ERP. I've worked as a consultant for a lot of companies from Tray to NetSuite, Workday, Ultrix, DataStax, and numerous others.

Mo Naqvi, my partner in crime here, has background in process automation. Intel positions of software engineer as well as in banking systems, companies like JPMorgan and Macquarie. What you're gonna learn in this session? You're gonna get analyst data on what you can expect, just some industry data and what you expect around productivity when you upgrade your integration tooling.

I'm gonna share some key functional areas I need to think about when you're looking for more of a modern platform.

And you're gonna get a case study as well. So I'm gonna share a real life case study around outcomes so you know what the kind of results you can achieve.

Okay. So, yeah, back when I started my career in finance business systems way back in the day, you know, there were just like a handful of apps, right, in each department, and, you know, integrations were less common versus more common. And, you know, with the deployment of the cloud, business teams were able to deploy a lot more apps, and you see proliferation.

Your industry estimates have it as around, you know, twenty five percent more apps in the enterprise stack versus five years ago. To be honest, I think it's pretty conservative. I think it's a lot more. When we talk to midsize and large companies in, you know, in their marketing teams, in their sales teams, in finance, we see easily thirty plus apps in the department.

So just a huge proliferation in data stores, making sure you just sync up master data, you know, all those things, put everything in sync and building orchestrations and now touch not one or two apps, but, you know, dozens of applications. So, you know, there's a huge amount to integrate as you guys know. Right? And you really can't get there with developers and integration specialists alone at this point.

You know, they're in incredibly short supply, as IDC noted here, and they're forecasting a pretty similar shortfall in developer talent, integration talent by 2025. One of the challenges we have is the integration software we use goes way back. Right? And way back to some cases, the Windows 2000 days.

Right? It's just not designed for that kind of agility that we need when the demand for integration, the demand for automation is from business teams to IT is 10x or so what it was five or so years ago. Right? You just can't get there relying on integration experts, specialists, you know, developer centric UIs.

You can't get there with scripting and, you know, JavaScript and Python.

So there's really other two choices. You don't do anything, and your integration backlog just kinda increases, and you get more frustrated business teams, or you really look for another way.

Okay. So let's look at the existing tooling landscape. You probably recognize some of the categories that you run today. You're looking to look at the low end integration tools, you know, the Zapiers and the PowerAutomates.

You see that a lot within business teams. They're looking to quickly put together integrations, and they're easy to use. But the challenges is that as you scale, you really need the governance, you know, the observability, you know, the life cycle management, error handling, all those things. Because once you think beyond a couple of integrations with those kind of tools and you're getting into the dozens or even the hundreds of workflows, it can get pretty painful pretty quickly. Ultimately, they're a dead end if you wanna scale, and you'll be spending more time in operational weeks versus the frontiers there. On the enterprise integration side of things, your legacy integration tools, you know, say a lot of them, as I mentioned earlier, were designed way back. Some of them have their twenty plus year old code bases.

With these kind of tools, the builder experience is often really complicated. Some of them use Eclipse-based QIs, you know, Windows-based desktops.

And it's really hard to get to ultimately where you need to get to, which is you need to get to democratized integration, right, where business teams can build with it. And they're just not designed for that. They're not sort of designed for collaborative development as well for the business technologist and IT teams to work together. Right?

They're really designed for single user kind of integration. Now API management, I'm sure you guys know some of the pains there. They're just too heavy to wait for most integrations. You're just writing Java or some proprietary code or Dataweeb and those kinds of things.

Right?

It's just too costly. You're talking hundreds of thousands or millions of dollars in developer expenses.

And then finally, there's RPA tools. You know, this is like, you know, UX scripting. These seem attractive at first. Right?

And what's not to like? You can quickly mirror the mouse movements and script the UX, but the problem is that scripting the UX is just not a robust way to build an integration. You really wanna integrate via APIs. Your UI has changed, all those kinds of things, and they've and that will call your integrations to price.

So you really wanna make sure the integrations are through APIs, not UX scripting

So I just thought I'd kind of put this out there, a quick self-assessment. So I talked to a lot of IT leaders, you know, background in IT.

You know, it's often the same challenges that come up again and again, and so I'm gonna challenge you here to self-assess on your own. If your integrations take months, maybe you got only a handful of folks who know how to use maybe you got one or two or three different integration tools, whether they're specialists and consultants only.

If making changes to integration is just painful, if someone wants to add a new condition or a branch, or you have a marketing team that has a lead orchestration that is managed with an older tool and they wanna change their lead routing rules, if that's a very painful project, or if you have a lot of infrastructure.

Right? If you have to size things like molecules and vehicles and worker nodes to handle volume, you're probably overdue to start thinking about modernizing. So, I mean, these are the signs that come up again. Some folks have more than one, but, you know, each one of these is gonna cost you time, cost you effort, or satisfaction within the business teams.

So, you know, modern integration is a solution. I just wanna share some of the stats here from Gartner. Gartner estimates about a thirty to forty percent productivity benefit and less effort when you build integrations with modern versus older code bases, older technology. And so we're gonna talk about what that looks like.

The other kinda key thing to think about is kind of thinking back to, you know, cloud platforms, really, the growth in cloud apps.

Gartner sees iPaaS, so that's integration platform as a service, is now strategic and is actually from one of their reports. They're seeing it replacing earlier versions of software.

And so what you'll find is that if you have point integration suites, older data integration tools, you may not just only be able to replace one of them with a modern iPaaS. You may be able to consolidate multiple integration, multiple service buses all into one single platform, and we're seeing a lot of that where IT teams taking a long hard look, a a pretty fragmented landscape integration platforms, and looking to roll that up into a single iPaaS. And that's a big benefits there. Right? It lowers your overall maintenance costs, and it simplifies your integration stack, and it's one platform your business folks and your IT team can also collaborate around.

Okay. So let's kinda jump into Tray here. So just a little bit about Tray. So we provide a modern universal automation platform.

So it's a single platform for both application integration and data integration. We power thousands of companies, large and small, from AdRoll and all the way to companies like, you know, GitHub and HackerOne. You can check us out on G2 and on peer insights. We have a ninety six percent satisfaction, and we're tracked by all the latest leading analyst firms.

So Gartner, Nucleus, IDC major player, and Forrester as well. So, you know, we're pretty well adopted out there and used by lots of different organizations.

Okay. So let's first kinda start with three big differences. You know, what makes modern? And this is what we've really baked into the trade platform here. So there's three big differences of Tray. The first, and this is really key, right, is flexibility.

You don't wanna have to resort to code when you get to a certain level of sophistication. Okay? So and if you're thinking about modernizing, you really wanna road test the platform to make sure that what you draw on the whiteboard as a process, you could really mirror that with low code, the pay a place where you have a custom field, for example, or maybe a connector doesn't exist, for example. You're not gonna have to resort to writing Java or writing Python or Ruby on Rails and those kinds of things.

And so people just have to do that, that's when the maintenance of the technical debt starts to build. So you'll make sure that the low code has not the requirements today. We're gonna handle tomorrow's requirements too. So flexibility is really important so that your developers can use it to speed that development with low code, your business teams can use as well.

The second here, and I kinda alluded to this earlier on, is centralization and governance. The worst situation you want is Latte Faire integration where there's not a great deal of reuse. People are stepping over each other with workflows. Maybe even using separate tools as well.

So you really wanna wrap governance around it. So you got business teams, IT, building, everyone is marching to the same drum. So things like logging and error handling and workspaces and a role-based access control, those kinds of things, the projects where teams can work together, that enables you to deploy a local initiative once ensuring that in IT that you have good governance and control. The final area is scalability.

And so what you gotta find is this is the big difference with modern vessel. Right? In order to integrate, you kinda know your volume. You see, it's pretty predictable.

Two or three integrations, you know roughly whilst we're pumping them through your platform. When you move to low code, you only need, you know, dealing ten, twenty, thirty, a hundred, two hundred workloads because it's easier to build them. It means that the old way of work nodes and provisioning and sizing starts to become a liability because, you know, you have teams rolling out integration much faster, and they used to I'll show the speed difference in that moment. So you may wanna use, for example, application integration as well as application integration because a modern iPaaS has multiple use cases in one platform.

And if you move to that, you might find the part that's not designed for those kinds of volumes. Now the big difference with a modern platform is a serverless architecture, and what that means is that it elastically scales on the back end. That it means you have to pre-provision. You have to buy workers and deploy them and those kind of things.

You can just simply elastically scale on the backbone. And so it's a big benefit of a modern architecture. It takes a lot of pain out of the kind of IT cone feeling around it.

The key thing here as well is, you know, one platform integration. Right? And so this is a big area that we focus at with Tray, which is, you know, if you consolidate a model of integration tools, you're getting to one platform. The goal is to get to handle all use cases in one solution. And I've just kinda shared here just some examples of things we see often. Alright? So then, you know, marketing teams looking to connect their stack across digital channels, things like data cleansing, enrichment, scoring, deduping, building a whole new lead management process, sales and revenue operations, integrating things like, you know, CPQ, CRM, ERP for a faster, you know, quote to catch on into their process.

Service teams in creating, you know, their customer onboarding so they can auto provision their customers.

IT teams looking to handle provisioning, so auto provision employees and deprovision them. So lots of different use cases a modern platform can handle. So let's delve into the platform. So as a next generation platform, we really provide IT teams, as I mentioned, to consolidate multiple tools to one solution. So we provide visual process management and business process orchestration.

So you can automate those processes like lead management or code of cash. Data integration, unless you populate our Redshift or Snowflake warehouse or a data lake, We provide building storage for aggregations and lookups, and we support parallelization. Also, you can basically run parallel processes of row sets to pump through a data warehouse, for example. And we also support data transformation helpers as well.

So you can do things like stream, numeric, text. You have to write code to have those transformations. We'll take care of those with these built-in helpers. We support event processing and triggering integration or animations, things like webhooks, native application database triggers, and we also support streaming.

In this case, we need to go with message queues, with building queuing, as mentioned, and also HubSpot. So pretty great way of, you know, triggering workflows, web webhooks, consuming APIs, consuming message streams, those kinds of things. And then finally, we also support publishing integration marketplaces as well. So here at Center of Excellence, for example, if you wanna publish templates, you know, publish easy way for someone to activate integration using a couple of prompts, we're able to do that so you can expose that to across your user base so they can just activate integration, but it's time to go through a whole building experience.

All these use cases are supported by our visual collaborative web based workflow builder. I'm gonna share that in a moment. On the connectivity side of things, we provide

hundreds of connectors of standard from SAP, Oracle, Salesforce, Microsoft Dynamics, database connectors, Snowflake, Redshift, Kafka, application connectors, So, you know, in the cloud, on premise. And we also have a local connector as well. So that means you can roll your own connectors visually so you can basically point out the rest API endpoints and then the operations, and we'll add that to our catalog in the build up so you can then just reuse that connector.

On the governance management and scheduling side of things, we include a management layer. So that includes everything from security. We have an insights hub, basically provides instrumentation around workflows, executions, errors, so it kinda provides you with that kind of, like, cockpit on workflow execution, you know, sub two, type two compliant HIPAA, GPR, and, obviously, with the detail, think about all the trials and merging in those areas. And then on the personas, these are the kind of folks that typically kinda use Tray.

They'll be part of that visual builder for, say, integration architects, technologists, and business teams. We also provide development APIs. So if you connectivity API, other APIs that enable developers to access our connectors as well. And, obviously, this all works hand in hand.

So, developers can use builder. They can use our APIs. So, you know, so we have something to everyone in your team.

Okay. So this is the kind of key thing here is that integration built on talent really speaks up delivery. Just share some data stats with you here as well. So there's a huge shared shift to system development.

So you could build those core integrations, but not every integration. So you can let your system developers start to fix the load off you. And they're seeing a pretty substantial increase in system developers, about 4x versus pro developers. So that's where the growth is gonna come from in your organization that's gonna be building if you provide them with tools to build.

Okay. So Mo's gonna show you in the product, but just a few things to think about. So the key here is that reflects exactly a process. So the builder experience that we provide in our trade builder, if you can whiteboard it, what it looks like in the whiteboard, we'll show that exactly in the product.

So all your conditionals, your branches, your nesting, multiple levels of loops, all of that is in the workflow. So this enables your business to build and you also feel natural as well. Also, readability is important too. So when you come back to it, there's not code buried in the workflow.

Right? It's all a visual flow.

Next is you're gonna minimize return to code. Right? Because let's say the more Ruby, JavaScript, and Python you add, the less maintainable flow. You wanna be able to add code if you want to, but you never have to never have to.

So we provide everything from all of that sort of conditional logic to handle visually. We also provide those data helpers as well, so things like text, numerics, dates, PDF helpers, all those areas as well. So you don't have to write code there either when you're concatenating and all those kinds of things and cleansing strings. So we'll support that visually within a builder.

And then finally, connectivity. So we actually provide about five hundred connectors out of the box for platform as well. So pretty much across pretty much all the mainstream, ERP and HR and CRM services and database and tools, those kinds of things.

Collaboration is really important, and this is a big difference with Tray.

You know, this kind of, like, looks like kinda comes together across a landscape. So we support concepts called workspaces and projects, and so that enables basically collaboration and composition. So, for example, you might have built a lead management project that might comprise multiple workflows, and you can bundle that into a single project or multiple workflows so you can group that together. Workspaces, you can create things like role based access control.

So you might have a contributor in marketing, owner in marketing, maybe an owner in the sales ops workspace. You can partition everyone and assign roles to them. And, also, you can reuse as well. Right?

So you might start with your lead management project. But let's say, for example, you have a separate team, separate workspace, just put a quote to cash project, then you can actually get those workflows to connect together. So you can gradually grow to having a much more sophisticated kind of integration automation ecosystem over time with everyone working autonomously, but also together, right, and also grouping your products together in almost, like, code level control.

Now I mentioned governance and management of complex projects. So this is just a kind of quick rundown of kind of what we would provide within the platform here. So we supply log streaming to platforms like Datadog for observability, so you can basically route those logs out. We provide workflow analytics, work with Insights Hub, gives you things like executions and usage.

Also, it gives you good visibility of how much you're using the platform, how the adoption is, so for a visualization around that. Virtual audit trails for managing objects. So, you know, we can basically roll back, you know, all those kind of things and look at audit trail of change management around workflows and any business usage. Look at that.

And, also, we provide basically reusability as well, what we call snippets. So you take a piece of the logic, and then you can save that and then reuse that logic later on too. Also, sandbox is doing great sandbox in one click. Right?

Think about how much effort that takes otherwise. You create a whole different sandbox environment. We need to click a workspace as a, you know, sandbox, and then go ahead and then basically work in that too. So and, obviously, with compliance.

So this is the instrumentation I was mentioning earlier. This is a few of widgets software insights hub. So things like which workflow is consuming the most tasks, which ones are throwing errors, for example, success rates, adoption across the business as well. So we've got that cockpit of insights that you can really kinda, like, see and check into, adoption.

Productivity is pretty critical. So we have hundreds of connectors in the platform. They're all included, standard. They're all versioned.

They'll continue updated. They would be managed by Tray. That's not third party management. So we've added hundreds of new connectors and thousands of endpoints refreshed over the last twelve months or so.

And we also provide a universal connector as well that plugs into any HTTP based API, so REST, GraphQL, SOAP, as well as a connector builder so you can build new connectors visually. Ideally, you wanna provide tools to your business users and your developers in one platform. So, you know, everyone's working together. So we also in digital low code, we also provide connectors through a standalone API called the Tray Connectivity API.

And so what we do here is that all of our connector library here, you basically see we expose them all as three endpoints. You know, you can get our pick list, you can get into operations, and you can execute an operation using that core connector as well. So your development team can basically get access to across the entire connect library while only basically having to worry about accessing through APIs. Similarwise integration with the development team too.

Okay. So just kinda ground up here, ground up the mode. Just kind of benefits. So I just wanna share some examples as soon as I kinda promise at the start of this.

Your benefits come across the spectrum here. So just carry custom results and when you move to modern. So I'll jump into Airbnb a little bit more detail in a moment, but as you can see, Cisco, just a vast number of automations, seventy five automations in a month in a pretty short amount of time at Cisco, and they've moved more of a self-service model in marketing for the lead management versus relying on your development team. IBM, they're using Tray to speed up their data delivery to load their post SQL data warehouse.

So rather than their team spend managing data and chasing issues out of scale, they basically cleared their team there as well as boosted some of the throughput as well into their platform. And then NetApp is using Tray for collaborative integration development across team. They've built thirty plus integrations. So, you know, real results through modernization.

Just to kinda delve into Airbnb, so they're using Tray in conjunction actually with some of the API management sub-top sort of things. They're using us to accelerate integration of their new payment processing, reach new geography then also wanna make ticketing management. So when they first started out, you know, thinking more of API kind of code first, you know, they were looking at a hundred thousand of costs in development, a project.

With Tray, they cut the projects that was sized at two months down to basically a week or so with Tray. So they're able to easily integrate, you know, HubSpot and Salesforce and Stripe, the ERPs. So when they enter a new geo, they equally integrate the payment processing with their ERPs.

They've connected Stripe for payment processing and also just opened the door for a whole stack of new use cases as well that you could respond to using low code.

So that's really just the roundup here. So just round up demo, just takeaways. You know? So with low code, it's all about flexibility.

You're doing way more with clicks, minimizing code where possible, ensuring your flows are as readable as possible, so being as flexible to handle all your business logic visually using a platform that really promotes collaboration team-based development, ensuring you have all the governance and control around it. You have connectors that are built in, a vast array of connectors, and you can build new connectors easily using a tool like Connector Builder. And then finally, scalability using a serverless architecture that you can use to scale elastically on the with demand rather than have to worry about scaling yourself and provisioning workers.

And so when you bring all this kind of together, that enables you to get to that velocity, cut development costs, and really kind of meet the business team is really what they're looking for around redelivering their integration automation demands.

So with that, I'm gonna hand it over to Mo.

who is gonna take you through a demonstration of their Tray platform. So over to you, Mo.

Thanks, Paul. I'm gonna jump into the Tray platform and just give a sense for what it would look like both as a builder and a user of Tray. And as you mentioned, I think Tray is one of the most modern automation platforms out there. And there are a lot of different ways in which that modernness really comes into play as a user.

So for example, when you first log into Tray, you'll see here all the different workflows that you've created. Tray really centers around a workflow, which is really just a series of steps that you can configure in a drag and drop interface to tell Tray what you want done and when and how. We'll go through what it looks like to actually build one of those workflows, but to just see one in action, for example, we can trigger a workflow that I've made where, for example, if I send an email to myself or if somebody were sending me an email with, for example, a file to upload, normally, I might have to upload that file manually into a system like Snowflake and then have to reconcile that file with other systems of record that we might have to see if there were any errors or if there were any mistakes in that file.

What's happening with Tray is that we are instead getting that file directly into a Teams channel, for example, or we might use Slack internally, where a user can see exactly what was submitted, can kind of update some information. Maybe I'll say that the date was actually from yesterday, and this might be our Spectrum auction.

And I add another message here, wherever it might be. And if I send this information onwards, it might, for example, inform me that it's doing that now. And if there were any errors or anything that bubbled up where maybe that file was missing some information or didn't meet some data validation rules, it might send me a message back in Teams and basically inform me of that and guide me through next steps. This workflow is something that we configured inside of Tray, and you can kind of see what that looks like here. So jumping in, we can see that the first step is the trigger when an email arrives. The next step is to just respond to that email trigger and let them know that we received it, and then to check if the email has any attachments and if it does have attachments to send a team's notification.

Now whenever somebody sends that team's notification and I act upon it, we'll kick off another workflow. So this is the second workflow where it's constantly waiting for approval or denial of that request. It's then reading that information that was sent in, sending it to Snowflake, and then reconciling it. And if needed, you know, if there's any inconsistency with the data, it's bringing that in.

So what makes this such a modern interface is just how smoothly all of this went. For one, I can see a complete log of every single step that was ever taken every single time this workflow was enacted. I didn't have to stand up any servers or any kind of infrastructure in order to do that. It all came kind of out of the box.

I can see exactly what this workflow did for me, for example, and when. Similarly, if I encountered any errors, like here, for example, it's encountered an error with Snowflake, I could see exactly what that error was and if I wanted even to retry that manually or else to set up, for example, automatic error handlers where I can say, for example, if something succeeds, perform one step. And if it fails, maybe bring in another system like Slack. And the ease with which I could bring in another system is exactly what makes Tray so powerful.

So whenever you're building in Tray, on the very left side, you'll be able to see all the different hundreds of different connectors that we have, available to you. If you are looking for a very specific system, let's say you're working with Teams or Slack or Snowflake or any of the different systems that we've mentioned here before, you can basically drag and drop that in. So I think, for example, Salesforce is a very common system for people to use. You can drag and drop that into our interface.

On the right side, you'll see all the different actions that are available to you. Instead of having to go through reams and reams of documentation, you kind of can see them in a list format in front of you here. And, for example, if you wanted to find certain records, you could select that action. You would see the authentication that you're using.

So, for example, we'll go into our sandbox system.

Then Tray will automatically find whatever records are available. So even if you have custom records or custom fields, Tray will pull those back and make them available. So let's say that we were looking for an account and we were looking specifically for, let's say, the account name and account ID. Right?

So the ability to configure exactly what my step would be, what inputs it would take, and then also to know exactly what outputs it will provide and then to pipe those outputs downstream to other systems. So for example, if I wanted to send a message in Slack that says that there was an error for a workflow related to account and then I wanted to pipe in that the output of what I just got in from Salesforce should be the input into my message in Slack, I can do that very simply and very easily. If you are working with a team that's familiar with APIs and with JSON, they'll kind of be familiar with this JSON path that we use and that we make user friendly in this way.

And if you are working with people who are even more advanced than that, where they don't wanna just use the Boolean logic and the branching and the looping logic that comes out of the box with Tray, but they want to use something more advanced like JavaScript or Python directly in Tray, they can actually write code in here as well. So coming back to that flexibility that they're afforded inside of this very powerful platform.

From a governance and management perspective, not only can you build these workflows as you go along, but you can actually collaborate with other team members and build them. And you can see a complete history of when somebody worked on a workflow. For example, I've worked on this date, and I can see my colleague, Elise, has worked on it. On these other dates, I can see what changes she made. I can roll back to them or roll forward if I need it. I can even filter for certain steps. So if I wanna look for a certain step having been created before or after a certain date, I can do that here as well.

Jumping into our main management area. As Paul was mentioning, the way that we separate workflows and separate responsibilities is through workspaces where different teams can collaborate either, for example, they might do it by business function or they might set up sandboxes for staging or for development to keep workflows where they belong as far as who can access them and specifying, for example, that a certain individual within your team might be an administrator in one certain workspace, but another individual might only be a viewer in that same workspace, and a third person might be a contributor. And kind of mixing and matching those roles to their best effect and to make sure that you have the right governance in place.

Lastly, I know we mentioned project as being a way to organize these workflows in ways that can make sense. And you can have projects that are small and just have a few different steps, and you can have projects that are very large and have multiple steps. And this project feature is a relatively new one, but it's one that is very powerful in terms of how people just organize their workflows and manage them.

So, hopefully, we've covered a broad set of topics as far as how you can automate your workflows in Tray and how you can use Tray to really make your organization more seamless, work better and faster, and to really integrate all the different systems you might have across your organization.

With that, I will send it back to Paul for our closing thoughts.

Hey. Thanks very much, Mo, for that demonstration. Really covered all the ground there. I hope everyone got a feel for, you know, the modern experience, what a Tray workflow looks like, how easy it to build, you know, some of the governance and management capabilities also within the platform. So that's really what modern integration and modern automation looks like and, you know, how you can roll this out to business teams and technologists, also to your developers as well as speed of their development.

So with that, I'm gonna hand it back to Vance.

Paul, Mo, great session. Great demo. Wow. What a great look at modern integration. I think a lot of folks are scratching their heads going, wow. How many other capabilities does Tray have? And we love having this kind of information to help people get more from their integration without having to hire more people or learn more technology.

So great session, both of you guys.

Thanks very much, Vance.

Yeah. Totally our pleasure. Really great. You know, with so much good information, we've got a lot of comment and questions here. So with your permission, guys, let's go to some questions.

Sounds great.

Yeah. Thank you.

Let me start off with this one. It's kind of one of the most popular comments we've got here. With all the automation and low code capability in Tray, how long does it take to actually build a production, not POC integration?

Yeah. We've had some customers build a production integration in a week or so, sometimes more, sometimes less as well. I mean, it all depends on the size of the integration. I mean, some cases, our customers are building a quick integration, for example, with Slack.

You're back into sort of system, for example. In other cases, mission-critical or to cache where they're connecting their CRM and the ERP process. So, you know, depending on the size of the process, in some cases, it could be days. I don't realize it longer than a few weeks, you know, such as in Airbnb's case.

Wow, Paul. That's awesome. And just to kinda drill into that a little bit, I know you have a lot of automation and low code capabilities bundled in Tray and even some templates. But what is the kind of skill or training that you recommend the early adopters have on the team to get the most from Tray and get those kinda great productivity results?

I would tag it as a power user, as someone. We call them technologists, where you'd be pretty comfortable with maybe if you wanna write some code, you can, or if you're just gonna go with a code only. So it says a power user, API familiarity, process orchestration, flows, familiarity. But the main skills really is understanding the business process, understand what the business process is gonna look like, and then understanding the systems, the endpoints, and the logic.

You know, Paul and Mo, this is really fantastic. Look at how deep the support is in Tray. Let's talk a little bit about how when people want to pivot from low code exclusively to either some extra hand coding or they wanna drill down and do some particular calls to how the workflow is gonna work. How do you end up supporting the ability for folks to add code?

Yeah. So within the tray connector base, we have many different connectors to systems like Salesforce and HubSpot and Asana and so on. But we also have connectors that you can use to do more core logic. Two of those are the JavaScript connector as well as the Python connector.

And if you think about the traditional code base that you probably are familiar with, you really have to stick to one. Right? If you're building in Python, you have to stick to Python. If you're building in JavaScript, you have to build in JavaScript, you can't really mix and match within one code base.

But I think one of the advantages of Tray is that we allow you to code in modern languages such as that, and we allow you to mix and match. So if you have some people with a certain skill set today and then tomorrow you hire people with a different skill set, they could still work on each other's workflows and build upon each other's work.

Excellent. Excellent. You know, a lot of great questions here about design. Let's just spend a minute on run time because there's so much power in the whole life cycle of what Tray is doing here. Here's a comment in question. We were glad to see the speaker talk about control and IT management. Can we get a little more detail about Tray’s visibility and governance features?

So we provide the instrumentation level, dedicated UX called Insights Hub. So Insights Hub basically provides visualization and click downs. You can see successes, errors across your flows, flows breaking up. We have flows in terms of their volume, workflow execution, just overall usage of the platform, and, obviously, you can drill down and see, for example, which ones are failing and how they failed. Our logs are pretty verbose as well, so easy for humans to understand them. And then for kind of the governance and management things, we provide workspaces.

So you can create, like, for example, a marketing workspace or a sales workspace.

You can assign roles to focus in those workspaces. You know, one might be a contributor, one might be an owner, for example. As well as you can group workflows together into a project, see if a project let's see, an easy management project, and you have, like, ten, twenty different workflows in there. Maybe one work was called another workflow. You can group them into a project also.

So, yeah, it's a pretty robust platform.

You know, guys, this has been a fantastic session Q&A. The time has just flown by. One last thing before you go. I got a note here. We'd like to have our team learn more about Tray. What's the next step? And a little bit maybe not just about the next step for trials or resources, but maybe talk a little bit about pricing and how folks begin to do a deployment scenario.

So, literally, you can head over to Tray.ai today and request a trial. It's not your grandpa's integration software. We have to wait for someone in presales to demonstrate it to you. Right? I guess you get hands on. You can go over and sample a trial, and, basically, we'll cal tol provision your full Tray account.

In terms of pricing, so we basically make it pretty straightforward, and you can tell with the Tray pricing on our website. We basically provide three editions, professional team and enterprise, and we're very clear on the functionality that gets included in each edition.

Fantastic. Fantastic. Paul Turner, Mo Naqvi from Tray. Really great session, really great demo, and a really informative Q&A. Thanks a lot, guys.

Hey. That sounds good. Thanks, Paul.

Yeah. Thank you.

And a quick note. Paul mentioned quite a number of valuable resources. We have most of them right here in the breakout room. Right under the view screen, you'll see some links, including a link to that pretrial Paul talked about. Here's a slide that'll take you directly to the Tray.ai website for some more resources.

Just click the download button for the slides. You get the slides and in that PDF download, you'll see a slide that'll take you directly to the Tray.ai website where you can get all these great resources. So again, a big thanks to our speakers and thanks to the audience for making this Q&A really, really exceptional. Thanks a lot.