Alvanda

Alvanda is process management where the work of an organization is written as procedures made of steps, owned by positions on an org chart rather than named people. Agents read and update procedures, steps, positions and assignments so documented process and real work stay in sync.

103 actions API key available

Alvanda website Platform Documentation Capability data verified 2026-08-18

A new customer contract is signed and the onboarding procedure has to actually run

Agent pulls the account, the start date, and the service level from the signed record

List Positions resolves which seat owns each step, rather than which person happens to be free

Create Task raises the procedure's tasks against the owning positions with their due dates

List Tasks reads what is outstanding, who holds it, and what has passed its escalation threshold

Overdue tasks are raised to the position's manager on the channel that person reads

The operations lead rules on any change to the chart the escalation would otherwise force

What This Integration Enables

Alvanda makes a structural commitment most process tools avoid: work is owned by positions on an org chart, not by named people. A procedure is built out of steps, each step belongs to a seat, and a person inherits work by holding that seat. It sounds like a filing detail until the first resignation, at which point it is the difference between a process that keeps running and a process that walks out of the building.

That commitment is what makes Alvanda genuinely worth automating rather than merely integrating. FlowRunner agents read and write procedures and their steps, wire the flow between steps, raise and advance the live tasks those procedures produce, read the whole org chart in one call, and keep guiding documents, strategy, meetings, and comments in step with the work. Because Alvanda tracks the time between starting and stopping a task, a flow that starts one and never stops it keeps accruing, so the connector treats those two as a pair rather than a fire and forget. Every capability here is built and verified against Alvanda's published API, and the connector supports accounts on a staging or self-hosted host as well as the standard one.

One operational note worth designing around: everything this connection does is done as the token's owner, with that person's permissions. When a call is refused for no obvious reason, reading the signed-in person's permissions is the diagnosis rather than a retry.

Without FlowRunner

The written process and the real one diverge A documented procedure exists, and the work happens some other way

Accountability follows people Work is assigned to whoever did it last, and leaves with them when they do

Escalation depends on somebody noticing A task sits for a week because the person who would have chased it was on leave

With FlowRunner

The document is the runtime Procedures are not descriptions of the work, they are what the agent instantiates as tasks

Accountability follows the seat Tasks are raised against positions, so the work survives a person changing roles

Escalation runs on the clock Thresholds are read and acted on continuously rather than when someone remembers

Use Case Scenarios

Onboarding that instantiates itself

A signed contract lands. The agent reads the onboarding procedure with Get Procedure and List Procedure Steps, then raises a task for each step with Create Task, dated from the go-live rather than from today. It never guesses at owners: List Positions and Get Position Chart resolve which seat owns which step, and the task is raised against the seat. As the work proceeds, Advance Task moves a task on to the next step of its procedure without closing the whole thing, and Complete Task closes it when the step is genuinely done. The customer record in HubSpot and the project channel in Slack both stay current from the same run.
Escalation that happens on the clock

A procedure's escalation settings decide how long a task may sit before it is raised to a manager, and then to that manager's manager. The agent reads List Tasks on a schedule, which answers what is outstanding, who holds it, and when it is due. For anything past its threshold, it resolves the manager through the position chart rather than through a hard-coded list, and posts the specific task with its history from Get Task Step History so the manager sees how it moved rather than only that it is late. Where a task is stuck because the person holding it cannot finish it, Hand Over Task returns it to be picked up, which is the vendor's own mechanism for that rather than a reassignment invented in the flow.
Policy that stays attached to the work

Procedures point at guiding documents, the written policies and references that say how a step is meant to be done. When a policy changes, the agent updates the guiding document, moves it into the right folder, and uses List Procedure Sharing to work out which positions are expected to follow procedures that reference it. Those people get a notification with the change summarized, and a copy of the revised policy lands in Confluence for the wider audience. What the agent does not do on its own is publish, because publishing makes the document reachable by anybody holding its link.

Human-in-Loop Highlight

In Alvanda, the org chart is not reference data. It is the assignment mechanism, which means a write to the chart is a write to who is accountable for live work. Delete Position removes a seat, and with its child option enabled it removes everything reporting into it, which can take a large part of the chart in a single call. Set Position User taking somebody out of a position takes away whatever that position granted them. Delete User removes a person outright, and tasks assigned to a removed person can strand a procedure mid-run.

So a FlowRunner agent raises, advances, hands over, and completes tasks all day without asking, and stops the moment the chart itself is the thing changing: "The joiners and leavers feed asks to remove three people from positions and delete one position with two seats reporting into it. Those seats currently hold 11 open tasks across 4 procedures, including 2 past their escalation threshold. Here they are. Reassign the tasks first, deactivate the people instead of deleting them, or proceed?" The operations lead answers. Alvanda ships the safer verb for exactly this case, and the agent prefers it: Set Users Active switches access off without removing anybody, which is reversible in a way a delete is not. That is what an automation exception looks like when the platform is doing its job. The agent has already worked out what will break. It just does not get to decide that breaking it is acceptable.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

