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

# Get started for business users

> Connect Claude to FlowForma, then explore, build, desk test, and publish flows by chatting with Claude, with example prompts to try.

This guide follows a flow from start to finish: connect, explore, build, desk test, check, publish, try it out, and change it later. Once the FlowForma connector is set up for your organisation, you can connect in a couple of minutes.

## Connect to FlowForma

**1. Find the FlowForma connector**

In Claude, open **Customize** > **Connectors** and find **FlowForma**.

If it isn't listed, ask your IT admin to add it, and point them to [Set up for IT admins](https://docs.flowforma.com/flowforma-for-claude/it-admin-setup.md). On an individual Claude plan, you add it yourself, using the same page.

**2. Connect and sign in**

Click **Connect**. FlowForma shows a consent page, which lists what the connector will be allowed to do, then Microsoft asks you to pick an account.

Pick the work account you use for FlowForma. This isn't necessarily the account you use for Claude.

**3. Turn it on for your chat**

In a chat, click the **+** button at the bottom left of the message box, then **Connectors**, and make sure **FlowForma** is turned on. Then ask Claude about your flows.

Claude's menus change from time to time. If these steps don't match what you see, see Anthropic's guide to [using connectors](https://support.claude.com/en/articles/11176164).

## Explore your apps and flows

Ask Claude which FlowForma apps you have access to, which flows they hold, and how a flow works. Claude works with your own permissions, so you only see what you already could in FlowForma.

* "What FlowForma apps do I have access to?"
* "Give me the link to open the Purchase Request form."
* "Walk me through what the Leave Request flow does, step by step."
* "Who approves an expense claim over 1,000 in the Expenses flow?"
* "Which SharePoint lists does the Asset Register flow use?"
* "Show me the rules in the Contract Approval flow that are switched off."

To list an app's flows, you need read access to the app's **Flows** list. To read a flow in full, so Claude can explain or change it, you need to be an app admin or an admin of that flow.

An app admin is a member of the app's FlowForma admin group, or a site collection admin (an administrator of the whole SharePoint site the app is in). For the full list, see [What it can access](https://docs.flowforma.com/flowforma-for-claude/what-it-can-access.md#who-can-see-and-change-what).

## Build or change a flow

Describe the process you need, or the change you want to make, and Claude builds it. Anyone signed in can ask for a new flow. To change an existing flow, Claude reads it first, so you need the access above.

* "Build me a flow for new starter onboarding. HR fills in the details, IT sets up equipment, and the line manager signs off."
* "Add a cost centre question to the first step of the Purchase Request flow and make it required."

Claude works on a private working copy, which only you can see, until you publish. Nothing changes in FlowForma while you build. Working copies are deleted 24 hours after you last use them, so publish or finish your change within a day.

For the parts of a flow Claude can't build yet, see [Not yet supported](https://docs.flowforma.com/flowforma-for-claude/not-yet-supported.md).

## Desk test the flow

A desk test reads the flow and lays out what it will do, without running it in FlowForma: every route and what decides it, when each question shows and hides, and who gets each step on each route. It can also suggest improvements, and walk a form through the flow with answers you give it.

* "Desk test this flow."
* "How can I improve this flow?"
* "What happens if the total is 2,400?"

Anyone signed in can desk test a flow they're building. To desk test a flow that's already in FlowForma, Claude reads it first, so you need the access above.

## Check it against your site

Before you publish, Claude checks the flow against your site. The check finds anything the flow needs that's missing, such as a list, column, person, or permission, and shows what will change. Checking a flow needs you to be an app admin.

* "Check the new flow against the site. Is anything it needs missing?"

If the check finds a problem, ask Claude to fix it, then check again. For what each message means, see [Messages you might see](https://docs.flowforma.com/flowforma-for-claude/messages.md).

## Publish it

Publishing a flow from Claude works the same way as saving it in the FlowForma designer. There's no separate draft stage in FlowForma.

1. Claude shows you a preview of what will change. Before an update, the preview also lists any change to who can see or act on the forms, or to what's recorded.
2. You confirm, and Claude prepares the flow for publishing. This runs the same check against your site again.
3. Claude asks you to approve publishing it. A prepared publish lasts 10 minutes, so if you take longer to approve, Claude prepares it again.
4. FlowForma publishes the flow to your app.

What happens next depends on the flow:

* **A new flow** is switched on if a flow licence is available.
* **An updated flow** keeps its current on/off state.

If someone else changes the flow after Claude has read it, FlowForma stops the publish rather than overwrite their change. Ask Claude to read the flow again, then repeat your change.

If a publish fails partway, FlowForma removes what it had added where it can. Open the flow in FlowForma and check it before you try again.

Publishing a flow needs you to be an app admin.

> [!TIP]
>
> Try new flows and bigger changes in a test app first, then publish them to your live app once you're happy.

## Try it out

Once the flow is published, open it in FlowForma and submit a test form to see it working.

* "Give me the link to start a new Staff Onboarding form."
* "Give me the link to open the Staff Onboarding flow in the designer."

## Change it later

To change a published flow, ask Claude, and it follows the same steps: it reads the current flow, works on a private working copy, checks the result against your site, and asks you to approve publishing it.

* "Change the approver on the second step of the Staff Onboarding flow to the Finance team."

## Undo a change

A publish can't be undone with one click, so keep a copy first:

1. Before a big change, [export the flow](https://docs.flowforma.com/product/the-flowforma-site/import-export.md#export-a-flow) from FlowForma as a backup.
2. To reverse a change, ask Claude to change the flow back, then publish it again.


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