ALITEO

Connect AI agents to ALITEO, the KARAT Software project, task, and service desk platform. Agents create and update tasks, run rich task filters, manage service requests, and keep delivery boards current.

1 trigger 26 actions API key available

Platform Documentation ↗ Capability data verified 2026-08-01

A support escalation or intake form arrives for a delivery team

Agent reads the customer, the request and the affected project from the message

Agent runs Check User to confirm the intended owner exists in the company and belongs to the project

Agent resolves the target workspace, project and section before writing anything

Agent calls Create Task with priority, dates, custom attributes and the confirmed solver

Agent posts the new task, its owner and its due date to the delivery channel

Where no valid solver resolves, the agent asks the delivery lead who should own the work before the task is assigned

What This Integration Enables

ALITEO is one platform holding three jobs that most companies buy separately: project delivery, a service desk, and time tracking, all scoped to a single company behind one API key. That combination is the reason to automate it rather than a nice-to-have. When the ticket, the project plan and the timesheet live in the same object graph, an agent can answer questions no single-purpose tool can, such as which delivery project absorbed the hours that were meant for the escalation queue last week.

The centre of gravity is Search Filtered Tasks, ALITEO's own rich filter exposed as an action. A flow can scope by workspace, project, section or portfolio, restrict by owner, solver or follower, include or exclude individual processing states, sort the result, or hand over a saved filter identifier that takes precedence over everything else. That last detail matters more than it reads: it means the delivery lead can define the view in ALITEO, where they already think about it, and the agent runs their definition rather than a parallel one drifting in a workflow config. Around that filter sit the writes. Agents create and update tasks, and append comments that carry their own author so an external thread mirrors into the timeline with attribution intact. They spin up projects, teams and portfolios, log time in blocks under one day, and invite users with their exact permission flags. They also search the full-text index across tasks, comments, attachments, to-dos, timesheets, meetings and documents, scoped to what the acting user is permitted to see. The one live trigger is on timesheets, which is to say ALITEO makes tracked time the thing it tells you about first.

Without FlowRunner

Intake by relay Escalations reach the board only after someone retypes them

Time discovered late Tracked hours surface at month end, after the invoice window

Stale work stays hidden Nobody has time to page through filters looking for stalled tasks

With FlowRunner

Intake straight to the board Requests land as tasks with owner, priority and dates already set

Time moves as it is logged Timesheet changes reach payroll and invoicing the day they happen

Stalled work surfaces itself A saved filter runs on a schedule and puts the exceptions in front of a person

Use Case Scenarios

Escalations that arrive as tasks, not as messages

A customer escalation comes in through a support channel. The agent reads it, resolves the owning team, and calls Check User to confirm the intended solver exists and belongs to the project before it assigns anything. It then calls Create Task in the correct section with priority, due date and custom attributes populated, and mirrors the original thread into the task timeline with Add Task Comments, each comment carrying its real author. The delivery lead opens ALITEO and finds the escalation already shaped like work.

Won deals that become delivery projects and portfolios

A deal is marked won in HubSpot. The agent calls Create Project inside the right workspace with the schedule, lifecycle status, risk flags and member list drawn from the deal, then calls Create Portfolio and attaches the project to it, populating the company registration number, VAT number and address from the CRM record. The delivery structure and the billing identity are in place before the kickoff call, and neither was typed twice.

Tracked time that reaches invoicing while it still matters

On Timesheet Created Or Changed fires as entries are logged across the company. The agent expands each entry with Get Timesheet Details, resolves the person with Get User Details, and posts billable hours into the accounting workflow feeding QuickBooks Online. ALITEO caps each poll at 1000 rows, so high-volume companies run the feed continuously rather than in a nightly batch. Time that was logged on Tuesday is on the invoice draft by Wednesday.

Human-in-Loop Highlight

The sharpest thing an agent can do with Search Filtered Tasks is also the most dangerous. Point it at a service-desk team, exclude the closed processing states, filter to tasks untouched for thirty days, and you have a list of stale tickets. The obvious next step is to run Update Task across the list with the archive switch on, and the obvious next step is where this goes wrong, for a documented reason: the archive switch archives a task regardless of its current processing state. A ticket that is still in Solving, on a customer who is still waiting and has simply stopped replying to a thread nobody answered, archives just as cleanly as an abandoned one. The customer does not learn their problem was closed. They learn it a month later, when they ask again.

There is a second edge on the same action. Update Task changes only the fields supplied, which makes it safe for single-field edits, with one exception: supplying solvers replaces the existing solver list outright rather than adding to it. An agent tidying assignments can silently remove everyone else working the task.

So FlowRunner runs the sweep and stops before it commits. The agent builds the candidate list, expands each one with Get Task Details, and routes the batch as a human-in-the-loop decision to the service desk lead through Slack: "Eleven tasks match the 30-day stale filter. Nine are in Waiting and have no customer message since the last agent reply. Two are still in Solving, including task 4417 where the customer replied four days ago and nobody answered. Archive the nine, or review the list first?" The lead answers, the agent archives exactly what was approved, and the two that needed a human get one.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

26 actions

Tasks

