Before you start
You need:- FlowForma on the FlowForma cloud service. Dedicated instances and on-premises installs aren’t supported.
- SharePoint Online in Microsoft’s commercial cloud. Government and sovereign clouds aren’t supported.
- A Claude plan that supports custom connectors. On Team and Enterprise plans, an owner adds the connector.
Set up the connector
1
Add the connector to Claude
On Team and Enterprise plans, an owner adds the connector once for everyone:
- In Claude, open Organization settings > Connectors.
- Click Add, then choose Custom > Web.
- Enter
FlowFormaas the name and the connector address above as the URL, then save.
2
Connect to test it
Connect to FlowForma yourself, to check the connector works before you tell your users:
- In Claude, open Customize > Connectors, find FlowForma, and click Connect.
- Review the FlowForma consent page, which shows what the connector will be allowed to do.
- Pick your Microsoft work account.
- In a new chat, ask Claude “What FlowForma apps do I have access to?”
3
Let your users know
Point your users to Get started for business users.
Microsoft Entra app and permissions
The connector signs in through FlowForma Digital Process Automation. FlowForma Copilot, the AI built into FlowForma, signs in through the same app. The app has these delegated permissions:
These are delegated permissions, so the connector always works as the signed-in user. It can never do more than that person can already do in SharePoint and FlowForma. The connector also holds no client secret for the app.
For more, see What it can access and the Security and data FAQ.
Control what it can do
On Team and Enterprise plans, owners can set each connector tool to Always allow, Needs approval, or Blocked for the whole organisation. People can’t override these settings. To set them, open Customize > Connectors, select FlowForma, then go to Tool permissions. To stop anyone publishing flows to FlowForma from Claude, block thepush_flow tool. To also stop people switching flows on or off, block switch_flow. People can still explore, explain, desk test, and draft flows. For the full list of tools, see Tools.
For the latest steps, see Anthropic’s guide to using connectors.
Conditional Access
If a Conditional Access policy asks for an extra sign-in step for SharePoint, such as a compliant device, the connector can’t ask for it yet. People the policy applies to can still connect, but the connector’s tools can’t reach SharePoint for them, and they see a message saying their organisation needs an extra sign-in step. There’s no workaround for this yet. People the policy applies to can still use FlowForma itself as normal.Monitor activity
Your admins can see connector activity in your own Microsoft 365 tenant:- Microsoft Entra sign-in logs show each sign-in to FlowForma Digital Process Automation. FlowForma Copilot sign-ins show there too.
- Version history on the Flows list shows every flow published through the connector. A publish is a normal change to the flow, made as the signed-in user.
Turn it off
- For one person: they disconnect or remove the FlowForma connector in Customize > Connectors.
- For your whole organisation: on Team and Enterprise plans, an owner removes the connector from Organization settings > Connectors.
- In Microsoft Entra: in Enterprise applications, open FlowForma Digital Process Automation, then Properties. Set Enabled for users to sign-in? to No to stop everyone, or set Assignment required? to Yes and assign only the people you choose. This also covers people using personal Claude accounts with their work account, but it stops FlowForma Copilot as well.

