> ## 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

<CardGroup cols={2}>
  <Card title="Rooms" icon="layer-group" href="/mcp/rooms">
    Create rooms from scratch, a template, or by duplicating one. List, update, and pull engagement analytics.
  </Card>

  <Card title="Sections & pages" icon="rectangle-list" href="/mcp/structure">
    Build out the structure of a room and control who can see each part.
  </Card>

  <Card title="Content blocks" icon="cube" href="/mcp/structure#content-blocks">
    Add text, images, links, embeds, PDFs, and task lists to any page.
  </Card>

  <Card title="Action items" icon="list-check" href="/mcp/action-items">
    Create and track shared to-do items with owners, due dates, and status.
  </Card>

  <Card title="Workflows & webhooks" icon="bolt" href="/mcp/workflows">
    Trigger automations and get notified when a room is completed.
  </Card>

  <Card title="Lookups" icon="magnifying-glass" href="/mcp/workflows#lookups">
    Find companies, users, labels, statuses, and templates to reference in other actions.
  </Card>
</CardGroup>

## Tips for better results

<AccordionGroup>
  <Accordion title="Name things clearly" icon="tag">
    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>

  <Accordion title="Batch your requests" icon="layer-group">
    You can create several sections, pages, or actions in a single ask. Claude will handle them in order and report back on each.
  </Accordion>

  <Accordion title="Build top-down" icon="arrow-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>

  <Accordion title="Be specific about visibility" icon="eye">
    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>

  <Accordion title="Ask to review before bulk changes" icon="list-check">
    For example: *"List the actions first, then mark the overdue ones done."* This keeps you in control of what gets changed.
  </Accordion>
</AccordionGroup>

## 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.