List Tasks Returns every task in a single section of an ALITEO project or team, with archived and completed switches to narrow the result to open work. The response can be a flat array of task identifiers or richer objects carrying identifier and name. Used as the cheap read before a targeted expansion.
Get Task Details Retrieves the complete record for one or more tasks by identifier, including description, priority, status, dates, solvers, attributes, comments and attachments. Several identifiers can be passed in one call, so a batch expands without repeated round trips.
Create Task Creates a task inside a project or team. Either a project or a team identifier acts as the parent, and when no section is given ALITEO places the task in the default section. Priority, visibility, dates, solvers and custom attributes can all be set at creation, and passing a master task identifier makes the new task a subtask.
Update Task Modifies an existing task. Every field is optional and only the supplied values change, which makes it safe for single-field edits such as moving a status or pushing a due date. Two behaviours deserve an approval in front of them: supplying solvers replaces the existing solver list outright, and the archive switch archives the task regardless of its current processing state.
Add Task Comments Appends one or more comments to a task, each able to carry its own author. Used to mirror a discussion thread from an external help desk or chat tool into the task timeline with attribution intact.
List Reaction Tasks Returns the tasks waiting on a reaction from a specific user, which is the same set that user sees in their personal action queue. Optionally narrowed to tasks still in the Solving state and optionally including tasks assigned to solver groups the user belongs to. Used to build a nudge that reflects what the person actually sees.

Search

Search Filtered Tasks Runs ALITEO's rich task filter and returns the matches. Scope by workspace, project, section or portfolio, restrict by owner, solver or follower, include or exclude individual processing states, and sort the result. Supplying a saved filter identifier takes precedence over every other setting, which lets a flow run the view the delivery lead defined in ALITEO itself.
Full-Text Search Runs a full-text search across tasks, comments, attachments, to-dos, timesheets, meetings and documents. Terms must be at least three letters and every supplied word must be present in a match. Results are scoped to what the acting user is permitted to see, so the search never widens a person's visibility.

Projects

List Projects Returns all projects inside one workspace, with an active-only switch to hide archived projects and a choice between bare identifiers and objects carrying identifier and name.
Get Project Details Retrieves full project records by identifier, including description, schedule, status, risk flags, members and custom attributes. Several identifiers can be expanded in one call.
Create Project Creates a project inside a workspace, optionally seeded with a schedule, lifecycle status, quality and deadline risk flags, members and web links. Used to stand up delivery structure the moment a deal is won or an intake form is submitted.

Teams

List Teams Returns every team in the company. Teams are the non-project containers for recurring or service-desk work, and their identifiers can act as the parent when creating tasks.
Get Team Details Retrieves full team records by identifier, including description, members and links. Several identifiers can be expanded in one call.
Create Team Creates a team in the company. Used to collect recurring work that does not belong to a time-boxed project, such as a support queue or an internal service desk.

Portfolios

List Portfolios Returns every portfolio in the company. Portfolios group related projects with client contact details and are used for account or programme level reporting.
Get Portfolio Details Retrieves full portfolio records by identifier, including type, visibility, schedule, member list, contacts, links and the company billing details attached.
Create Portfolio Creates a portfolio and optionally attaches existing projects to it. Company billing fields such as registration number, VAT number and address can be populated at the same time, which makes it a natural landing point for a customer record synced from a CRM.

Timesheets

List User Timesheets Returns every timesheet entry logged by one user, optionally bounded by a date range. The most direct way to pull a person's tracked time into payroll, invoicing or reporting.
Get Timesheet Details Retrieves full timesheet records by identifier, including the logged description, date, duration in minutes, start and end times, source component and custom attributes.
Create Timesheet Logs a block of worked time against a company, project, team or task. Duration must be greater than zero and under 1440 minutes, so one entry cannot span more than a day. Start and end times are optional and only their hour and minute components are used.
List Timesheet Attributes Returns the company-level custom attributes that can be attached to timesheet entries, with their identifiers and API codes. Call it once to discover the codes a programmatic timesheet needs.

Users

List Company Users Returns every user account in the company, covering internal staff and external collaborators. Used to reconcile the ALITEO roster against an HR system or identity provider.
Get User Details Retrieves full company user records by identifier, including preferred name, email, position, member type and the permission flags controlling what the user may create.
Invite User Adds a user to the company by email address and optionally sends the invitation immediately. Member type, administrator rights, supervisor scope and the flags controlling whether the user may create projects, teams, portfolios and timesheets are all set here, which makes this the onboarding action and the one to keep an eye on.
Check User Verifies whether a person exists in the company and, when a project is supplied, whether they belong to it. Used as the guard before assigning work to someone who may not have been onboarded yet.

Company

List Workspaces Returns every workspace in the company. A workspace is the top-level container owning projects, so its identifier is the starting point for most project automations.

Triggers

1 triggers

Event Triggers

On Timesheet Created Or Changed Fires when a timesheet entry is created or modified anywhere in the company, emitting the changed entries. Used to move tracked time into payroll, invoicing or reporting while the week is still open. ALITEO caps each poll at 1000 rows, and the first poll establishes a baseline without firing so existing entries are not replayed. The polling interval can be set as low as 30 seconds.

Frequently Asked Questions

What can FlowRunner do with ALITEO?

FlowRunner agents can run List Tasks, Get Task Details, and Create Task in ALITEO, plus 23 more actions.

Does connecting ALITEO to FlowRunner require OAuth?

No. ALITEO connects to FlowRunner with an API key, no OAuth flow required.

Can ALITEO trigger a FlowRunner workflow automatically?

Yes. ALITEO supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with ALITEO

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us