Every Connector Is Getting Its Own Workflow Node

Yeah, no worries. Thank you very much, Michael. Yeah, so hello everyone.

So today I would like to do a quick demo on using connectors in workflow automation. We talk quite a lot about connectors. Let me share my screen first.

Right, so I just want to caveat this a little bit because this is work in progress. So I'll not be able to show a full workflow working end to end. However, early feedback is always welcome.

And also I want to demonstrate the concept we are heading for. So I will start with, we're talking a lot about connectors. So I will start with a brief recap of connectors vision.

So this is already in documentation. So I will recommend everyone to go there and read a bit because they will become the glue which will bring the true value of platform to our customers eventually. So Reading the evil docs, connectors will bring together customer data from any source, access or external.

Michael just talked about that via working towards this right now and drive heavily platform pillar and beyond. Right, so the power of this concept is that fundamentally, product teams will need to create their connector once, and then their data will become available to all pillars and more. and how this is going to look in workflow automation. So I'll come here and I'll create a new workflow.

Okay, I'm going to start with a simple manual trigger. And this is where the magic is happening, basically. When I want to add a new node, I'm going to see that there is a new section here, which is evil connectors.

So previously, what needs to happen to have a node in workflow automation means that we actually need to implement this node in workflow automation. We need to ******** it. etc, etc. Now, what is happening is actually I'm getting a list of all the available connectors dynamically as they are.

So for example, I have 12 here in this pre-prod environment. If I come to connectors page, I'm going to see exactly the same list. And also these connectors will come as they are.

So they will come with their names, their description, their icons even. So the users will be able to understand exactly what they're coming from. So for example, if I select Evil Teamwork, which is the new name for researcher, This will appear here, and now if I go to the options, what I'm going to see is that it dynamically basically brings all the APIs for me.

So, for example, let's say I want to do something with projects, so I'll select this in the folder, and then all the endpoints. Points for this projects will appear for me, and I can say maybe I want to get all the projects, and then the further selections will come to this as well. So, when I close this, the important piece here is that this... node will dynamically be persisted against this workflow.

That means if this evil team work connector get updated, if the API get updated in the future, so for any new workflows, this will automatically appear without anyone needs to come in Evil workflow automation and do anything. and they will be available for use. The other thing I want quickly to show is that this also applies to AI tools. Let me create a new workflow.

And again, simple manual trigger. I'll put an AIA node here. OK.

And let's say I will obviously use the Access LLM. And now the new bit here is that if I go to the tool section, I'm going to have this evil tools. And again, you're going to see this very same 12 connectors here, but this time they can be used as AI tools, which means basically utilise the MCP part of it.

So I can select, for example, Evo Teamwork and then open the properties and sort it out as that. So this kind of concludes my short demo. So as I said, obviously, the full working workflow will be coming soon.

We are working towards to kind of bring all this together. If you have any questions, please put them in the chat or get to me. Directly.

And I will pass this back to Elliot, I believe you.