Flows

Get the one-line code that puts the site's chat on the website, where to paste it, and where the chat shows today. The chat appears on the website once the code is on its pages and its placement includes the website (set_chat_placement). After the owner pastes and publishes it, check_chat_install confirms it.

get_chat_install

Returns the Flows account this connection is signed in as: its name and email, or the one site a site connection link is bound to. Use it to confirm the connection is working.

get_profile

Show where a site's setup stands, as a checklist: the site and its address, the business details still missing, and where the chat shows (off, articles, website or articles_and_website). Use it to choose the next step with the user.

get_setup_status

A screenshot of the connected site's homepage, showing its real look: layout, colours, type and spacing. Default = above-the-fold; pass fullPage:true to see the whole page (scrolled so lazy content renders, capped at 4000px tall). Cached for 7 days; pass refresh:true after the site changes (fresh captures are capped per site per hour, and the cached shot is returned past the cap). Omit instanceId and Flows uses your site automatically.

get_site_screenshot

List the data tables on a Flows site you own (Projects → Databases). Each table has an id, name, columns, and row count, plus plan quota. Use this before create_table or query_rows so you use exact names/ids.

list_tables

List the Flows sites you own — names, domains, and each site's data tables with row counts — so one call maps the whole account. Name a site to any tool by its instanceId, domain or name.

list_my_sites

List the store products on a site you own, newest first, each with its productId, name, price, which store it came from, its collections, whether it is hidden, and how many content sections it already has. Read this FIRST — nothing else gives you a productId. hidden:false marks the products shoppers can actually see, so those are where content work reaches an audience; a hidden:true product is one the merchant has taken off their store and will decide themselves when to bring back. Covers every rail: Stripe, Wix, Shopify and manual products all carry sections the same way.

list_products

List folders that group data tables on this site (Projects → Databases).

list_folders

Move a data table into a folder, or to the root. Folder is created if the name does not exist. Pass empty folder to unfile to root.

move_table

Read rows from a data table you own. Optional keyword search (q) and exact column filter — both run across the whole table, so total and offset paging are exact. Hard limit 50 rows per call.

query_rows

Read how the site's chat agent is set up: its welcome title and greeting, the three suggested asks under the composer (chip word + the message it sends), tone, the owner's instructions, which abilities are switched on, the chat's design (theme: style, launcher, colours, fonts, sign-in stylesheet) and the owner's sign-in words.

get_concierge_settings

Read where the site's reader chat appears: showOn is off, website (the pages of the owner's own website), articles (the Flows article and listing pages of a site Flows publishes articles for) or articles_and_website. Also lists the website pages it stays away from (hiddenPages) and the site's pages to choose from, each with its path, title and whether it is hidden.

get_chat_placement

Read one data table: name, column schema (field types), row count, and a few sample rows. Pass the table name or id from list_tables.

get_table

Read one product's content sections — the accordions shoppers open on the product, in the dashboard's Content tab. Returns the product's description, its current sections in order, whether it is hidden from the store, and the limits a write must respect. This is what a write builds on: set_product_content saves the complete set, so the sections here are the ones to carry forward alongside anything new. Bodies are plain text, and the renderer gives four markers meaning: "• " or "- " opens a bullet list, "1. " a numbered list, "## " a subtitle, and **bold** emphasises inline anywhere. A blank line closes a block. Every other line becomes a paragraph and reaches the page exactly as typed.

get_product_content

Remove a column and all its values from every row. First call returns needs_confirmation + confirmToken; call again with that token after the user agrees.

remove_column

Rename a column on a data table. Existing row values move to the new field name.

rename_column

Rename a data table and/or change its description.

rename_table

Rename a data table folder, named by its name or id from list_folders.

rename_folder

Save a site's business details: the name shoppers know the site by, and the name of the business behind it. Send only the details to change; the rest stay as they are.

save_business_details