103 actions

Procedures

List Procedures Retrieves the account's procedures. A procedure is a documented way of doing something, built out of steps.
Get Procedure Retrieves one procedure by its identifier.
Create Procedure Creates a procedure. Its escalation settings decide how long a task may sit before it is raised to a manager, and then to their manager.
Update Procedure Changes a procedure's name, description, or escalation settings. Alvanda requires the name on every update, even when it is not what is changing.
Delete Procedure Permanently deletes a procedure with its steps. Archiving is the better operation when a procedure is simply out of use.
Duplicate Procedure Copies a procedure with its steps, which is how a variant is started without disturbing the original.
Set Procedure Archived Archives a procedure or brings it back. Archived procedures stop appearing in the normal listing but keep their history.
Set Procedure Pinned Pins a procedure for quick access, or unpins it.
List Pinned Procedures Retrieves the procedures the signed-in person has pinned.
List Procedure Steps Retrieves the steps that make up one procedure, in order.
List Procedure Filters Retrieves the filters available on the procedure listing, which is what the interface offers people.
List Procedure Sharing Retrieves which positions a procedure has been shared with.

Steps

List Steps Retrieves steps, optionally narrowed to one procedure. A step is one instruction inside a procedure.
Get Step Retrieves one step by its identifier.
Create Step Adds a step to a procedure. Marking it as the start or the end places it in the flow, and giving it parent steps says what must happen first.
Update Step Changes a step's name, guidance, duration, or place in the flow. Alvanda requires both the name and the procedure on every update, even when neither is changing.
Delete Step Removes a step from its procedure.
Set Step Child Links a step so another follows it, or removes that link. This is how a procedure's flow is wired together.
Set Step Parent Links a step so it follows another, or removes that link.
Update Step Estimation Time Changes how long a step is expected to take, without touching anything else about it.

Tasks

List Tasks Retrieves tasks, which are the live runs of a procedure's steps. This is the operation most flows want, because it answers what is outstanding, who holds it, and when it is due.
Get Task Retrieves one task by its identifier.
Create Task Creates a task against a procedure. Marking it recurring has Alvanda create it again on a schedule rather than once.
Update Task Changes a task's name, description, due date, or assignee. Alvanda requires the name, the procedure, and the due date on every update, even when none of them is changing.
Delete Task Permanently deletes a task.
Assign Task Hands a task to somebody.
Complete Task Marks a task done, which moves the procedure on to whatever follows.
Set Task Running Starts work on a task, pauses it, or resumes it. Alvanda tracks the time between these, so a flow that starts a task and never stops it keeps accruing.
Advance Task Moves a task on to the next step of its procedure without marking the whole task done.
Hand Over Task Hands a task back, which is how somebody who cannot finish it returns it to be picked up.
Stop Task Recurring Stops a recurring task creating any more copies. The one that already exists is left alone.
Get Task Step History Retrieves how a task moved through its procedure's steps, which is its audit trail.

Positions and the org chart

List Positions Retrieves the positions on the org chart. A position is a seat somebody holds, and it is what procedures and tasks are assigned against.
Get Position Retrieves one position by its identifier.
Get Position Chart Retrieves the whole org chart in one call, which is how the reporting structure is read rather than walked seat by seat.
Create Position Creates a position on the org chart, placed in a reporting line by its parent and filed under a department.
Update Position Changes a position's name, place in the reporting line, or permissions. Alvanda requires the name on every update.
Delete Position Removes a position from the org chart. Its child option removes everything reporting into it as well, which can take a large part of the chart, which is why it sits behind this page's human gate.
Duplicate Position Copies a position, which is how a second seat with the same responsibilities is opened.
List Position Users Retrieves the people holding a position.
Set Position User Puts somebody in a position, or takes them out. Taking somebody out takes away whatever the position granted them.
List Position Procedures Retrieves the procedures shared with a position, which is what whoever holds it is expected to follow.

Departments

List Departments Retrieves the departments. A department groups positions.
Get Department Retrieves one department by its identifier.
Create Department Creates a department to group positions under.
Update Department Renames a department.
Delete Department Deletes a department. What is filed under it is worth checking first, because a department groups positions.
List Department Positions Retrieves the positions filed under a department.
List Department Managers Retrieves the people who manage departments.

People

