632+ production-grade Power Automate cloud flows you can discover, customize, and deploy straight from your AI assistant — turning days of development into minutes and an easy ROI.
On a schedule, queries Salesforce for records modified in the last interval, groups by object type, and emails a digest of changes — useful for sales-ops oversight without inbox clutter.
Connect FlowLibs over MCP and work with the catalog conversationally — in Claude, Codex, Cursor, VS Code, Cline, or Windsurf.
Describe the outcome you want and your assistant searches the catalog by connector, category, or complexity.
Pull prerequisites, connections, environment variables, and ordered import steps without leaving the chat.
Have a solution packaged with your own environment-variable values baked in, ready to import.
Cloud-first patterns, packaged the way modern Power Platform solutions ship.
Every pattern is a real Power Automate cloud flow — built for Microsoft 365, Dataverse, and the connector ecosystem.
Connection references, environment variables, and choices included. Import the solution, wire up your connections, run.
Every flow is reviewed end-to-end — connectors, error handling, retry logic, and governance considerations.
Patterns span the Microsoft 365 stack and the systems-of-record around it.
Multi-connector flows that show off the breadth of the library.
Join the waitlist and be first to know when new cloud flows are added to the library.
Search by connector, audience, or skill level. Find the flow that matches your stack in seconds.
A hand-curated rotation of cloud flows. Refreshed weekly.
A centralized notification flow that receives requests via HTTP trigger and dispatches notifications to multiple channels: email, Teams, push notifications, and SMS. Acts as a reusable notification service for other flows.
Triggered on Dataverse solution import event to production environments. Pauses the import and routes an Approvals request to the COE lead with solution name, version, component count, and requesting user. On rejection, rolls back and notifies the developer. On approval, completes import and posts a Teams changelog.
Reads a Dataverse log of DLP violations, looks up the maker via Office 365 Users, and sends a personalized Outlook email with the policy violated, affected flow name, and remediation steps.
Triggered on a schedule, calls Microsoft Graph and Azure Key Vault APIs via HTTP to check app registration client secret expiry dates across all service principals used by Power Platform connections. Logs rotation status to Dataverse and posts a Teams adaptive card when any credential is within 14 days of expiration, preventing silent flow failures from expired secrets.
Periodically pull all users and their managers via Office 365 Users, build a hierarchical org chart, and publish to SharePoint.
On PR open, reads a flexible CODEOWNERS map from Dataverse (more dynamic than a static file), calls Request Reviewers For A Pull Request by changed paths, and Teams-messages each reviewer.