Infinity

Infinity is flexible work management where boards hold folders and items and every column is an attribute you define. Agents create and update items, manage boards and folders, set custom attributes and react to item changes in real time.

1 trigger 32 actions API key available

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

On Board Event fires when a value is created on an item in the intake board

Get Item with Expand set to values reads the item back once its fields have arrived

Agent checks the attributes it depends on are actually populated before acting

List Items looks for an existing item that already covers this request

Update Item writes the classification, owner and due date onto the item's values

Create Comment records what the agent decided and what it based that on

The board owner approves any change to the board's attributes before the schema moves

What This Integration Enables

Infinity is for teams who would rather build their own model than accept somebody else's. A board holds folders and items, an item is a bag of values rather than a record with fixed fields, and every column on screen is an attribute you defined. That is a database with a work-management interface on top, and it means an agent working here has to read the model before it writes to it. FlowRunner agents call List Attributes to learn the identifiers a value must name, List Folders to learn which attributes a folder's items may carry, and only then create or update items with values that land in the right columns.

The same flexibility is what makes the schema the thing worth protecting. Values are cheap to change and easy to correct. Attributes and folders are not: deleting an attribute takes with it every value every item held for it, and updating a folder's attribute list replaces that list rather than adding to it. FlowRunner agents run the data work continuously and stop at the edge of the model, where human-in-the-loop review belongs.

Without FlowRunner

The model drifts Columns get added for one request and never removed, and nobody knows which are still read

Half-formed records Automations fire the moment an item appears, before its fields have been filled in

Manual re-keying Data arriving from forms and other tools is copied into the board by hand

With FlowRunner

The model is maintained Attribute definitions are read before every write, so a workflow adapts to the board rather than assuming it

Records read when complete Flows wait for values to arrive, then read the item back with its values expanded

Intake writes itself Items arrive with their values already mapped onto the right attribute identifiers

Use Case Scenarios

Intake that waits for the record to finish arriving

Infinity's own documentation is direct about this: an item is created empty and its values arrive afterwards, one at a time. So an agent triggered on item creation would read a blank record and classify nothing. The workflow here listens for a value being created instead. When the trigger fires, the agent calls Get Item with Expand set to values, checks that the attributes it needs are present, and only then acts: it reads the request text, writes a category and an owner back with Update Item, and posts a summary into Slack for the team that owns that category. Requests that arrive incomplete stay in the queue rather than being misfiled.
One board, many sources, one shape

A form response from Typeform, a signup pulled from HubSpot and a support thread from Zendesk all describe the same kind of work in three different shapes. The agent reads the board's attribute definitions once, maps each source onto them, and calls Create Item with values that name the right attribute identifiers. Where a source carries a file, Attach File From URL stores it in the workspace and the item's value points at it. The board ends up with one consistent record per request no matter which door the request came through.
A weekly model review the board owner actually reads

On a schedule, the agent reads List Boards, List Folders and List Attributes across the workspace, then counts how many items carry a value for each attribute. Attributes that no item has used in months, folders whose attribute lists have drifted apart, and boards whose views no longer match their folders all land in a digest. The agent proposes the cleanup and names the cost of each step. It does not run any of it on its own.

Human-in-Loop Highlight

Delete Attribute is the operation that earns the pause. In Infinity an attribute is a column, and deleting it removes the values every item on that board held for it. Update Folder is the quieter version of the same risk: the attribute list you send replaces the one that was there, so an agent that reads the folder, adds one identifier and forgets to include the rest has just made several fields unusable for every item in that folder. So the cleanup agent proposes and stops. It posts to the board owner: "The attribute Client Ref on the Delivery board is populated on 9 of 312 items, all created before March. Deleting it removes those 9 values permanently. Delete the attribute, keep it, or hide it from the view instead?" The owner decides, and the agent carries out only the answer it was given. Reading the model is the agent's job. Changing it is the owner's.

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

32 actions

Account and Workspace