List Users Retrieves the people in the account, filterable by position, department, or name.
Get User Retrieves one person by their identifier.
Get My Profile Retrieves the person the token belongs to. Everything this connection does is done as them, with their permissions.
Get My Permissions Retrieves what the signed-in person is allowed to do, which is the read worth making when a call is refused for no obvious reason.
Create User Adds somebody to the account. On a paid plan this can consume a seat, and Alvanda emails the person.
Update User Changes somebody's details. Alvanda requires all four fields on every update, so a flow reads the person first and sends back what should not change.
Delete User Removes somebody from the account. Whatever they hold is worth reassigning first, because tasks assigned to a removed person can strand a procedure.
Set Users Active Switches access on or off for one or more people at once without removing them. It is the reversible alternative to deleting somebody.
List User Positions Retrieves the positions somebody holds.
List User Procedures Retrieves the procedures somebody is expected to follow, which comes from the positions they hold.
List Unassigned Users Retrieves the people who hold no position at all, which is how somebody who has fallen off the org chart is found.
Resend User Verification Email Sends somebody their verification email again. This delivers a real email.
Unlock User Unlocks an account that has been locked out, usually after too many failed sign-ins.

Guiding documents

List Guiding Documents Retrieves the guiding documents, which are the written policies and references a procedure points at.
Get Guiding Document Retrieves one guiding document with its content.
Create Guiding Document Creates a guiding document, optionally inside a folder.
Update Guiding Document Changes a guiding document's title or content. Alvanda requires the title on every update.
Delete Guiding Document Permanently deletes a guiding document. Anything pointing at it loses the reference.
Move Guiding Document Moves a guiding document into a different folder.
Set Guiding Document Published Publishes a guiding document so people outside the account can read it, or withdraws it. Publishing makes the document reachable by anybody holding its link.
List Guiding Document Folders Retrieves the folders guiding documents are filed in.
Create Guiding Document Folder Creates a folder to file guiding documents in.
Delete Guiding Document Folder Deletes a folder. What is filed in it is worth checking first.

Strategy

List Strategic Areas Retrieves the strategic areas, which are the themes initiatives are grouped under.
Get Strategic Area Retrieves one strategic area by its identifier.
Create Strategic Area Creates a strategic area to group initiatives under.
Update Strategic Area Renames a strategic area.
Delete Strategic Area Deletes a strategic area. What is grouped under it is worth checking first.
List Strategic Initiatives Retrieves the strategic initiatives, which are the time-boxed pushes inside a strategic area.
Get Strategic Initiative Retrieves one strategic initiative by its identifier.
Create Strategic Initiative Creates a strategic initiative inside an area. The quarter and year pair place it on the strategy calendar.
Delete Strategic Initiative Permanently deletes a strategic initiative with its actions.
List Strategic Initiative Actions Retrieves the actions under a strategic initiative, which are the concrete things being done to deliver it.

Meetings

List Meetings Retrieves the meetings, optionally within a date range or of one status.
Get Meeting Retrieves one meeting by its identifier.
Create Meeting Schedules a meeting for a group. This puts a real meeting in real people's calendars.
Delete Meeting Cancels a meeting, which removes it from real people's calendars.
End Meeting Ends a meeting that is under way. Anybody still in it is dropped.
List Meeting Participants Retrieves who is in a meeting.
List Meeting Recordings Retrieves the recordings made of a meeting.
Set Meeting Recording Starts or stops recording a meeting. Recording real people has consent implications in many places, so a flow that does this makes sure the meeting knows.

Comments

List Comments Retrieves the comments on something. Both the kind of thing and its identifier are required, because Alvanda's comments are shared across every kind of object.
Create Comment Adds a comment to something. Marking it internal keeps it away from people outside the account.
Delete Comment Permanently deletes a comment.
Resolve Comment Marks a comment resolved, which is how a raised point is closed off.

Notifications and search

List Notifications Retrieves the signed-in person's notifications, or just the unread ones.
Get Notification Count Retrieves how many notifications are waiting, without reading them.
Mark Notifications Read Marks one notification read, or all of them when none is named.
Delete Notification Removes one notification from the signed-in person's list.
Search Searches across the account, or within one kind of thing. Narrowing the scope is much cheaper than searching everything.

Webhooks

List Webhooks Retrieves the account's registered webhooks.
List Webhook Events Retrieves the events this account can subscribe to. Alvanda publishes no event list in its specification, so this is the only way to learn the vocabulary.
Register Webhook Subscribes an address to one event. The event vocabulary is per account, so reading it first is not optional.
Delete Webhook Removes a webhook so it stops delivering.

Frequently Asked Questions

What can FlowRunner do with Alvanda?

FlowRunner agents can run List Procedures, Get Procedure, and Create Procedure in Alvanda, plus 100 more actions.

Does connecting Alvanda to FlowRunner require OAuth?

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

Can Alvanda trigger a FlowRunner workflow automatically?

Alvanda doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Alvanda

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us