Search Flows' own documentation — how features work, how to set them up, and what each setting does. Use it whenever the user asks HOW to do something in Flows, before answering from assumption. Covers putting the chat on a website, choosing the pages and the design for the chat, connecting AI tools over MCP, and every other documented feature. Each result carries a `page` link to the full docs section — share it in your answer so the user can read the rest.

search_flows_docs

Set (or clear) the brand logo shown in the chat header, the same control as Concierge → Configure → Header logo. The logo REPLACES the agent name in the header rather than sitting beside it. SVG markup only — a single <svg>…</svg> with a viewBox, containing static shapes; scripts, links, embedded images and animation are rejected, not stripped, so an invalid logo fails loudly instead of rendering nothing on the merchant's site. Pass an empty string to clear and fall back to the name. Draw the mark with currentColor and it adapts to both themes automatically; otherwise supply logoLight too, because a near-black wordmark is invisible on a dark header and a white one is invisible on a light header.

set_header_logo

Set where the site's reader chat appears. showOn: off, website (the pages of the owner's own website), articles (the Flows article and listing pages of a site Flows publishes articles for) or articles_and_website. hiddenPages: the website pages it stays away from, as paths such as /checkout; it replaces the list, and [] shows the chat on every page. Pages published later show the chat until they are hidden too. On the website, the chat appears on pages that carry its install code (get_chat_install). Send one or both; changes reach the live chat straight away.

set_chat_placement

Set a product's buy-link — an https URL the product's Buy action routes to on every surface instead of the cart. This is how a merchant sells account-bound things through their store: their own subscriptions, memberships, or anything whose purchase belongs on another page. Saved straight to Stripe (the merchant's native Product.url field), so it applies to Stripe and manual products — list_products shows the source. Up to 500 characters; an empty string clears the link and the Buy action routes through the cart again.

set_product_buy_link

Write a product's content sections — the merchant's own prose about what they sell, like "What's included", "How to use" or "FAQ", shown as accordions wherever the product appears and live the moment you save. This saves the COMPLETE ordered set: whatever you send becomes the product's sections, so get_product_content gives you the existing ones to carry forward, and an empty array clears them. Up to 6 sections, titles 40 characters, bodies 4000. This copy sits beside a price and the merchant stands behind every word of it as a commitment to their customers, so it lands best when each specific traces back to their own product data, pricing, or what they have told you. Bodies are plain text, and the renderer gives four markers meaning: "• " or "- " opens a bullet list, "1. " a numbered list, "## " a subtitle, and **bold** emphasises inline anywhere. A blank line closes a block. Every other line becomes a paragraph and reaches the page exactly as typed.

set_product_content

Write a product's description — the short paragraph at the top of the product, above its content sections. get_product_content returns the current one. This is the merchant's Stripe field, so it is saved straight to Stripe and also appears on Stripe Checkout, invoices, receipts and the customer portal: one description covers the whole journey from browsing to paying. Up to 2000 characters, plain prose, and an empty string clears it. Products synced from Wix or Shopify keep their description on that platform, so this applies to Stripe and manual products — list_products shows which is which under "source". A description reads best as a couple of sentences on what the product is and who it suits, with the detail living in sections.

set_product_description

Turn site-chat AI read ON or OFF for a data table (same as "Allow AI to read this table" in Databases → Configure). Only when the user clearly asks. ON = public site chat may use this table's rows. If columns look personal, the first call returns needs_ai_read_confirm with a confirmToken — tell the user, and if they still want it, call again with that confirmToken. Optional aiDescription is short context for the chat about the table.

set_ai_readable

Shape how the site's chat agent greets, guides and looks: the welcome title and greeting, the three suggested asks, tone, the owner's instructions, ability switches, and the chat's design (theme). Send the settings to change; the rest stay as they are. Changes reach the live chat straight away.

update_concierge_settings

Update fields on one row. Pass recordId from query_rows/get_table and a data object with only the columns to change (merge).

update_row