Get Profile Returns the account the token belongs to. The cheapest connection check, and it needs no workspace.
List Workspaces Returns the workspaces the token can reach. Every other operation is scoped to one, and Infinity counts its rate limit per workspace, so this is the first call in most flows.
List Workspace Users Returns the people in a workspace: who a board can be shared with and who an item can be assigned to.
List Workspace Members Returns the memberships in a workspace, each carrying the role that decides what its holder may do. A membership is not the same object as a user record.
Invite Member Invites somebody to a workspace by email address. Used when onboarding provisioning reaches the work-management layer.
Remove Member Removes a membership from a workspace, addressed by the membership identifier rather than the user's.

Boards

List Boards Returns a workspace's boards. Each board holds folders, items and the attribute definitions those items use.
Get Board Returns one board's name, description and color.
Create Board Adds a board to a workspace. Used to provision a space per client, project or campaign on demand.
Update Board Changes a board's name, description, color or access list.
Delete Board Deletes a board along with its folders, items and attribute definitions. The widest write in the connector and one that belongs behind review.

Items

List Items Returns a board's items. Set Expand to values or every row comes back looking empty, because Infinity only returns an item's field values when they are asked for.
Get Item Returns one item. This is the call a value-created trigger follows up with, again with Expand set to values.
Create Item Adds an item to a board. Values name the attributes they belong to by identifier, so List Attributes comes first.
Update Item Changes an item's folder or its values. The values you send replace the ones they name, so read the item expanded before changing only some of them.
Delete Item Deletes an item and its values.

Comments

List Comments Returns the comments on an item.
Create Comment Adds a comment to an item. Infinity stores comment text as HTML, so an agent writing a summary wraps its own paragraphs.
Delete Comment Removes a comment from an item.

Attributes

List Attributes Returns a board's attribute definitions, which are its columns. The lookup that makes every item write correct, because there is no other way to learn the identifiers.
Create Attribute Adds a column to a board. Creating it is not enough on its own: the attribute has to be added to a folder before items in that folder can carry it.
Update Attribute Renames an attribute or changes its settings.
Delete Attribute Deletes an attribute and the values every item held for it. The operation this page's human gate exists for.

Folders

List Folders Returns a board's folders. A folder decides which attributes its items may carry, so it is structure rather than grouping.
Create Folder Adds a folder to a board, naming the attributes its items may carry.
Update Folder Changes a folder, and is also how a newly created attribute becomes usable. The attribute list sent here replaces the existing one, so include what is already there.
Delete Folder Deletes a folder from a board.

Views and References

List Views Returns a board's saved views: the table, kanban, calendar and other layouts its folders are shown through.
List References Returns a board's references, which are the links that let an item on one board point at an item on another.

Files and Hooks

Attach File From URL Stores a file in the workspace from an address and returns the attachment an item value can point at. Attachments belong to the workspace, so one file can be referenced from any board in it.
List Hooks Returns the webhooks registered on a board, including any a trigger created. Infinity deactivates a hook after three failed deliveries, so this is where a quiet trigger gets diagnosed.
Delete Hook Removes a webhook from a board. Used to clear up a hook left behind by a deleted flow.

Triggers

1 triggers

Event Triggers

On Board Event Fires when the chosen event happens on a board. Reach for Value Created rather than Item Created: Infinity creates an item empty and each of its values arrives afterwards as a separate event, so a flow listening for item creation reads a blank record. The reliable pattern is to listen for the value, then read the item back with Get Item and Expand set to values before acting on it. Infinity deactivates a hook after three failed deliveries, retrying after one minute and then ten, so a trigger that goes quiet is worth checking with List Hooks.

Frequently Asked Questions

What can FlowRunner do with Infinity?

FlowRunner agents can run Get Profile, List Workspaces, and List Workspace Users in Infinity, plus 29 more actions.

Does connecting Infinity to FlowRunner require OAuth?

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

Can Infinity trigger a FlowRunner workflow automatically?

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

Start building with Infinity

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us