> ## Documentation Index
> Fetch the complete documentation index at: https://docs.flowla.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What you can do

> Manage your Flowla rooms in plain language — no code required.

## Capabilities

> [card] [Rooms](https://docs.flowla.com/mcp/rooms.md)
>
> Create rooms from scratch, a template, or by duplicating one. List, update, and pull engagement analytics.

> [card] [Sections & pages](https://docs.flowla.com/mcp/structure.md)
>
> Build out the structure of a room and control who can see each part.

> [card] [Content blocks](https://docs.flowla.com/mcp/structure.md#content-blocks)
>
> Add text, images, links, embeds, PDFs, and task lists to any page.

> [card] [Action items](https://docs.flowla.com/mcp/action-items.md)
>
> Create and track shared to-do items with owners, due dates, and status.

> [card] [Workflows & webhooks](https://docs.flowla.com/mcp/workflows.md)
>
> Trigger automations and get notified when a room is completed.

> [card] [REX knowledge graph](https://docs.flowla.com/mcp/REX.md)
>
> Pull a deal's signals, scores, insight cards, and the quote-backed findings behind them — and write signals back.

> [card] [Lookups](https://docs.flowla.com/mcp/workflows.md#lookups)
>
> Find companies, users, labels, statuses, and templates to reference in other actions.

## Tips for better results

> [accordion] Name things clearly
>
> Referring to "the Acme room" or "the Pricing section" helps Claude target the right object. The more specific the name, the less back-and-forth.

> [accordion] Batch your requests
>
> You can create several sections, pages, or actions in a single ask. Claude will handle them in order and report back on each.

> [accordion] Build top-down
>
> Rooms → sections → pages → blocks → actions. If something can't be added, it's usually because the layer above it doesn't exist yet.

> [accordion] Be specific about visibility
>
> Say when something should be hidden or marked internal so buyer-facing content stays clean. Claude won't assume — it will do exactly what you ask.

> [accordion] Ask to review before bulk changes
>
> For example: *"List the actions first, then mark the overdue ones done."* This keeps you in control of what gets changed.

## A full example

Here's what a complete room setup looks like in a single prompt:

```text theme={null}
Create a Flowla room called 'Initech – Evaluation' from our sales template,
assigned to me. Add sections for Overview, Pricing, and Next Steps. Under
Next Steps, add an action items: 'Sign NDA' due next Friday assigned to
buyer@initech.com and an internal task 'Loop in solutions engineer'.
Then show me the room.
```

Claude will create the room, build the section structure, populate the action-plan block, and return a summary of everything it made.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.