Integration

Flowla integration

Flowla runs digital sales rooms: branded pages where a seller and a buyer share content, a mutual action plan and next steps. List rooms with their engagement totals, read a room's full structure and its analytics (progress, assignees, who viewed which page and for how long), list visitor sessions, build room content (sections, pages, groups and text, image, embed, link, PDF or action-plan blocks), manage action items, list and create companies, and trigger Flowla workflows. Creating or editing the room itself, webhooks, and the users, labels, statuses, templates and room-completed events lists are not exposed. Authentication is an API key generated in the Flowla workspace under Settings, API, sent in the x-flowla-api-key header.

Connect Flowla How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Flowla.Built from the 23 Flowla tools below, on the connection you add once.

What you can do with Flowla

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Action item, 4 operations

create_action_itemsCreate action itemsPOSTAdds action items (mutual action plan tasks) to an action-plan block: title, description, status, start and due dates, internal flag and assignees. Read their ids back with list_action_items.
delete_action_itemDelete action itemDELETEDeletes an action item (a mutual action plan task) from its action-plan block.
list_action_itemsList action itemsGETLists action items (mutual action plan tasks) of a room, a page, or one action-plan block (blockId needs pageId): title, status, dates, internal flag and assignees.
update_action_itemUpdate action itemPATCHUpdates an action item: title, description, status (todo, in_progress, done, cancelled), dates, internal flag or assignees. Only the fields sent change; assignees replaces the whole list.

Block, 3 operations

create_blocksCreate blocksPOSTAdds content blocks to a group: text (Markdown), image, embed, link, PDF or an action-plan (task list). Images and PDFs are fetched from their public URL and stored by Flowla. Blocks are laid out in columns.
delete_blockDelete blockDELETEDeletes a block from a page; deleting an action-plan block also deletes all its action items.
update_blockUpdate blockPATCHChanges a block's text (Markdown, for text blocks) or URL (image, embed, link and PDF blocks). A block's type cannot change: delete it and create a new one.

Group, 3 operations

create_groupsCreate groupsPOSTAdds one or more groups (rows that hold blocks, each with an optional title) to a page. Read their ids back with get_room_contents.
delete_groupDelete groupDELETEDeletes a group and all its blocks permanently, including the action items of any action-plan block in it.
update_groupUpdate groupPATCHRenames a group (a row of blocks) on a page.

Page, 3 operations

create_pagesCreate pagesPOSTAdds one or more pages to a section of a room, each with a title and an access level. Read their ids back with get_room_contents.
delete_pageDelete pageDELETEDeletes a page of a room and all its groups and blocks permanently.
update_pageUpdate pagePATCHRenames a page of a room or changes its access level (visible, restricted, locked or hidden).

Section, 3 operations

create_sectionsCreate sectionsPOSTAdds one or more sections (top-level chapters) to a room, each with a title and an access level (visible, restricted, locked or hidden). Read their ids back with get_room_contents.
delete_sectionDelete sectionDELETEDeletes a section of a room and all its pages, groups and blocks permanently.
update_sectionUpdate sectionPATCHRenames a section of a room or changes its access level (visible, restricted, locked or hidden).

Company, 2 operations

create_companyCreate companyPOSTCreates a company in the organization from its domain (the name defaults to the domain) and returns its id, name, domain, website and creation date.
list_companiesList companiesGETLists the organization's companies (the accounts rooms are linked to), searched by name or domain: id, name and domain, with totals.

Analytic, 1 operation

get_room_analyticsGet room analyticsGETReturns a room's analytics: progress percentage, everyone on the room (team and buyers, with last visit and view count) and, per section, who viewed each page and action, for how long, and their engagements. Personal data.

Content, 1 operation

get_room_contentsGet room contentsGETReturns the full structure of a room (sections, then pages, groups and blocks) with the text of each block; action-plan blocks also carry their action items. Use it to read the ids of everything in a room.

Room, 1 operation

list_roomsList roomsGETLists the organization's rooms with engagement totals (views, unique views, clicks, comments, downloads, reactions, shares, completed tasks), last engagement, owner and company ids, cover and colors.

Session, 1 operation

list_sessionsList sessionsGETLists visitor sessions (each time someone viewed a room): room, start time, visitor city, region and country, browser and OS, identified contact (name, email) and room owner. Personal data.

Workflow, 1 operation

trigger_workflowTrigger workflowPOSTTriggers a configured Flowla workflow (automation), passing data as its input. What happens next depends on the workflow, which may send emails or update rooms and your CRM.

Use Flowla from Claude Code, Cursor or Codex

Connect Flowla in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Flowla operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Flowla

Create your workspace
Sign up free. Nothing to install.
Connect Flowla once
Add your Flowla connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.