@fusebase/fusebase-gate-sdk 2.5.1-sdk.2 → 2.5.4

package/dist/apis/PortalsApi.d.ts

@@ -5,7 +5,7 @@
  * Domain: portals
  */
 import type { Client } from "../runtime/transport";
-import type { AddPortalAiAgentBlockRequestContract, AddPortalAiAgentBlockResponseContract, AddPortalAppBlockRequestContract, AddPortalAppBlockResponseContract, AddPortalAppPageRequestContract, AddPortalAppPageResponseContract, AddPortalBlankNoteBlockRequestContract, AddPortalBlankNoteBlockResponseContract, AddPortalBlockRequestContract, AddPortalBlockResponseContract, AddPortalCardBlockRequestContract, AddPortalCardBlockResponseContract, AddPortalCardGroupBlockRequestContract, AddPortalCardGroupBlockResponseContract, AddPortalCarouselBlockRequestContract, AddPortalCarouselBlockResponseContract, AddPortalChatBlockRequestContract, AddPortalChatBlockResponseContract, AddPortalCountdownBlockRequestContract, AddPortalCountdownBlockResponseContract, AddPortalCustomWidgetBlockRequestContract, AddPortalCustomWidgetBlockResponseContract, AddPortalDatabaseBlockRequestContract, AddPortalDatabaseBlockResponseContract, AddPortalEmbedBlockRequestContract, AddPortalEmbedBlockResponseContract, AddPortalFileUploaderBlockRequestContract, AddPortalFileUploaderBlockResponseContract, AddPortalFormBlockRequestContract, AddPortalFormBlockResponseContract, AddPortalHeadingBlockRequestContract, AddPortalHtmlCssBlockRequestContract, AddPortalHtmlCssBlockResponseContract, AddPortalImageBlockRequestContract, AddPortalInfoBlockRequestContract, AddPortalInfoBlockResponseContract, AddPortalKanbanBlockRequestContract, AddPortalKanbanBlockResponseContract, AddPortalLinkedBlockRequestContract, AddPortalLinkedBlockResponseContract, AddPortalNoteBlockRequestContract, AddPortalNoteBlockResponseContract, AddPortalTaskListBlockRequestContract, AddPortalTaskListBlockResponseContract, AddPortalTextBlockRequestContract, AddPortalTimelineBlockRequestContract, AddPortalTimelineBlockResponseContract, BulkInviteToPortalRequestContract, BulkInviteToPortalResponseContract, CreatePortalFolderRequestContract, CreatePortalFolderResponseContract, CreatePortalPageRequestContract, CreatePortalPageResponseContract, CreatePortalPageWithNoteRequestContract, CreatePortalPageWithNoteResponseContract, CreatePortalRequestContract, CreatePortalResponseContract, DuplicatePortalItemRequestContract, DuplicatePortalItemResponseContract, DuplicatePortalRequestContract, GetPortalPageBlockCountResponseContract, globalIdInPathRequired, InvitePortalManagerRequestContract, InvitePortalManagerResponseContract, InviteToPortalRequestContract, InviteToPortalResponseContract, ListPortalAiAgentsResponseContract, ListPortalChatChannelsResponseContract, ListPortalChatUsersResponseContract, ListPortalContentResponseContract, ListPortalDatabaseBlockSourcesResponseContract, ListPortalLinkableBlocksResponseContract, orgIdInPathRequired, OrgPortalListResponseContract, PortalDetailContract, PortalTextAndMediaBlockResponseContract, PublishPortalDraftResponseContract, SearchPortalInfoBlockIconsResponseContract, SetDashboardViewReadonlyRequestContract, SetDashboardViewReadonlyResponseContract, UpdatePortalAccessRequestContract, UpdatePortalAccessResponseContract, UpdatePortalCustomCodeRequestContract, UpdatePortalCustomCodeResponseContract } from "../types";
+import type { AddPortalAiAgentBlockRequestContract, AddPortalAiAgentBlockResponseContract, AddPortalAppBlockRequestContract, AddPortalAppBlockResponseContract, AddPortalAppPageRequestContract, AddPortalAppPageResponseContract, AddPortalBlankNoteBlockRequestContract, AddPortalBlankNoteBlockResponseContract, AddPortalBlockRequestContract, AddPortalBlockResponseContract, AddPortalBpmnDiagramBlockRequestContract, AddPortalBpmnDiagramBlockResponseContract, AddPortalCardBlockRequestContract, AddPortalCardBlockResponseContract, AddPortalCardGroupBlockRequestContract, AddPortalCardGroupBlockResponseContract, AddPortalCarouselBlockRequestContract, AddPortalCarouselBlockResponseContract, AddPortalChatBlockRequestContract, AddPortalChatBlockResponseContract, AddPortalCountdownBlockRequestContract, AddPortalCountdownBlockResponseContract, AddPortalCustomWidgetBlockRequestContract, AddPortalCustomWidgetBlockResponseContract, AddPortalDatabaseBlockRequestContract, AddPortalDatabaseBlockResponseContract, AddPortalDynamicTableBlockRequestContract, AddPortalDynamicTableBlockResponseContract, AddPortalEmbedBlockRequestContract, AddPortalEmbedBlockResponseContract, AddPortalFileUploaderBlockRequestContract, AddPortalFileUploaderBlockResponseContract, AddPortalFormBlockRequestContract, AddPortalFormBlockResponseContract, AddPortalHeadingBlockRequestContract, AddPortalHtmlCssBlockRequestContract, AddPortalHtmlCssBlockResponseContract, AddPortalImageBlockRequestContract, AddPortalInfoBlockRequestContract, AddPortalInfoBlockResponseContract, AddPortalKanbanBlockRequestContract, AddPortalKanbanBlockResponseContract, AddPortalLinkedBlockRequestContract, AddPortalLinkedBlockResponseContract, AddPortalNoteBlockRequestContract, AddPortalNoteBlockResponseContract, AddPortalRecentFilesBlockRequestContract, AddPortalRecentFilesBlockResponseContract, AddPortalTaskListBlockRequestContract, AddPortalTaskListBlockResponseContract, AddPortalTextBlockRequestContract, AddPortalTimelineBlockRequestContract, AddPortalTimelineBlockResponseContract, BulkInviteToPortalRequestContract, BulkInviteToPortalResponseContract, CreatePortalFolderRequestContract, CreatePortalFolderResponseContract, CreatePortalLinkRequestContract, CreatePortalLinkResponseContract, CreatePortalPageRequestContract, CreatePortalPageResponseContract, CreatePortalPageWithNoteRequestContract, CreatePortalPageWithNoteResponseContract, CreatePortalRequestContract, CreatePortalResponseContract, DuplicatePortalItemRequestContract, DuplicatePortalItemResponseContract, DuplicatePortalRequestContract, GetPortalPageBlockCountResponseContract, globalIdInPathRequired, InvitePortalManagerRequestContract, InvitePortalManagerResponseContract, InviteToPortalRequestContract, InviteToPortalResponseContract, ListPortalAiAgentsResponseContract, ListPortalChatChannelsResponseContract, ListPortalChatUsersResponseContract, ListPortalContentResponseContract, ListPortalDatabaseBlockSourcesResponseContract, ListPortalLinkableBlocksResponseContract, orgIdInPathRequired, OrgPortalListResponseContract, PortalDetailContract, PortalTextAndMediaBlockResponseContract, PublishPortalDraftResponseContract, SearchPortalInfoBlockIconsResponseContract, SetDashboardViewReadonlyRequestContract, SetDashboardViewReadonlyResponseContract, UpdatePortalAccessRequestContract, UpdatePortalAccessResponseContract, UpdatePortalCustomCodeRequestContract, UpdatePortalCustomCodeResponseContract } from "../types";
 export declare class PortalsApi {
     private client;
     constructor(client: Client);
@@ -37,7 +37,7 @@ export declare class PortalsApi {
     }): Promise<AddPortalAppBlockResponseContract>;
     /**
      * Add a published app as a portal page (embed)
-     * Creates a new sidebar page in the portal that embeds a published Fusebase app (a flexible block with an app-feature brick). Pass productId (the product that owns the app) and appId (the app to embed) — typically the app you just built and published via the CLI. For a managed product (Customizer "Managed Products") also pass productType='managed' and productOrgId from findPublishedApps. The app's URL is resolved by the portal at render time from these ids; nothing is hard-coded. Pass parentId to nest the page under an existing folder. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Returns the page/menu-item/block ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new sidebar page in the portal that embeds a published Fusebase app (a flexible block with an app-feature brick). Pass productId (the product that owns the app) and appId (the app to embed) — typically the app you just built and published via the CLI. For a managed product (Customizer "Managed Products") also pass productType='managed' and productOrgId from findPublishedApps. The app's URL is resolved by the portal at render time from these ids; nothing is hard-coded. Pass parentId to nest the page under an existing folder, or positionType ('sidebar' default, 'top', 'footer') to place a root page in a specific menu bar. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Returns the page/menu-item/block ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     addPortalAppPage(params: {
         path: {
@@ -62,7 +62,7 @@ export declare class PortalsApi {
     }): Promise<AddPortalBlankNoteBlockResponseContract>;
     /**
      * Add a block of any palette type to a portal page
-     * Stages a single block of any supported type onto an existing portal page — the universal building block behind the customizer's 'Add new block' palette (no new page or sidebar item is created). Pass pageId (the target page node id from listPortalContent) and type. Supported types: note, content, docs, help, request, meetings, links, files-dashboard, tasks-dashboard, chats-dashboard, files-recent, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'dashboard'|'app-feature'|...}) and may carry bricks; the link cards (docs/help/request/meetings/links) and others take their fields via the free-form `properties` object (e.g. image/link). It does NOT accept type='projection' — use addPortalLinkedBlock for a Linked block. This op does NOT accept type='embed', a flexible block with template.type='timeline' or a timeline brick (use addPortalTimelineBlock), a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks. It also does NOT accept type='files-bucket': use addPortalFileUploaderBlock for File uploader blocks. It does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. It does NOT accept a flexible `form` template or a `form` brick either: use addPortalFormBlock, which owns the canonical Form block and its fields. It does NOT accept type='info': use addPortalInfoBlock, which owns the canonical Info block, its icon catalog and its destination resolution. It does NOT accept type='task-list' or a note/content block with properties.templateKey='task-list': use addPortalTaskListBlock, which creates the note and its task list. Use addPortalNoteBlock for the common note case or addPortalAppPage for an app on its own page. Note: a `content` block renames the page to its title, so leave title empty for content blocks. The block is staged in the portal's customizer draft (not published immediately); the owner reviews and publishes it. Returns the block id and the draft branch/seqs. Requires portals.write access.
+     * Stages a single block of any supported type onto an existing portal page — the universal building block behind the customizer's 'Add new block' palette (no new page or sidebar item is created). Pass pageId (the target page node id from listPortalContent) and type. Supported types: note, content, docs, help, request, meetings, links, files-dashboard, tasks-dashboard, chats-dashboard, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'dashboard'|'app-feature'|...}) and may carry bricks; the link cards (docs/help/request/meetings/links) and others take their fields via the free-form `properties` object (e.g. image/link). It does NOT accept type='projection' — use addPortalLinkedBlock for a Linked block. This op does NOT accept type='embed', a flexible block with template.type='timeline' or a timeline brick (use addPortalTimelineBlock), a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock), a flexible block with template.type='integration' or an integration brick (use addPortalDynamicTableBlock), a flexible block with template.type='diagram' or a diagram brick (use addPortalBpmnDiagramBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks. It also does NOT accept type='files-bucket': use addPortalFileUploaderBlock for File uploader blocks. It does NOT accept type='files-recent': use addPortalRecentFilesBlock for Recent files blocks. It does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. It does NOT accept a flexible `form` template or a `form` brick either: use addPortalFormBlock, which owns the canonical Form block and its fields. It does NOT accept type='info': use addPortalInfoBlock, which owns the canonical Info block, its icon catalog and its destination resolution. It does NOT accept type='task-list' or a note/content block with properties.templateKey='task-list': use addPortalTaskListBlock, which creates the note and its task list. Use addPortalNoteBlock for the common note case or addPortalAppPage for an app on its own page. Note: a `content` block renames the page to its title, so leave title empty for content blocks. The block is staged in the portal's customizer draft (not published immediately); the owner reviews and publishes it. Returns the block id and the draft branch/seqs. Requires portals.write access.
      */
     addPortalBlock(params: {
         path: {
@@ -72,6 +72,19 @@ export declare class PortalsApi {
         headers?: Record<string, string>;
         body: AddPortalBlockRequestContract;
     }): Promise<AddPortalBlockResponseContract>;
+    /**
+     * Add a BPMN Diagram block to a portal page
+     * Stages one Customizer-compatible BPMN Diagram block on an EXISTING portal page — the programmatic equivalent of the customizer's Experimental "BPMN Diagram" tile. It creates exactly one flexible block with a single BPMN diagram brick; no page, sidebar item or menu icon change comes with it. The diagram is created EMPTY, exactly as the Customizer creates it: the process itself is drawn or imported from a `.bpmn` file in Portal Customizer. BPMN XML, `.bpmn` file uploads, task ids, persisted data/details and links for BPMN Task elements are rejected. This is not a Mermaid diagram, a generic flowchart, a Timeline or an image. The body may be empty, which reproduces the Customizer default: the title "BPMN Diagram", a 500px canvas, a blank backdrop with the title shown, width 6 and automatic height. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `content.diagramHeight` is the BPMN canvas height in pixels (integer 150-5000, default 500) and is distinct from the block Layout height. `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    addPortalBpmnDiagramBlock(params: {
+        path: {
+            orgId: orgIdInPathRequired;
+            portalId: globalIdInPathRequired;
+            pageId: globalIdInPathRequired;
+        };
+        headers?: Record<string, string>;
+        body: AddPortalBpmnDiagramBlockRequestContract;
+    }): Promise<AddPortalBpmnDiagramBlockResponseContract>;
     /**
      * Add a Card block to a portal page
      * Stages one Customizer-compatible Card on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Card" tile. It creates exactly one flexible block with the five canonical bricks (Image, Heading, Description, Button, Destination URL); no page, sidebar item or media asset is created. `view` is the Card Type: `top-image`, `left-image`, `right-image` or `fill-image` (default `top-image`; `fill-image` defaults the text to white). `content` configures the bricks: `image.visible` only — the Card always uses the built-in template image and an `src`/URL/asset id/upload is rejected —, `heading` and `description` (plain text plus one palette colour token such as `cyan-700`, size `s`/`m`/`l`/`xl`, a unique set of `bold`/`italic`/`underline`/`lineThrough` styles and alignment), `button` (plain label sent as `button.text` — there is no `label` field and sending one is rejected — with no dynamic variables) and `destination`. `visible` defaults to `true`, so a visible item does NOT need `visible: true`: send `content.button: {text: "Open"}` to set an enabled Button label. Any of Image, Heading, Description and Button can be hidden with `visible: false`, which then must be the item's only field. `destination` is shared by the whole Card and its Button: an exact `pageId` of a page in THIS portal, an absolute https URL, an email address, or `null` for no link — a raw DynamicLink, `javascript:`/`data:` URL or caller-supplied internal title/targetId is rejected, and the link target (new tab) is not configurable. `appearance` is optional; omitting it keeps the Card's canonical bare wrapper, and a `custom` backdrop takes a colour, gradient or one of the five preset background images (`azure`, `mira`, `solis`, `serenity`, `glow`). `layout` sets Customizer Width (2-6, default 3) and Height (Auto by default, a manual value is at least 50px). HTML, Markdown, CSS, Tailwind classes, a wrapper title and raw bricks are not accepted. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -163,6 +176,19 @@ export declare class PortalsApi {
         headers?: Record<string, string>;
         body: AddPortalDatabaseBlockRequestContract;
     }): Promise<AddPortalDatabaseBlockResponseContract>;
+    /**
+     * Add a Dynamic Table block to a portal page
+     * Stages one Customizer-compatible Dynamic Table block on an EXISTING portal page — the programmatic equivalent of the customizer's Dynamic "Table" tile. It creates exactly one flexible block with a single integration brick; no page, sidebar item or OAuth connection is created. This is NOT addPortalDatabaseBlock: Database shows a Fusebase Database table/view, while Dynamic Table reads records from a HubSpot, Asana or monday.com connection. The block is created UNCONFIGURED, exactly as the Customizer creates it before a Data source is picked: the response carries `configured: false` and the Data source, table fields, filters, sorting and pagination are still chosen in Portal Customizer. `tokenId`, provider source ids, mappings, filters, order, pagination, template and bricks are rejected. The body may be empty, which reproduces the Customizer default: the title "Dynamic Table", a blank backdrop with the title shown, width 6 and automatic height. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    addPortalDynamicTableBlock(params: {
+        path: {
+            orgId: orgIdInPathRequired;
+            portalId: globalIdInPathRequired;
+            pageId: globalIdInPathRequired;
+        };
+        headers?: Record<string, string>;
+        body: AddPortalDynamicTableBlockRequestContract;
+    }): Promise<AddPortalDynamicTableBlockResponseContract>;
     /**
      * Add an Embeds & Integrations block to a portal page
      * Stages one Customizer-compatible Embed block on an EXISTING portal page — the programmatic equivalent of the customizer's "Embeds & Integrations" action. No new page and no sidebar menu item is created. embedType is one of the 11 chooser variants (custom, youtube, google-drive, ms-doc, calendly, hubspot, airtable, loom, data-studio, figma, miro). For `custom` pass `content` (URL or embed code) and NOT `url`; for every named variant pass `url` and NOT `content` — the service builds the canonical iframe. hubspot here is an iframe Embed block, not a Flexible Block integration brick. For a published page resolve pageId from listPortalContent; for a page created earlier in the active draft use the pageId that operation returned. The block is staged in the portal's customizer draft (not published immediately). Returns the block id and the draft branch/seqs. Requires portals.write access.
@@ -292,6 +318,19 @@ export declare class PortalsApi {
         headers?: Record<string, string>;
         body: AddPortalNoteBlockRequestContract;
     }): Promise<AddPortalNoteBlockResponseContract>;
+    /**
+     * Add a Recent files block to a portal page
+     * Stages one Customizer-compatible Recent files block on an EXISTING portal page — the programmatic equivalent of the customizer's File management "Recent files" tile. The block lists the five most recently created files of the whole portal or of exactly one portal page; no page, sidebar item, file or bucket is created and no file access is widened (the File Manager applies the viewer's own access at render time). The body may be empty, which reproduces the Customizer default: the title "Recent files" scoped to the entire portal. `title` is at most 100 characters. `source` is either `{type:'entirePortal'}` or `{type:'portalPage', pageId}` with an exact page id of THIS portal — a page title, path, URL, file or bucket id is rejected. `layout` sets Width (3-6, default 3) and Height (Auto by default, a manual value is at least 50px). Sort order (createdAt descending), the item count of 5, the offset, raw query/link data, Appearance and Rows are fixed and not configurable. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    addPortalRecentFilesBlock(params: {
+        path: {
+            orgId: orgIdInPathRequired;
+            portalId: globalIdInPathRequired;
+            pageId: globalIdInPathRequired;
+        };
+        headers?: Record<string, string>;
+        body: AddPortalRecentFilesBlockRequestContract;
+    }): Promise<AddPortalRecentFilesBlockResponseContract>;
     /**
      * Add a task list as a block to a portal page
      * Creates a new Fusebase note, shares it into the portal, initialises a task list inside it and adds the note as a block to an existing portal page — the programmatic equivalent of the customizer's Project management "Task list" tile. No new page and no sidebar menu item is created. For a published page resolve pageId from listPortalContent; for a page created earlier in the active draft use the pageId that operation returned. Optional body: title (block and task list title, at most 100 characters, default "Task list") and layout (colspan 3-6, default 6; height in pixels or null for Auto, default null). The list starts empty — tasks are added by portal users, not by this operation, and an existing task list cannot be attached. Use addPortalBlankNoteBlock when an empty note is wanted instead. The block is appended after the last block of the page body and is staged in the portal's customizer draft (not published immediately). Returns the note/task list/block ids and the draft branch/seqs. Requires portals.write access.
@@ -356,7 +395,7 @@ export declare class PortalsApi {
     }): Promise<CreatePortalResponseContract>;
     /**
      * Create a root folder in a portal
-     * Creates a new empty root folder (a portalSection) in the portal's sidebar navigation. The folder is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending folder, and publishes it. Returns the created folder/page ids, its url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new empty root folder (a portalSection) in a portal menu bar. Pass positionType to choose the bar: 'sidebar' (default), 'top' (topbar), or 'footer'. The folder is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending folder, and publishes it. Returns the created folder/page ids, its url, and the draft branch/seqs. Requires portals.write access.
      */
     createPortalFolder(params: {
         path: {
@@ -366,9 +405,21 @@ export declare class PortalsApi {
         headers?: Record<string, string>;
         body: CreatePortalFolderRequestContract;
     }): Promise<CreatePortalFolderResponseContract>;
+    /**
+     * Create an external link menu item in a portal
+     * Creates a menu item that opens an external URL (no page is created). Use it to build a topbar or footer nav of external links (e.g. Chat / Case Studies / Contact). Pass name and url; positionType chooses the bar: 'sidebar' (default), 'top' (topbar), or 'footer'. Optionally pass icon, openInNewTab (default true), and parentId to nest under a folder. The link is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending link, and publishes it. Returns the created menu-item id and the draft branch/seqs. Requires portals.write access.
+     */
+    createPortalLink(params: {
+        path: {
+            orgId: orgIdInPathRequired;
+            portalId: globalIdInPathRequired;
+        };
+        headers?: Record<string, string>;
+        body: CreatePortalLinkRequestContract;
+    }): Promise<CreatePortalLinkResponseContract>;
     /**
      * Create an empty portal page
-     * Creates a new EMPTY sidebar page in the portal — a page node plus its sidebar menu item, with no Fusebase note and no block. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing published or active-draft folder. The returned pageId can immediately be passed to semantic block operations to add content before publishing. Use createPortalPageWithNote instead when a page backed by a new Fusebase note is wanted. Returns the page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new EMPTY page in the portal — a page node plus its menu item, with no Fusebase note and no block. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass positionType ('sidebar' default, 'top' or 'footer') to choose the menu bar. Pass parentId to nest the page under an existing published or active-draft folder. The returned pageId can immediately be passed to semantic block operations to add content before publishing. Use createPortalPageWithNote instead when a page backed by a new Fusebase note is wanted. Returns the page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     createPortalPage(params: {
         path: {
@@ -380,7 +431,7 @@ export declare class PortalsApi {
     }): Promise<CreatePortalPageResponseContract>;
     /**
      * Create a portal page backed by a Fusebase note
-     * Creates a new sidebar page in the portal backed by a freshly created Fusebase note. The note is created in the portal's workspace and shared into the portal; optional initial text or html can be appended to it. The page (page node + note menu item + note content block) is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing folder. Returns the note/page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new sidebar page in the portal backed by a freshly created Fusebase note. The note is created in the portal's workspace and shared into the portal; optional initial text or html can be appended to it. The page (page node + note menu item + note content block) is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing folder, or positionType ('sidebar' default, 'top', 'footer') to place a root page in a specific menu bar. Returns the note/page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     createPortalPageWithNote(params: {
         path: {

package/dist/apis/PortalsApi.js

@@ -43,7 +43,7 @@ class PortalsApi {
     }
     /**
      * Add a published app as a portal page (embed)
-     * Creates a new sidebar page in the portal that embeds a published Fusebase app (a flexible block with an app-feature brick). Pass productId (the product that owns the app) and appId (the app to embed) — typically the app you just built and published via the CLI. For a managed product (Customizer "Managed Products") also pass productType='managed' and productOrgId from findPublishedApps. The app's URL is resolved by the portal at render time from these ids; nothing is hard-coded. Pass parentId to nest the page under an existing folder. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Returns the page/menu-item/block ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new sidebar page in the portal that embeds a published Fusebase app (a flexible block with an app-feature brick). Pass productId (the product that owns the app) and appId (the app to embed) — typically the app you just built and published via the CLI. For a managed product (Customizer "Managed Products") also pass productType='managed' and productOrgId from findPublishedApps. The app's URL is resolved by the portal at render time from these ids; nothing is hard-coded. Pass parentId to nest the page under an existing folder, or positionType ('sidebar' default, 'top', 'footer') to place a root page in a specific menu bar. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Returns the page/menu-item/block ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     async addPortalAppPage(params) {
         return this.client.request({
@@ -73,7 +73,7 @@ class PortalsApi {
     }
     /**
      * Add a block of any palette type to a portal page
-     * Stages a single block of any supported type onto an existing portal page — the universal building block behind the customizer's 'Add new block' palette (no new page or sidebar item is created). Pass pageId (the target page node id from listPortalContent) and type. Supported types: note, content, docs, help, request, meetings, links, files-dashboard, tasks-dashboard, chats-dashboard, files-recent, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'dashboard'|'app-feature'|...}) and may carry bricks; the link cards (docs/help/request/meetings/links) and others take their fields via the free-form `properties` object (e.g. image/link). It does NOT accept type='projection' — use addPortalLinkedBlock for a Linked block. This op does NOT accept type='embed', a flexible block with template.type='timeline' or a timeline brick (use addPortalTimelineBlock), a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks. It also does NOT accept type='files-bucket': use addPortalFileUploaderBlock for File uploader blocks. It does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. It does NOT accept a flexible `form` template or a `form` brick either: use addPortalFormBlock, which owns the canonical Form block and its fields. It does NOT accept type='info': use addPortalInfoBlock, which owns the canonical Info block, its icon catalog and its destination resolution. It does NOT accept type='task-list' or a note/content block with properties.templateKey='task-list': use addPortalTaskListBlock, which creates the note and its task list. Use addPortalNoteBlock for the common note case or addPortalAppPage for an app on its own page. Note: a `content` block renames the page to its title, so leave title empty for content blocks. The block is staged in the portal's customizer draft (not published immediately); the owner reviews and publishes it. Returns the block id and the draft branch/seqs. Requires portals.write access.
+     * Stages a single block of any supported type onto an existing portal page — the universal building block behind the customizer's 'Add new block' palette (no new page or sidebar item is created). Pass pageId (the target page node id from listPortalContent) and type. Supported types: note, content, docs, help, request, meetings, links, files-dashboard, tasks-dashboard, chats-dashboard, flexible. Type-specific fields: note/content require noteId; flexible requires template (e.g. {type:'text'|'image'|'title'|'dashboard'|'app-feature'|...}) and may carry bricks; the link cards (docs/help/request/meetings/links) and others take their fields via the free-form `properties` object (e.g. image/link). It does NOT accept type='projection' — use addPortalLinkedBlock for a Linked block. This op does NOT accept type='embed', a flexible block with template.type='timeline' or a timeline brick (use addPortalTimelineBlock), a flexible block with template.type='dashboard' or a dashboard brick (use addPortalDatabaseBlock), a flexible block with template.type='integration' or an integration brick (use addPortalDynamicTableBlock), a flexible block with template.type='diagram' or a diagram brick (use addPortalBpmnDiagramBlock) or type='chat' — use addPortalEmbedBlock for Embed blocks and addPortalChatBlock for Chat blocks. It also does NOT accept type='files-bucket': use addPortalFileUploaderBlock for File uploader blocks. It does NOT accept type='files-recent': use addPortalRecentFilesBlock for Recent files blocks. It does NOT accept a flexible ai-agent template or an ai-agent brick: use addPortalAiAgentBlock, which binds the agent to the caller. It does NOT accept a flexible `form` template or a `form` brick either: use addPortalFormBlock, which owns the canonical Form block and its fields. It does NOT accept type='info': use addPortalInfoBlock, which owns the canonical Info block, its icon catalog and its destination resolution. It does NOT accept type='task-list' or a note/content block with properties.templateKey='task-list': use addPortalTaskListBlock, which creates the note and its task list. Use addPortalNoteBlock for the common note case or addPortalAppPage for an app on its own page. Note: a `content` block renames the page to its title, so leave title empty for content blocks. The block is staged in the portal's customizer draft (not published immediately); the owner reviews and publishes it. Returns the block id and the draft branch/seqs. Requires portals.write access.
      */
     async addPortalBlock(params) {
         return this.client.request({
@@ -86,6 +86,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a BPMN Diagram block to a portal page
+     * Stages one Customizer-compatible BPMN Diagram block on an EXISTING portal page — the programmatic equivalent of the customizer's Experimental "BPMN Diagram" tile. It creates exactly one flexible block with a single BPMN diagram brick; no page, sidebar item or menu icon change comes with it. The diagram is created EMPTY, exactly as the Customizer creates it: the process itself is drawn or imported from a `.bpmn` file in Portal Customizer. BPMN XML, `.bpmn` file uploads, task ids, persisted data/details and links for BPMN Task elements are rejected. This is not a Mermaid diagram, a generic flowchart, a Timeline or an image. The body may be empty, which reproduces the Customizer default: the title "BPMN Diagram", a 500px canvas, a blank backdrop with the title shown, width 6 and automatic height. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `content.diagramHeight` is the BPMN canvas height in pixels (integer 150-5000, default 500) and is distinct from the block Layout height. `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalBpmnDiagramBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/bpmn-diagram",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalBpmnDiagramBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a Card block to a portal page
      * Stages one Customizer-compatible Card on an EXISTING portal page — the programmatic equivalent of the customizer's Content display "Card" tile. It creates exactly one flexible block with the five canonical bricks (Image, Heading, Description, Button, Destination URL); no page, sidebar item or media asset is created. `view` is the Card Type: `top-image`, `left-image`, `right-image` or `fill-image` (default `top-image`; `fill-image` defaults the text to white). `content` configures the bricks: `image.visible` only — the Card always uses the built-in template image and an `src`/URL/asset id/upload is rejected —, `heading` and `description` (plain text plus one palette colour token such as `cyan-700`, size `s`/`m`/`l`/`xl`, a unique set of `bold`/`italic`/`underline`/`lineThrough` styles and alignment), `button` (plain label sent as `button.text` — there is no `label` field and sending one is rejected — with no dynamic variables) and `destination`. `visible` defaults to `true`, so a visible item does NOT need `visible: true`: send `content.button: {text: "Open"}` to set an enabled Button label. Any of Image, Heading, Description and Button can be hidden with `visible: false`, which then must be the item's only field. `destination` is shared by the whole Card and its Button: an exact `pageId` of a page in THIS portal, an absolute https URL, an email address, or `null` for no link — a raw DynamicLink, `javascript:`/`data:` URL or caller-supplied internal title/targetId is rejected, and the link target (new tab) is not configurable. `appearance` is optional; omitting it keeps the Card's canonical bare wrapper, and a `custom` backdrop takes a colour, gradient or one of the five preset background images (`azure`, `mira`, `solis`, `serenity`, `glow`). `layout` sets Customizer Width (2-6, default 3) and Height (Auto by default, a manual value is at least 50px). HTML, Markdown, CSS, Tailwind classes, a wrapper title and raw bricks are not accepted. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
@@ -191,6 +206,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Dynamic Table block to a portal page
+     * Stages one Customizer-compatible Dynamic Table block on an EXISTING portal page — the programmatic equivalent of the customizer's Dynamic "Table" tile. It creates exactly one flexible block with a single integration brick; no page, sidebar item or OAuth connection is created. This is NOT addPortalDatabaseBlock: Database shows a Fusebase Database table/view, while Dynamic Table reads records from a HubSpot, Asana or monday.com connection. The block is created UNCONFIGURED, exactly as the Customizer creates it before a Data source is picked: the response carries `configured: false` and the Data source, table fields, filters, sorting and pagination are still chosen in Portal Customizer. `tokenId`, provider source ids, mappings, filters, order, pagination, template and bricks are rejected. The body may be empty, which reproduces the Customizer default: the title "Dynamic Table", a blank backdrop with the title shown, width 6 and automatic height. `title` is the block title (plain text, only the `{{ClientName}}` and `{{ClientLastName}}` variables). `appearance` sets Customizer Backdrop `none`, `blank` or `custom`; a custom backdrop takes a background, padding (default `s`) and `showTitle` (default true). `layout` sets Width (2-6, default 6) and Height (Auto by default, a manual value is at least 50px). The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalDynamicTableBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/dynamic-table",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalDynamicTableBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add an Embeds & Integrations block to a portal page
      * Stages one Customizer-compatible Embed block on an EXISTING portal page — the programmatic equivalent of the customizer's "Embeds & Integrations" action. No new page and no sidebar menu item is created. embedType is one of the 11 chooser variants (custom, youtube, google-drive, ms-doc, calendly, hubspot, airtable, loom, data-studio, figma, miro). For `custom` pass `content` (URL or embed code) and NOT `url`; for every named variant pass `url` and NOT `content` — the service builds the canonical iframe. hubspot here is an iframe Embed block, not a Flexible Block integration brick. For a published page resolve pageId from listPortalContent; for a page created earlier in the active draft use the pageId that operation returned. The block is staged in the portal's customizer draft (not published immediately). Returns the block id and the draft branch/seqs. Requires portals.write access.
@@ -341,6 +371,21 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Add a Recent files block to a portal page
+     * Stages one Customizer-compatible Recent files block on an EXISTING portal page — the programmatic equivalent of the customizer's File management "Recent files" tile. The block lists the five most recently created files of the whole portal or of exactly one portal page; no page, sidebar item, file or bucket is created and no file access is widened (the File Manager applies the viewer's own access at render time). The body may be empty, which reproduces the Customizer default: the title "Recent files" scoped to the entire portal. `title` is at most 100 characters. `source` is either `{type:'entirePortal'}` or `{type:'portalPage', pageId}` with an exact page id of THIS portal — a page title, path, URL, file or bucket id is rejected. `layout` sets Width (3-6, default 3) and Height (Auto by default, a manual value is at least 50px). Sort order (createdAt descending), the item count of 5, the offset, raw query/link data, Appearance and Rows are fixed and not configurable. The block is staged in the portal's customizer draft (not published immediately). Requires portals.write access.
+     */
+    async addPortalRecentFilesBlock(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/pages/:pageId/blocks/recent-files",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "addPortalRecentFilesBlock",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Add a task list as a block to a portal page
      * Creates a new Fusebase note, shares it into the portal, initialises a task list inside it and adds the note as a block to an existing portal page — the programmatic equivalent of the customizer's Project management "Task list" tile. No new page and no sidebar menu item is created. For a published page resolve pageId from listPortalContent; for a page created earlier in the active draft use the pageId that operation returned. Optional body: title (block and task list title, at most 100 characters, default "Task list") and layout (colspan 3-6, default 6; height in pixels or null for Auto, default null). The list starts empty — tasks are added by portal users, not by this operation, and an existing task list cannot be attached. Use addPortalBlankNoteBlock when an empty note is wanted instead. The block is appended after the last block of the page body and is staged in the portal's customizer draft (not published immediately). Returns the note/task list/block ids and the draft branch/seqs. Requires portals.write access.
@@ -418,7 +463,7 @@ class PortalsApi {
     }
     /**
      * Create a root folder in a portal
-     * Creates a new empty root folder (a portalSection) in the portal's sidebar navigation. The folder is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending folder, and publishes it. Returns the created folder/page ids, its url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new empty root folder (a portalSection) in a portal menu bar. Pass positionType to choose the bar: 'sidebar' (default), 'top' (topbar), or 'footer'. The folder is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending folder, and publishes it. Returns the created folder/page ids, its url, and the draft branch/seqs. Requires portals.write access.
      */
     async createPortalFolder(params) {
         return this.client.request({
@@ -431,9 +476,24 @@ class PortalsApi {
             expectedContentType: "application/json",
         });
     }
+    /**
+     * Create an external link menu item in a portal
+     * Creates a menu item that opens an external URL (no page is created). Use it to build a topbar or footer nav of external links (e.g. Chat / Case Studies / Contact). Pass name and url; positionType chooses the bar: 'sidebar' (default), 'top' (topbar), or 'footer'. Optionally pass icon, openInNewTab (default true), and parentId to nest under a folder. The link is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending link, and publishes it. Returns the created menu-item id and the draft branch/seqs. Requires portals.write access.
+     */
+    async createPortalLink(params) {
+        return this.client.request({
+            method: "POST",
+            path: "/:orgId/portals/:portalId/links",
+            pathParams: params.path,
+            headers: params.headers,
+            body: params.body,
+            opId: "createPortalLink",
+            expectedContentType: "application/json",
+        });
+    }
     /**
      * Create an empty portal page
-     * Creates a new EMPTY sidebar page in the portal — a page node plus its sidebar menu item, with no Fusebase note and no block. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing published or active-draft folder. The returned pageId can immediately be passed to semantic block operations to add content before publishing. Use createPortalPageWithNote instead when a page backed by a new Fusebase note is wanted. Returns the page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new EMPTY page in the portal — a page node plus its menu item, with no Fusebase note and no block. The page is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass positionType ('sidebar' default, 'top' or 'footer') to choose the menu bar. Pass parentId to nest the page under an existing published or active-draft folder. The returned pageId can immediately be passed to semantic block operations to add content before publishing. Use createPortalPageWithNote instead when a page backed by a new Fusebase note is wanted. Returns the page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     async createPortalPage(params) {
         return this.client.request({
@@ -448,7 +508,7 @@ class PortalsApi {
     }
     /**
      * Create a portal page backed by a Fusebase note
-     * Creates a new sidebar page in the portal backed by a freshly created Fusebase note. The note is created in the portal's workspace and shared into the portal; optional initial text or html can be appended to it. The page (page node + note menu item + note content block) is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing folder. Returns the note/page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
+     * Creates a new sidebar page in the portal backed by a freshly created Fusebase note. The note is created in the portal's workspace and shared into the portal; optional initial text or html can be appended to it. The page (page node + note menu item + note content block) is staged in the portal's customizer draft (not published immediately): the portal owner opens the customizer, reviews the pending page, and publishes it. Pass parentId to nest the page under an existing folder, or positionType ('sidebar' default, 'top', 'footer') to place a root page in a specific menu bar. Returns the note/page/menu-item ids, the page url, and the draft branch/seqs. Requires portals.write access.
      */
     async createPortalPageWithNote(params) {
         return this.client.request({

package/dist/types/portals/portals.d.ts

@@ -54,6 +54,48 @@ export interface CreatePortalFolderRequestContract {
     name: string;
     /** Optional icon key for the folder (default: "folder"). */
     icon?: string;
+    /**
+     * Menu bar to place the folder in: "sidebar" (default), "top" (topbar), or
+     * "footer".
+     */
+    positionType?: PortalContentPositionType;
+}
+export interface CreatePortalLinkRequestContract {
+    /**
+     * Display name of the link menu item.
+     * @maxLength 100
+     */
+    name: string;
+    /** Absolute http(s) URL the link opens (e.g. "https://example.com/contact"). */
+    url: string;
+    /**
+     * Menu bar to place the link in: "sidebar" (default), "top" (topbar), or
+     * "footer". Use "top" for a topbar nav (e.g. Chat / Case Studies / Contact).
+     * Ignored when `parentId` is set (the link inherits the parent's bar).
+     */
+    positionType?: PortalContentPositionType;
+    /** Optional icon key for the link (default: "custom_link"). */
+    icon?: string;
+    /** Whether the link opens in a new tab (default: true). */
+    openInNewTab?: boolean;
+    /**
+     * Optional id of an existing folder menu item to nest the link under.
+     * When omitted the link is added at the root of its menu bar.
+     */
+    parentId?: string;
+}
+export interface CreatePortalLinkResponseContract {
+    /** Id of the created link menu item. */
+    menuItemId: string;
+    /** Draft branch the change was staged on. */
+    branchId: string;
+    /** Sequence numbers assigned to the staged change events (addMenuItem). */
+    seqs: number[];
+    /**
+     * Always true: the link is staged in the portal's customizer draft, not yet
+     * live. The portal owner reviews and publishes it from the customizer.
+     */
+    staged: boolean;
 }
 export interface CreatePortalFolderResponseContract {
     /** Id of the created folder (the portalSection menu item). */
@@ -96,6 +138,11 @@ export interface CreatePortalPageRequestContract {
      * created at the portal root.
      */
     parentId?: string;
+    /**
+     * Menu bar to place the page in: "sidebar" (default), "top" (topbar), or
+     * "footer". Ignored when `parentId` is set (the page inherits the parent's bar).
+     */
+    positionType?: PortalContentPositionType;
 }
 export interface CreatePortalPageResponseContract {
     /** Id of the created sidebar menu item. */
@@ -131,6 +178,11 @@ export interface CreatePortalPageWithNoteRequestContract {
     content?: string;
     /** Content format used with `content`. Defaults to `text`. */
     format?: WorkspaceNoteContentFormatContract;
+    /**
+     * Menu bar to place the page in: "sidebar" (default), "top" (topbar), or
+     * "footer". Ignored when `parentId` is set (the page inherits the parent's bar).
+     */
+    positionType?: PortalContentPositionType;
 }
 export interface CreatePortalPageWithNoteResponseContract {
     /** Global id of the created Fusebase note backing the page. */
@@ -772,6 +824,165 @@ export interface AddPortalCountdownBlockResponseContract {
     /** Always true: the block is staged in the customizer draft, not yet live. */
     staged: boolean;
 }
+export interface PortalBpmnDiagramContentContract {
+    /**
+     * Height in pixels of the BPMN canvas INSIDE the block — the Customizer's
+     * "Diagram height" field. This is not the block's Layout height.
+     * Default: 500.
+     * @minimum 150
+     * @maximum 5000
+     */
+    diagramHeight?: number;
+}
+/**
+ * Customizer Appearance section of a BPMN Diagram. Omitting `appearance` keeps
+ * the factory `blank` wrapper with the block title shown.
+ */
+export type PortalBpmnDiagramAppearanceContract = {
+    backdrop: "none" | "blank";
+} | {
+    backdrop: "custom";
+    background: PortalCardBackgroundContract;
+    /** Default: `s`. */
+    padding?: "none" | "s" | "m" | "l";
+    /** Default: true. */
+    showTitle?: boolean;
+};
+/** Customizer Layout section of a BPMN Diagram. */
+export interface PortalBpmnDiagramLayoutContract {
+    /** Customizer Width. Default: 6. */
+    colspan?: 2 | 3 | 4 | 5 | 6;
+    /**
+     * Customizer Height: null = Auto; a manual value is at least 50px. Default: null.
+     * @minimum 50
+     */
+    height?: number | null;
+}
+export interface AddPortalBpmnDiagramBlockRequestContract {
+    /**
+     * Block title shown above the diagram. Plain text; only `{{ClientName}}` and
+     * `{{ClientLastName}}` are variables. Default: `BPMN Diagram`.
+     * @minLength 1
+     * @maxLength 100
+     */
+    title?: string;
+    content?: PortalBpmnDiagramContentContract;
+    /** Omitted keeps the canonical blank backdrop with the title shown. */
+    appearance?: PortalBpmnDiagramAppearanceContract;
+    /** Default: width 6 columns and automatic height. */
+    layout?: PortalBpmnDiagramLayoutContract;
+}
+export interface AddPortalBpmnDiagramBlockResponseContract {
+    /** Id of the created block. */
+    blockId: string;
+    /** Id of the page the block was added to. */
+    pageId: string;
+    /** Draft branch the change was staged on. */
+    branchId: string;
+    /** Sequence numbers assigned to the staged change events (addBlock). */
+    seqs: number[];
+    /** Always true: the block is staged in the customizer draft, not yet live. */
+    staged: boolean;
+}
+/**
+ * Customizer Appearance section of a Dynamic Table. Omitting `appearance` keeps
+ * the factory `blank` wrapper with the block title shown.
+ */
+export type PortalDynamicTableAppearanceContract = {
+    backdrop: "none" | "blank";
+} | {
+    backdrop: "custom";
+    background: PortalCardBackgroundContract;
+    /** Default: `s`. */
+    padding?: "none" | "s" | "m" | "l";
+    /** Default: true. */
+    showTitle?: boolean;
+};
+/** Customizer Layout section of a Dynamic Table. */
+export interface PortalDynamicTableLayoutContract {
+    /** Customizer Width. Default: 6. */
+    colspan?: 2 | 3 | 4 | 5 | 6;
+    /**
+     * Customizer Height: null = Auto; a manual value is at least 50px. Default: null.
+     * @minimum 50
+     */
+    height?: number | null;
+}
+export interface AddPortalDynamicTableBlockRequestContract {
+    /**
+     * Block title shown above the table. Plain text; only `{{ClientName}}` and
+     * `{{ClientLastName}}` are variables. Default: `Dynamic Table`.
+     * @minLength 1
+     * @maxLength 100
+     */
+    title?: string;
+    /** Omitted keeps the canonical blank backdrop with the title shown. */
+    appearance?: PortalDynamicTableAppearanceContract;
+    /** Default: width 6 columns and automatic height. */
+    layout?: PortalDynamicTableLayoutContract;
+}
+export interface AddPortalDynamicTableBlockResponseContract {
+    /** Id of the created block. */
+    blockId: string;
+    /** Id of the page the block was added to. */
+    pageId: string;
+    /** Draft branch the change was staged on. */
+    branchId: string;
+    /** Sequence numbers assigned to the staged change events (addBlock). */
+    seqs: number[];
+    /** Always true: the block is staged in the customizer draft, not yet live. */
+    staged: boolean;
+    /**
+     * Always false: the block is the unconfigured shell the Customizer creates
+     * before a Data source is picked. The OAuth connection, provider source and
+     * table fields are still chosen in Portal Customizer.
+     */
+    configured: boolean;
+}
+/**
+ * Data scope of a Recent files block: the whole portal, or exactly one of its
+ * pages. `pageId` belongs to `portalPage` only.
+ */
+export type PortalRecentFilesSourceContract = {
+    type: "entirePortal";
+} | {
+    type: "portalPage";
+    pageId: string;
+};
+/** Customizer Layout section of a Recent files block. */
+export interface PortalRecentFilesLayoutContract {
+    /** Customizer Width. Default: 3. */
+    colspan?: 3 | 4 | 5 | 6;
+    /**
+     * Customizer Height: null = Auto; a manual value is at least 50px. Default: null.
+     * @minimum 50
+     */
+    height?: number | null;
+}
+export interface AddPortalRecentFilesBlockRequestContract {
+    /**
+     * Block title shown above the file list. Plain text. Default: `Recent files`.
+     * @minLength 1
+     * @maxLength 100
+     */
+    title?: string;
+    /** Default: the entire portal. */
+    source?: PortalRecentFilesSourceContract;
+    /** Default: width 3 columns and automatic height. */
+    layout?: PortalRecentFilesLayoutContract;
+}
+export interface AddPortalRecentFilesBlockResponseContract {
+    /** Id of the created block. */
+    blockId: string;
+    /** Id of the page the block was added to. */
+    pageId: string;
+    /** Draft branch the change was staged on. */
+    branchId: string;
+    /** Sequence numbers assigned to the staged change events (addBlock). */
+    seqs: number[];
+    /** Always true: the block is staged in the customizer draft, not yet live. */
+    staged: boolean;
+}
 /** One block a Linked block may point at. */
 export interface PortalLinkableBlockContract {
     /** Exact id to send as `source.blockId`. Never invent one. */
@@ -1656,7 +1867,7 @@ export interface ListPortalChatUsersResponseContract {
  * Any other value is rejected with 400 (the reducer throws on unknown types,
  * which would otherwise fail the whole draft at publish time).
  */
-export type PortalBlockType = "note" | "content" | "docs" | "help" | "request" | "meetings" | "links" | "files-dashboard" | "tasks-dashboard" | "chats-dashboard" | "files-recent" | "flexible";
+export type PortalBlockType = "note" | "content" | "docs" | "help" | "request" | "meetings" | "links" | "files-dashboard" | "tasks-dashboard" | "chats-dashboard" | "flexible";
 export interface AddPortalBlockRequestContract {
     /** Id of the existing portal page node to add the block to. */
     pageId: string;
@@ -1731,6 +1942,11 @@ export interface AddPortalAppPageRequestContract {
     parentId?: string;
     /** Optional icon key for the menu item (default: "note"). */
     icon?: string;
+    /**
+     * Menu bar to place the page in: "sidebar" (default), "top" (topbar), or
+     * "footer". Ignored when `parentId` is set (the page inherits the parent's bar).
+     */
+    positionType?: PortalContentPositionType;
 }
 export interface AddPortalAppPageResponseContract {
     /** Id of the created portal page node hosting the app embed. */
@@ -2076,6 +2292,20 @@ export declare const PortalCountdownAppearanceContract: {
     readonly Blank: "blank";
     readonly Custom: "custom";
 };
+export declare const PortalBpmnDiagramAppearanceContract: {
+    readonly None: "none";
+    readonly Blank: "blank";
+    readonly Custom: "custom";
+};
+export declare const PortalDynamicTableAppearanceContract: {
+    readonly None: "none";
+    readonly Blank: "blank";
+    readonly Custom: "custom";
+};
+export declare const PortalRecentFilesSourceContract: {
+    readonly Entireportal: "entirePortal";
+    readonly Portalpage: "portalPage";
+};
 export declare const PortalFormAppearanceContract: {
     readonly None: "none";
     readonly Blank: "blank";

package/dist/types/portals/portals.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PortalTimelineAppearanceContract = exports.PortalTimelineViewContract = exports.PortalCustomWidgetAppearanceContract = exports.PortalCustomWidgetBrickContract = exports.PortalCustomWidgetDestinationContract = exports.PortalInfoDestinationContract = exports.PortalInfoImageContract = exports.PortalCardGroupAppearanceContract = exports.PortalCardGroupImageContract = exports.PortalFormFieldWidthContract = exports.PortalFormFieldTypeContract = exports.PortalFormAppearanceContract = exports.PortalCountdownAppearanceContract = exports.PortalCardDestinationContract = exports.PortalCardAppearanceContract = exports.PortalCardViewContract = exports.PortalCardBackgroundContract = exports.PortalFlexibleTextAppearanceContract = exports.PortalTextBackgroundContract = exports.PortalDatabaseBlockAppearanceContract = exports.PortalBackgroundContract = exports.PortalDatabaseBlockTargetContract = void 0;
+exports.PortalTimelineAppearanceContract = exports.PortalTimelineViewContract = exports.PortalCustomWidgetAppearanceContract = exports.PortalCustomWidgetBrickContract = exports.PortalCustomWidgetDestinationContract = exports.PortalInfoDestinationContract = exports.PortalInfoImageContract = exports.PortalCardGroupAppearanceContract = exports.PortalCardGroupImageContract = exports.PortalFormFieldWidthContract = exports.PortalFormFieldTypeContract = exports.PortalFormAppearanceContract = exports.PortalRecentFilesSourceContract = exports.PortalDynamicTableAppearanceContract = exports.PortalBpmnDiagramAppearanceContract = exports.PortalCountdownAppearanceContract = exports.PortalCardDestinationContract = exports.PortalCardAppearanceContract = exports.PortalCardViewContract = exports.PortalCardBackgroundContract = exports.PortalFlexibleTextAppearanceContract = exports.PortalTextBackgroundContract = exports.PortalDatabaseBlockAppearanceContract = exports.PortalBackgroundContract = exports.PortalDatabaseBlockTargetContract = void 0;
 exports.PortalDatabaseBlockTargetContract = {
     Database: "database"
 };
@@ -42,6 +42,20 @@ exports.PortalCountdownAppearanceContract = {
     Blank: "blank",
     Custom: "custom"
 };
+exports.PortalBpmnDiagramAppearanceContract = {
+    None: "none",
+    Blank: "blank",
+    Custom: "custom"
+};
+exports.PortalDynamicTableAppearanceContract = {
+    None: "none",
+    Blank: "blank",
+    Custom: "custom"
+};
+exports.PortalRecentFilesSourceContract = {
+    Entireportal: "entirePortal",
+    Portalpage: "portalPage"
+};
 exports.PortalFormAppearanceContract = {
     None: "none",
     Blank: "blank",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fusebase/fusebase-gate-sdk",
-  "version": "2.5.1-sdk.2",
+  "version": "2.5.4",
   "description": "TypeScript SDK for Fusebase Gate APIs - Generated from contract introspection",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",

package/release-notes/{2.5.1-sdk.2.md → 2.5.1-sdk.3.md}

@@ -1,8 +1,8 @@
-# Release Notes 2.5.1-sdk.2
+# Release Notes 2.5.1-sdk.3
 
 - Current ref: `HEAD`
 - Previous tag: `v2.5.1-sdk.2`
-- Generated at: 2026-08-03T11:23:10.295Z
+- Generated at: 2026-08-03T11:21:58.855Z
 
 ## Included Drafts
 

package/release-notes/2.5.4.md

@@ -0,0 +1,9 @@
+# Release Notes 2.5.4
+
+- Current ref: `HEAD`
+- Previous tag: `v2.5.4`
+- Generated at: 2026-08-05T12:30:28.686Z
+
+## Included Drafts
+
+- None

package/release-notes/latest.md

@@ -1,8 +1,8 @@
-# Release Notes 2.5.1-sdk.2
+# Release Notes 2.5.4
 
 - Current ref: `HEAD`
-- Previous tag: `v2.5.1-sdk.2`
-- Generated at: 2026-08-03T11:23:10.295Z
+- Previous tag: `v2.5.4`
+- Generated at: 2026-08-05T12:30:28.686Z
 
 ## Included Drafts