Data Engine Plugs Into Every Pillar

So, Matt.

Matthew Harvey 3:31

Yeah, I'll just share my screen. Thank you. OK, you should be able to see that now.

So, to start with, we have... In platform, we have all of the sort of pillars have already been mentioned. I'm going to start with workflow automation.

So if I just create a new one called AD demo. The connector, we'll create it, and then in here, as you've seen in previous iterations of the meeting, shown the Evo connectors. So, in here now we have Access Data Engine, so if I just drag this in and click on it, it should load up.

So, essentially, we've added... bunch of functionality that you can connect to a data engine. If I go to folder, you can see we have a whole different bunch of things you can do. I'm just going to focus on a few of these today, because otherwise they would take me a very long time to cover everything.

But essentially, what you can do is just select endpoint under a certain folder. API version, but that we left that as optional, and if I press query. Then we can see for my organization, we should take a pretty proper test if we just wait for it to execute.

OK, we've got results saying. This is the pre-protest, this is your domain logo, etcetera, etcetera. and that lines up with what I have in Data Engine here with that organization and a bunch of data in here. Now to get to the more exciting part of this demo, if I swap over to what I've already set up in yesterday, so we've got a schedule one.

So it's kind of an example of how you'd actually use this connector to do something in Data Engine. So, we have a trigger. And then we will call a schedule which exists in data engines.

If I hover over to schedules, we have AD connected demo, which will basically just refresh one of the tables I have. I believe it's this second one down, which is full of That's just one row about the date and time so that when that refreshes it will go to today. So if I go back to workflow automation, if I press run here.

So, see that that ran, and then it sends a post request, says success tree to trigger the schedule. And if I go back towards data engine, we see a few seconds ago it was successful. So if I go to the properties here.

And then... I think it's a better way of doing this if I go to... view data, and we say updated to the 15th, so which is today. So that means the data refreshed okay.

It's not kind of a demo about how Data Engine works, but more of a demo how we can connect stuff to it. So that kind of shows you how you can actually call something within Data Engine from any of the pillars. I also have another example, which Probably more relevant to how people would really use it.

It's a data one, so.. . For this example, I have selected the data folder, a table, and select. So within data engine, I have this table, which has about 200 rows in, and then if I...

Send a request there. I mean, I do the full run. It'll be easy to show.

OK, I waste today, see my no data finds. OK, so here. So in principle, I'm just going to show in principle that it worked yesterday, so we'll just carry on.

You can essentially get data engine, so whatever your output is of the rows, you can then get the data results and then put that into a data table within workflow automation. So you'd have user ID, title completed. So, sure, that's used to work, but I think you can kind of get the idea if I went to here and if I did.

Test. I can show you the first half. So you get a result, you'd get zero, and then you'd get the time, hour, date, etc. from that table we've just done already.

And that means kind of you can transfer data from data engine to work automation or vice versa, etc, etc. So that kind of covers everything I wanted to show a part of workflow automation. But if we swap to another pillar, which is co-work creator, we can create an agent using that connector as well.

So if I could create manually, I just called AD demo again, just call this AD demo. And then an email can be me. Next, connectors.

So this will be the same as across everywhere. You would just search for Access Data Engine. And then next, system instructions, help with ATE, et cetera, et cetera, carry on.

And then create it the same way. then you'd have an agent that can use our connector. And then if I swap over to teamwork as well, I'll create a, I found this to be the most. Good example of how a connector would work in actual real term.

So if you've got AD connector demo, we can create it in here. Instructions, we don't need any instructions for this. Uploads, nothing, connector, so we get EVO product data.

Data engine. Doesn't use any instance here, so that's fine. Actions, collaborators, yeah, that's okay.

So here in Researcher, we will just have this in my notepad. So can you please use the data engine connector and retrieve details about my accounts? I'm hoping this will know what it's doing.

Thing with AI, it's a bit hit and miss, but hopefully it will be okay. So here you go. So it's listing all the operations that we have for data engine.

So it's going to call get accounts and then hopefully that returns back and it will tell me. About what I'm doing, so just gotta wait for this. My account details, so data preview, we've already seen, account ID, region.

It says more information, so licenses, data refreshes, etcetera, etcetera. Also, I'll swap, so this kind of shows you can get any kind of data towards researcher. I've did one yesterday, so if I swap over to here.

This one, sorry, it was new. So this is kind of 1 I made earlier as well. So I basically just actually made a dashboard about everything you have in data engine.

So if I open a new tab, so it's nice and see. This is just the one prompt. So you can basically go tables, I've got all of this stuff, connections, I have everything here, schedules, data flows, data screen, data loaders, users.

The whole, the whole platform you can get, and... And it does this by basically having a massive API spec. This is the most unreadable JSON ever.

So I have a local version that's a bit nicer. So all we do is expose tons of endpoints that this connector can call, and then you can do it with your permissions via token. So anything that you have access to data engine as your user, you'd also have it via all of the pillars.

So I think that's everything I had planned to show, but it's kind of just the tip of the iceberg when it comes to connecting all of the things together. I could show a lot of stuff, so I don't know who's next, but I think I'll hand it over if there's any questions.