Live HTML mini-apps on your board: as a page of their own (an App) or as a block inside a document or canvas, installed from the community or built by your AI agent.
App Blocks and Apps are available on all Infa plans (Free, Pro, and Enterprise). Connecting a block to an integration needs a board connection, which is a Pro and Enterprise feature.
An App Block is a small, self-contained HTML mini-app that renders live on your board. A block can be as simple as a metric counter or as rich as a pull-request board fed by your GitHub connection. An App is a page whose whole body is one block: the same mini-app, given a page of its own in the board's tree.
Copy link
Overview
We at Infa think the best tool for a team is often a small one that nobody has built yet. App Blocks let your AI agent build it in minutes: one HTML file, registered on your board over MCP, rendered live for everyone on the board. You can use the blocks that ship with Infa, install blocks published by the community, or build your own.
Blocks come from three places:
Built-in blocks, on every board: Image, Component View, Paper Embed and Connected Data.
Community blocks, published by other Infa users and installable from the picker.
Every block is a standard MCP App (the open format AI chats use for interactive panels), so the same block runs on your board, on your machine with the Infa CLI, and inside an AI chat.
Open the insert menu in a document (type / and choose App Block) or use the canvas insert menu. The picker has two tabs:
On this board: the built-in blocks plus everything installed on the board. Blocks you authored carry a Draft or Published status tag and an overflow menu for publishing or removing them.
Community: published blocks from all Infa users, searchable and ordered by install count. Blocks already on your board insert on click; others show an Install button that installs and inserts in one step.
Rows with a Uses connections badge pull live data through one of your board's integration connections. After inserting one, bind a connection in its settings (see below).
To give a block a whole page instead, create an App.
Copy link
Using a Live Block
A block in a document starts locked, so the page behaves as usual: a click selects the block, and the mouse wheel scrolls the page. Double-click the block to use it. Its buttons, links and fields then take your clicks. To lock it again, choose Lock in the block's header, press Escape, or click outside it. Locking is your own view only; it is never saved.
On a canvas, a block follows the canvas's Interact / Lock control in the selection toolbar, so it can be moved like any other block.
Copy link
Configuring a Block
Select a block and choose Edit props (in the block's toolbar on documents, or the canvas toolbar). On an App, choose Configure. Infa renders a form from the settings the block declares: text fields, numbers, toggles, dropdowns.
If a block needs live integration data, one of its settings is a connection picker: a dropdown listing the board's connections for the provider the block uses. Pick one and the block starts receiving data through Infa's server. The block itself never sees your token.
Copy link
What a Block Can Reach
A block runs in a sandbox with its own security policy, on every surface. It can run its own scripts and styles, load fonts from Google Fonts, and show images and media from any https: address. It cannot make network requests of its own, load scripts from another site, open frames or submit forms. Everything a block shows comes through the host: its settings, its saved state, and the integration data Infa fetches for it.
Integration requests go through Infa's server, which calls the provider's official API with the viewing person's session and the connection bound in the block's settings. Tokens never reach the block.
Provider
Allowed requests
GitHub
GET
Figma
GET
Slack
GET
Notion
GET and POST
Linear
POST /graphql (GraphQL)
Requests outside a provider's official API are refused. Connections are managed per board: see the Integrations overview.
Copy link
Publishing and Managing Your Blocks
A block you author starts out visible only on the board it was registered on. When it is ready to share, publish it to the community: from the block's overflow menu in the picker, from your profile, or by asking your agent to call infa_publishAppBlock.
Manage everything you have authored at infa.ai/profile?tab=blocks. Each block shows one of three statuses:
Draft: only you can see and insert it.
On board: members of the board it was registered on can insert it (the default after registering).
Published: every Infa user can discover it in the Community tab and install it on their own boards.
No version pinning
Updating a block's source updates every existing install immediately, including installs on other people's boards if the block is published. Preview changes before updating a widely installed block.
Never publish a block containing hardcoded credentials, connection IDs, or board-specific data. Published source is visible to everyone; installers bind their own connections through the block's settings.
Apps and App Blocks
App Blocks and Apps are available on all Infa plans (Free, Pro, and Enterprise). Connecting a block to an integration needs a board connection, which is a Pro and Enterprise feature.
An App Block is a small, self-contained HTML mini-app that renders live on your board. A block can be as simple as a metric counter or as rich as a pull-request board fed by your GitHub connection. An App is a page whose whole body is one block: the same mini-app, given a page of its own in the board's tree.
We at Infa think the best tool for a team is often a small one that nobody has built yet. App Blocks let your AI agent build it in minutes: one HTML file, registered on your board over MCP, rendered live for everyone on the board. You can use the blocks that ship with Infa, install blocks published by the community, or build your own.
Blocks come from three places:
Every block is a standard MCP App (the open format AI chats use for interactive panels), so the same block runs on your board, on your machine with the Infa CLI, and inside an AI chat.
Apps
Building Apps and App Blocks
Open the insert menu in a document (type
/and choose App Block) or use the canvas insert menu. The picker has two tabs:Rows with a Uses connections badge pull live data through one of your board's integration connections. After inserting one, bind a connection in its settings (see below).
To give a block a whole page instead, create an App.
A block in a document starts locked, so the page behaves as usual: a click selects the block, and the mouse wheel scrolls the page. Double-click the block to use it. Its buttons, links and fields then take your clicks. To lock it again, choose Lock in the block's header, press Escape, or click outside it. Locking is your own view only; it is never saved.
On a canvas, a block follows the canvas's Interact / Lock control in the selection toolbar, so it can be moved like any other block.
Select a block and choose Edit props (in the block's toolbar on documents, or the canvas toolbar). On an App, choose Configure. Infa renders a form from the settings the block declares: text fields, numbers, toggles, dropdowns.
If a block needs live integration data, one of its settings is a connection picker: a dropdown listing the board's connections for the provider the block uses. Pick one and the block starts receiving data through Infa's server. The block itself never sees your token.
A block runs in a sandbox with its own security policy, on every surface. It can run its own scripts and styles, load fonts from Google Fonts, and show images and media from any
https:address. It cannot make network requests of its own, load scripts from another site, open frames or submit forms. Everything a block shows comes through the host: its settings, its saved state, and the integration data Infa fetches for it.Integration requests go through Infa's server, which calls the provider's official API with the viewing person's session and the connection bound in the block's settings. Tokens never reach the block.
/graphql(GraphQL)Requests outside a provider's official API are refused. Connections are managed per board: see the Integrations overview.
A block you author starts out visible only on the board it was registered on. When it is ready to share, publish it to the community: from the block's overflow menu in the picker, from your profile, or by asking your agent to call
infa_publishAppBlock.Manage everything you have authored at infa.ai/profile?tab=blocks. Each block shows one of three statuses:
Never publish a block containing hardcoded credentials, connection IDs, or board-specific data. Published source is visible to everyone; installers bind their own connections through the block's settings.