Quick answers, no hunting.

FlowLibs is a curated library of production-grade Power Automate cloud flows. Each flow is documented with its purpose, trigger, connectors, and audience, and packaged as an unmanaged Power Platform solution you can import directly into your environment — and customize freely once it's there.

Power Platform makers, Power Platform admins, and Microsoft 365 / Dataverse developers who want a head start on common automation patterns instead of building from scratch every time.

Visit the Cloud Flows page and use the sidebar filters to narrow by category, connector, audience, or skill level. Every card shows what the flow does and which connectors it needs at a glance.

Yes. The flows themselves are standard Power Automate cloud flows, so the same Microsoft licensing rules apply. Premium connectors (Salesforce, SQL Server, Dataverse, etc.) require a per-user or per-flow premium plan from Microsoft.

Download the solution zip, then go to make.powerautomate.com → Solutions → Import solution and upload the zip. Power Platform will walk you through resolving connection references and environment variables before activating the flow.

You need at least the System Customizer security role on the target environment. To turn flows on after import, the flow owner needs a Power Automate license that covers the connectors used.

FlowLibs ships every solution as an unmanaged solution. That's deliberate: an unmanaged solution lets you open it in your environment, inspect exactly how each flow is built, and edit or extend the components directly to fit your process. If your ALM practice calls for a managed copy in Test and Production, you can pack a managed version from your own dev environment — but what we hand you is unmanaged, so you're never locked out of customizing it.

The most common cause is a connector reference that hasn't been published in your environment yet (Premium connectors usually). Confirm your environment has the required connectors enabled, or reach out via the Support page with the import log and we’ll help diagnose.

A connection reference is a solution-aware pointer to a specific connection (set of credentials). Connection references decouple the flow from any individual user's connection, which makes ALM (Dev → Test → Prod) clean and predictable. After import, point each connection reference at a connection that lives in the target environment.

The library spans 17 connectors across the Microsoft 365 stack and the systems-of-record around it: SharePoint, Teams, Outlook 365, Excel Online, Word Online, OneDrive, OneNote, Planner, Forms, Approvals, Power BI, Dataverse, SQL Server, Salesforce, GitHub, Azure AD, RSS, HTTP, and a few more.

First, sign in to the connection in make.powerautomate.com → Connections and verify it's healthy. Premium connectors will show a license warning if the user doesn't have the right plan. For service-account scenarios, confirm the account has the necessary scopes / API permissions on the source system.

Create a new connection in the same environment, then update the connection reference to point to the new connection. Once the flow shows a successful run with the new connection, delete the old one. This keeps the flow alive throughout the rotation.

Yes. They're standard Power Platform solutions, so they work with both Power Platform Pipelines and Azure DevOps / GitHub Actions ALM workflows. Import the unmanaged solution into Dev, then promote it through your existing pipeline the same way you would any first-party solution.

It varies by flow, but most flows expose URLs, list / table names, and group IDs as environment variables so you can re-target them per environment without editing the flow. The detail page for each flow lists the variables you'll be prompted to set on import.

No — every FlowLibs component uses the flowlibs_ publisher prefix, so it lives in its own namespace. Your existing components are untouched.

Absolutely — that's the whole point of shipping unmanaged. Because the solution is unmanaged, you can edit the flow and its components directly in your environment, with no layering workarounds. If you expect to pull in future FlowLibs updates, keep track of what you changed (or make your edits in a separate solution) so you can re-apply them cleanly after an update.

A subset of the library is free to anyone with a FlowLibs account. Additional flows and pro features are gated behind a paid tier — pricing details will be published before the library exits early access.

Sign in or create a free account, then click "Request access" on the flow detail page. We'll grant access to your account and send a download link for the solution zip.

Each person should sign in with their own account. Solution downloads are per-account so we can keep the audit trail clean. Team / org plans are on the roadmap.

Go to Profile → Delete account, or email support@flowlibs.com if you can't access your account. We'll process the deletion within 7 days per our privacy policy.