Name: Trelica
Uploaded: 2024-12-11T17:25:02.165Z
Duration: 2 min 33 s
Description: AI-powered SaaS management platform enabling IT teams to discover, optimize, and automate software ecosystem management.

trelica

AI-powered SaaS management platform enabling IT teams to discover, optimize, and automate software ecosystem management.

Trelica

One of the big challenges with SaaS automation is there are many ways to achieve the same thing. But each way comes with its own compromises. We could go for a very generic approach like using Zapier or Make, which comes with the benefits of using one tool to solve all problems. But without the specificity to be targeted at IT operations, we sometimes lose some of the detail that we need to make things efficient. 

The other end of the spectrum is going for a very deeply technical tool, something like OCTA or Wakato. But there we need to have a high level of technical understanding, and it's expensive. So we need to find the right people to create and maintain those workflows. If those people leave the business or change roles, we may lose some of that knowledge. What we're trying to do.

With TR workflows is strike a balance. We created something that's built for purpose very targeted at the workflows we know our customers need to run. But also we've created flexibility within a confine that allows you to easily configure those things without high technical expertise. 

Let me show you what I mean by that. So if we create a new workflow here in TR, we've got a whole range of standardized workflow triggers that are built for purpose. For example, person leaves, person joins to support the employee life cycle. But also using API web hook triggers so we can connect into other tools within your organization and TI to other systems. Whether that's a j web hook or an Octor event hook. 

Let's take an example here from our library of workflows where we try to preconfig. 

Share the AI Agent Store with friends.

Obvious work workflows to make life easier for you. Here's one that's looking at inventory management. So as Triler discovers new applications, if we find certain conditions in this example, high access risk in Google Workspace, if a user is granting access to drive folders or email inbox, this workflow will trigger. 

We can do things there like set application status and send notifications over to the Infos SEC team now rather than just sending email. So again, we want to tap into those existing business systems. 

So we can also configure these workflows to trigger Slack notifications, Teams messages, and if we put notifications like Slack, Teams, or email into these workflows, you'll also notice we can put click button options off those notifications. So users can interact with the. 

Workflow and dictate what happens next. Let's look at a slightly more complex example though. Let's look at offboarding an employee, a classic IT automations process. Here's Google Workspace offboarding and here's an example of how we try to simplify things as much as possible while still giving you powerful outputs. 

The first two actions in my Google Workspace offboarding workflow, revoke access and clear user settings, are actually making several API calls each. For example, revoking access is going to randomize the password, revoke O tokens, reset 2FA codes. If we try to mirror that with API calls or with our recipes, we're going to have to keep building out multiple cards and you would have to know which of those actions are relevant, whereas we already know what you're trying to achieve. 

Which is pretty much the same as most other customers. We want to lock out access to the Google Workspace account. So while you can still do those actions individually, inica we're trying to wrap things up into simple digestible actions for you to make life easier. 

Another key point within the context of onboarding and offboarding is understanding the context of the user. Which again elevates us above a generic workflow tool. For example, in my offboarding workflow here, we're going to interact with the person's line manager. 

Now we know the context of the user because we can connect with your identity providers and your HR systems to understand line managers, teams, and cost center, and use that information in the workflow. This is also an interesting example because if we ask a line.

Manager here if they'd like to receive the drive folders for the lever. 

And the line manager says no I don't want to receive that information. 

We can interact again from the workflow by following up to the line manager with a slack form and say would you like to nominate somebody else to receive those files. 

And then the line manager can specify an alternative again taking us far beyond those generic workflow tools. 

But also not overly technical and relying on those communications tools like slack to tap into that process efficiently. 

And of course workflows aren't always totally linear either. 

We have to account for different situations different contexts which is why we also have these very useful but generic features around the ability to filter based on a user condition or. 

Putting in a delay step in or triggering workflows off other workflows and connecting them together. All of those powerful features you'd expect to see in a tool like Zapier but brought into a tool that's very much built for purpose for the kind of work you're trying to do. Automate your SAS stack. 

Perhaps most importantly, we also want a way to understand the audit log for these workflows. If you're not the person designed them, you need to be able to easily monitor them. So for any workflow that's running here, we can take an example here where I've got an onboarding workflow. I've got two runs in play and one that needs input. 

Now if I click on that, we get to an audit view of that particular workflow run with daytime stamps. Clear visibility as to what's holding the workflow up.

And all of this will be supported with email, slack messages, and teams notifications to prompt users or to trigger us when there's been a workflow error. Anything holding the process up. 

So again, EAS of configurability built for purpose and all in a way that ties into your existing stack such as jira for task syncing and also API web hooks from OCTA or slack or teams for messaging.

Note, that there may be slight differences in text and video. Watch video for the original content.

Trelica Video