FlowForma Adds Claude, ChatGPT and Copilot Workflow Design for Microsoft 365

What FlowForma says it shipped​

FlowForma Process Automation is an AI-powered, no-code platform for building, running and governing workflows natively on Microsoft 365 and SharePoint Online. The new piece is a conversational front door. The company says its visual flow designer stays at the center of the product. The assistant integrations are an addition, not a replacement.

According to the release, the assistant carries built-in knowledge of how FlowForma models steps, forms, rules and branches. Because of that, it asks the questions a business analyst would, writes the process specification, and builds a working flow. The examples given are a purchase requisition, employee onboarding and an incident report. Users can also bring existing FlowForma processes into a conversation and ask for improvement suggestions. The release also says a request such as a new approval route or form field is sent straight to FlowForma Process Automation.

Design in the chat, execution in FlowForma​

The central claim is a split of responsibilities. The AI assistant handles the conversation, and FlowForma Process Automation handles execution. The company says permissions and approvals keep running inside FlowForma. It also says the processes and their data stay in the organization's own Microsoft 365 tenancy. FlowForma adds that it is a Microsoft AI Cloud Partner and is ISO/IEC 27001:2022 certified.

That split is sensible. The assistant drafts and FlowForma executes, so the part that touches approvals and records stays on a platform built for it. Still, "processes and data stay in the tenancy" describes where workflows execute. It does not tell you what passes through the assistant provider during the design conversation.

What the announcement does not say​

The release leaves several details that admins would want before piloting this:

• Integration mechanism: It doesn't say how each assistant connects, or what plans, versions or permissions are needed.
• Copilot scope: "Microsoft Copilot" is not defined further. The release doesn't say which Copilot product or edition is meant, or whether licensing differs.
• Data flow: It doesn't say what prompts or process definitions go to Anthropic, OpenAI or Microsoft. It also doesn't cover retention, consent, identity controls or auditing.
• Change control: It says changes "go straight" to FlowForma. It doesn't describe testing, approval or publishing steps between a chat edit and a live process. Treat "prompt equals production" as unverified.
• Evidence for speed: The claim that this removes most of the wait for build work is a vendor assertion. No measured savings are given.

FlowForma's own product pages do list scenario testing and logic validation before go-live for its in-product AI builder. That is separate from the new assistant integrations, so it shouldn't be assumed to apply to them.

The legacy-migration angle, with dates​

The release suggests teams can rebuild processes that relied on InfoPath and SharePoint 2013 workflows by describing how they worked. The Microsoft lifecycle dates here are firm:

• Microsoft's guidance says SharePoint 2013 workflow was turned off for new tenants on April 2, 2024, and fully retired from existing tenants on April 2, 2026. That applies across all environments, including Government Clouds and Department of Defense.
• Microsoft recommends moving to Power Automate or other supported orchestration, including partner offerings. It names Power Automate as its own workflow solution.
• Microsoft says support for InfoPath 2013 ended on July 14, 2026. It recommends moving existing forms and workflows to supported Microsoft 365 solutions.

Both deadlines have passed. For SharePoint Online tenants this is no longer a planning exercise.

FlowForma is a third-party option. It is not a Microsoft feature or an official migration tool. The release describes recreating a process from a description. It doesn't describe automated conversion of old workflows, a feature-parity check or recovery of original logic and data. Anyone with a backlog of legacy workflows should first inventory what exists. Microsoft's guidance points to its Microsoft 365 Assessment tool for finding SharePoint 2013 workflow usage. Conversational rebuilding is a drafting aid, not a substitute for that audit.

Competitive context​

Runtimewire frames the launch as a test of whether a specialist workflow vendor can stay relevant when Microsoft and the large AI platforms both want to own the first prompt. That is a fair reading. Power Automate is Microsoft's own workflow answer, and FlowForma's FAQ describes its approach as complementary to Microsoft Copilot. Whether that holds depends on how well the integrations work, which this announcement can't show.

Availability and practical next steps​

FlowForma says it is available now in Claude, ChatGPT and Microsoft Copilot. Existing customers are told to contact their account manager. The company is offering new customers a 30-day free trial with no credit card. Those commercial terms come from the vendor.

If you are evaluating it, ask FlowForma for answers on these points:

1. Which assistant plans and Copilot surfaces are supported, and what admin consent is required.
2. Exactly what content leaves your tenant during design conversations, and how long the provider keeps it.
3. Whether AI-made changes need review or testing before they go live, and how they are logged.
4. Which FlowForma features can and cannot be created or edited by conversation.
5. How a rebuilt legacy process is validated against the original.

Bottom line​

This is a concrete product change. FlowForma has added assistant-based design and optimization on top of an existing Microsoft 365-native workflow platform. The governance story is plausible but thinly documented. The migration pitch is timely, because the Microsoft deadlines have passed. The speed claims are unproven. Pilot it on a low-risk process, and ask your vendor for the data-flow and change-control answers in writing.