Pipefy named a Strong Performer in Gartner® Peer Insights™ Voice of the Customer
Stay close to what's happening at Pipefy, from company news to announcements straight from our team.
Recently active
We launched the Pipefy product roadmap page Now you have one place to track everything that has evolved in the product: over 20 improvements from the last few months, including MCP Server, AI Agents, BYOM, and Integration Hub, always updated as new releases are announced. ⭐ Access the page, save it to your favorites, and follow the product's evolution directly from here. Check out all releases 💙 This content is exclusive to Pipefy Community members. Not a member yet? Sign up in under 2 minutes using your Google account.
The way work happens has changed. And it no longer starts inside a system The AI your team already uses — Claude, Codex, Gemini, Copilot — can now trigger, execute, and close complete processes in Pipefy.With governance, audit trails, and business rules built in. In days, not months. Discover what changes in your process Configure right now
Chatting with IT leaders is always enlightening! At our recent networking event in Chicago, discussions on AI, change management, and the adoption of new software were among the highlights. The IT leaders present shared a rather optimistic view of how AI will continue to support business efficiency in 2024. We also talked about how ensuring ease of use, proper setup, and managing expectations are crucial steps in preventing a tool from becoming shelfware. Above all, there was a consensus on the need to make sure new tech will seamlessly blend into each unique environment—before even contemplating its place in the tech stack. In this context, software integration emerges as a key player in truly setting the stage for success. 💡How do you align expectations for software within your stack?
Greater process visibility, access control, and new integration possibilities When a process spans multiple pipes, integrations, and AI Agents, understanding its connections and reviewing who can access each piece of information requires a clear view of operations.October's updates help you see those relationships, involve your team in agent troubleshooting, and build integrations with less manual work. Here is what changed and how each update can support your daily work. Explore all releases:Map: faster to open and visibility into connection volume Map: now shows the connections your AI Agents create AI Agent Permissions: view only access for Pipe Members Pipefy Integrations: AI powered routing, more connectors, and a faster builder Members and Permissions: filters to review access in a few clicks Claude: Pipefy arrives in the Anthropic ecosystem Map: faster to open and visibility into connection volumeExploring a process with multiple connections now involves less waiting. Map opens
OverviewPipefy is expanding its presence in the Anthropic ecosystem to give teams a direct way to query data, trigger workflows and manage pipes without leaving Claude. This integration has two complementary paths: a connector, available today, and a native plugin that brings prebuilt agent workflows and interactive commands into the Claude interface. What's new? Claude Connector available in the Claude Directory, linking Pipefy to Claude with no additional setup. Querying data, triggering workflows and managing pipes happening directly inside a Claude conversation, through the MCP protocol. Pipefy's native plugin under review by Anthropic, bringing prebuilt agent workflows and interactive commands into the Claude interface once approved. The same connection approach being extended to other enterprise AI marketplaces, such as Microsoft Copilot and Cursor. Connector and plugin solve different needs: the connector links Claude to your Pipefy data through MCP, while the plugin adds prebu
Pipefy is discontinuing its mobile app and moving access to the web version, which offers a fully responsive experience on mobile devices. This change reflects our decision to focus our efforts on the web platform, currently Pipefy’s most robust and up to date channel. We will provide a transition period so you have time to adapt without disruption to your operations, with support available throughout the process. Why is the mobile app being discontinued?We are focusing our investment on the web experience, which is currently Pipefy’s most robust and up to date channel. When will the app stop working?The app was removed from the App Store and Google Play on October 28 and will be permanently shut down on December 18.Can I keep using the app until then?Yes. If you already have the app installed, you can continue using it until December 18. New downloads are no longer available.How do I access Pipefy on my phone after that?Open https://app.pipefy.com/ in your phone’s browser and sign in
OverviewReviewing who has access to the workspace and at what permission level used to mean scrolling through the entire member list by hand. The Members and Permissions screen now has a filter panel that makes that review objective: in a few clicks, you isolate exactly the group of users you need to check. What's new?A Filters button next to the name search opens a panel with four combinable fields Role: select one or more roles, including each company's custom roles Billable: Yes or No 2FA: Yes or No Last login: Last 7, 30, or 90 days, More than 90 days ago, Never accessed, or a custom range How does this help?Admin access review in seconds: combine Super admin and Company admin to list everyone with elevated privileges, without opening each profile one by one Security risk identification: filtering by 2FA: No immediately surfaces everyone who still hasn't turned on two factor authentication Lower cost from idle licenses: Billable: Yes combined with Last login: More than 90 days ago
OverviewProcess management loses efficiency and exposes operations to errors when critical information like internal policies, price sheets, and contract templates must be manually downloaded and re uploaded into artificial intelligence tools. Pipefy AI Agents now read documents stored directly in Google Drive and Microsoft OneDrive. Your team connects files where they already live, keeping the knowledge base in sync automatically, with no manual copies going stale. What's new? Google Drive as a knowledge source: direct connection to files in Google Docs, Google Sheets, Google Slides, PDF, DOCX, TXT, CSV, and xlsx, available under the Add document menu inside the agent's Knowledge Base. Auto sync is enabled by default and can be turned off per file. Microsoft OneDrive as a knowledge source: connect a Microsoft account and paste the link to a OneDrive file right from the Add document menu. Supports PDF, DOCX, XLSX, TXT, CSV, PPTX, DOC, XLS, and PPT. Content preview: for both connectors
OverviewAdmins and Super Admins now receive automated alerts whenever API calls and Automations consumption hits 80%, 90%, 100%, and 150% of plan limits. Alerts arrive via email for direct visibility and can also be configured through Webhooks, delivering the same notice directly to your internal systems and automation workflows. What's new? Automated email notifications at four critical thresholds: 80%, 90%, 100%, and 150% of consumption limit. Configurable Webhooks that send these same alerts in real time to internal systems, communication platforms, or custom software. Email preference management in User Settings; Webhook configuration in Account Settings. Initial coverage for API calls and Automations, with continuous expansion to remaining add-ons. How does this help?Each team gets the alert on the right channel: email for direct admin visibility, Webhook for automated response by technical teams. Capacity planning becomes predictable, eliminating surprise overages or service d
OverviewAutomations and conditional fields now come with a suggested name. The name is built from what you configured. Anyone opening the list understands what each one does without opening its setup.Until today, a new automation started with an empty name. The person who created it knew what it did. Anyone inheriting the process, or the same person months later, had to open each one. In a pipe with dozens of automations, the list stopped being readable. What's new?Suggested at creation. The name comes from the trigger and action you configured. For conditional fields, it comes from the condition and the affected field. Works on what you already have. When editing an existing automation or conditional field, ask for a suggested name and bring the whole pipe up to the same standard. Both objects. Automations and conditional fields. Always editable. It's a suggestion, not a rule. Prefer your own naming? Just edit it. How does this help?A readable list. You understand what each automation
OverviewWe adjusted credit consumption for the Lite and BYOM (Bring Your Own Model) options in Pipefy AI. Running an automation with Lite now costs half of what it did, and BYOM runs cost a third less. The change is already live for the entire base, no configuration needed. What's new?Pipefy AI Lite: consumption drops from 2 credits to 1 credit per run. Bring Your Own Model (BYOM): consumption drops from 1.5 credits to 1 credit per run. Standard and Pro stay at 2 credits per run (Pro is in its promotional period until 10/08, then moves to 3 credits). How does this help?Lite's cost now matches its use case: picking the lightest model for simple tasks now makes financial sense too, not just technical. BYOM reflects the real cost of running your own model: if you already pay for your model's tokens, you no longer absorb a disproportionate credit cost on top of that. No action required: the update is already live across the entire base, no need to reconfigure existing agents or automations
OverviewInvestigating AI Agent executions just got faster. AI Agent Logs now include additional filters, a new Card ID column, and a calendar mode for selecting date ranges, making it easier to find the exact execution you need without scrolling through long lists. What's new?Date range calendar: filter executions by a specific period directly from the date picker. Card ID column: see which card each execution is linked to and jump straight to it. Triggers column and filter: identify what started each execution and filter by trigger type. Improved keyword search bar, now displaying results correctly. How does this help?Less time searching: the date range calendar removes the need to scroll through long execution lists to find the right period. Direct traceability: the Card ID column links each execution to its corresponding card, making audits and targeted investigations easier. More precise diagnosis: the Triggers filter isolates executions by what started them, helping you quickly sp
OverviewChanging the setup of a live process can be unsettling: a structural change might break active rules and bring operations to a halt. Pipe Snapshots brings the same concept as the UI's version history to the API. Each snapshot is a saved version of the pipe's setup, and the workflow can be restored to the latest snapshot if a change does not go as planned. What's new?Snapshot and restore capabilities are available through GraphQL API calls in the Pipefy Developer Portal:Full pipe snapshot (Create Pipe Snapshot): generates a structured JSON file containing setup elements such as phases, fields, automations, conditionals, and more. Restore to the latest stable version (Restore Pipe to Last Snapshot): reverts the pipe's setup to the latest saved snapshot. This action cannot be undone. View and manage history (Query & Rename Pipe Snapshots): list a process's saved snapshots and rename them to keep versions organized. How does this help?Greater confidence when changing live proce
OverviewVersion history lets you save and download any pipe's setup directly in Pipefy. It helps IT governance teams see how a process was configured on a specific date and provides a record for safer adjustments before high-risk operational changes. What's new?One-click version creation: save a version of your pipe's setup under Manage → Version history. You can rename each record to make it easier to identify. JSON file download: download a version's JSON file to inspect the setup, compare configurations from different points in time with a diff tool, or share it with an AI agent. Completion notification: receive an in-app notification confirming that processing is complete and the version is ready in the list. The notification appears when you refresh the page. Pipe traceability: view each version's ID, author, and date, with events automatically recorded in the history under Activities. How does this help?Record a stable process setup before editing the pipe: save a reliable checkp
OverviewCards that repeat, like recurring requests or similar tasks, can now be duplicated directly in Pipefy. The feature is already available to all accounts and removes the need to rebuild a card from scratch every time the process repeats. What's new? Duplicate card: open any card, click the menu in the top right corner and select Duplicate (only visible to users with permission to create cards in that pipe). Choose the copy scope: decide whether to copy only the start form fields, or all fields and card attributes, including assignees, labels, and due dates. Duplicated cards always land in the first phase: every card created through duplication automatically starts in the pipe's first phase, following the normal process flow. First version limitation: for now, attachments and connections are not duplicated, with the exception of connection fields. How does this help?Cuts repetitive typing: reuse data you already entered instead of rebuilding a similar card from scratch. Keeps the
OverviewYou can now process thousands of cards and records at once through the Pipefy Piece, without building loops to handle each item individually inside a flow. The new batch operations cover both sending data into Pipefy and exporting information from a pipe or database into a single file, making integrations, migrations, and initial data loads much faster. What's new?Batch Upsert: send a CSV or JSON file to create or update thousands of cards or records in a single operation. Use up to 3 combined fields to identify existing items, or match by ID or title, and choose whether unmatched items should be created or skipped. Batch Export: export all cards from a pipe or records from a database into a single CSV or JSON file. Use a saved report or an advanced filter to define what gets exported, and choose which columns are included. Processing tracking: track the status of each batch operation and access a row-level error report, reprocessing only the rows that failed without re-uploadi
OverviewWe've upgraded the automations engine behind Pipefy Integrations. Most of the work happens behind the scenes, but it translates into more reliable flows, clearer error messages, better performance, and a more up to date set of connectors. What's new?Clearer action labels: actions now show whether they read, search, write, or delete data, with delete actions highlighted in red. Cleaner step forms for HTTP Request, Google Sheets, and Custom API Call. Automations are sorted alphabetically, with friendly messages instead of blank screens when something fails to load. Over 270 updated connectors, including QuickBooks Desktop, HubSpot Private App token, and a new Google Drive trigger. Subflows scheduled for retry no longer cause the parent flow to fail. OAuth2 connections with special characters can now be saved correctly. Publishing a scheduled flow no longer breaks its schedule. Older flows and templates can be imported without errors. Large flows run faster and lighter. Newly inst
OverviewAI Agents now show you what they cost to run, before and after execution. You get an AI Credits estimate when testing a behavior, and the real consumption broken down by node once the agent runs, giving you full visibility into the cost of every configuration. What's new?Test Behavior cost estimate: see how many AI Credits a tested configuration would use before publishing it. Testing does not consume AI Credits. Execution Summary: see the total AI Credits consumed by each agentic run, right in the Summary. Cost per node: understand how AI Credits were distributed across individual execution nodes. How does this help?Safer configuration decisions: test an agent's behavior and see the estimated cost before pushing it to production, without spending any AI Credits. Predictable consumption: track the real cost of each execution in the Summary, no manual math required. Spotting expensive nodes: see exactly which node is consuming the most AI Credits and adjust the agent's configura
OverviewTeams can now give more people visibility into AI Agents without granting Pipe admin access. Admins can turn on, per Pipe, view only access to Agents and their execution history, without granting permission to create, edit or delete Agents. What's new?Permission configurable per Pipe, under Pipe Settings › AI Features View only access to AI Agents: members can inspect an Agent's configuration without permission to change it Access to Agent Logs: members can review execution history, including prompts, field values, knowledge base chunks and raw outputs Off by default: access is only granted when a Pipe Admin explicitly enables it, and it applies only to that Pipe How does this help?More visibility, less risk: more people can diagnose an Agent's behavior without expanding admin access on the Pipe Faster troubleshooting: whoever needs to investigate an execution sees prompts, fields and outputs right in the Pipe, without depending on an Admin for every lookup Protected configurat
OverviewMap now opens faster, showing only the first layer of connections, and you expand the rest on demand. On top of that, it now shows how many cards actually moved through each connection, so it is easy to see which connections carry the process and which ones are leftovers nobody uses anymore. What's new?Map now loads only the first layer of connections when it opens, regardless of how complex the process is. Pipes and databases with further connections are marked with a plus sign, showing you where there is more to explore. Clicking a marked pipe or database expands its connections directly on screen, without reloading the whole map. Pipe, database, and connection type filters still apply to everything on screen, including anything you expand. The Layers filter has been replaced by click to expand: to see more connections, look for marked pipes and databases and click them. The Card volume button, in the toolbar at the bottom of Map, turns on the card count per connection with o
OverviewFlows that depend on many manual conditions get harder to maintain as a process changes, and every new scenario means another rule to configure and review. This Pipefy Integrations update focuses on cutting that kind of manual work in the builder, adding authentication options aligned to corporate security standards, expanding the actions available in connectors you already use day to day, and fixing behaviors that caused data loss or slowdowns while building flows. What's new?AI Router: a new routing option available in the step configuration. Instead of building a condition for every scenario, you write a single question and AI decides which branch of the flow to follow. Clearer configuration forms: labels, fields, and validation were revised across pieces such as Slack, Google Drive, Google Docs, Google Calendar, Airtable, Tables, PDF, File Helper, Math Helper, Discord, WordPress, Pinterest, Delay, and Manual Trigger. Slack for multiple users: you can now send the same messa
OverviewMap now recognizes a new connection type: AI Agents. It maps the connections your AI Agents create between pipes and databases, bringing agent activity into the process view. What's new? AI Agents on the map: when an AI Agent creates cards in another pipe or database, that connection now appears as its own type, visually distinct from the rest. A more complete picture: alongside connections, automations, field connections and integrations, AI Agents round out the full view of how a pipe connects. Filter for agents only: the connection type filter now includes AI Agents, so you can isolate them when needed. Nothing to set up: AI Agent connections show automatically for any pipe that already has them. How does this help?Full visibility into AI driven automation: you see exactly where an AI Agent is creating cards in other pipes or databases, without having to infer it from manual automations. Faster dependency diagnosis: isolating the AI Agents filter lets you quickly spot which
OverviewThe Pipefy Integrations engine has received an update that strengthens three areas: credential security, stability during high-volume operations, and an optimized build and debugging experience. What's new?Variables Manager: your credentials are now stored as encrypted variables and referenced inside your steps. Values like `client_id`, `client_secret`, and tokens no longer appear in logs or in the Code step. Better handling of large flow runs: when a flow produces a very high volume of data, that output is now stored outside the main database. Heavy flows keep running smoothly, with no slowdown. Brand-new testing panel: a redesigned testing experience with Split and Drawer modes, Friendly View outputs, and one-click step testing right from the Canvas. A more stable engine, with clearer error messages: when a step fails, you get a clear description of the error and a shortcut that takes you straight to the step that broke. How does this help?Credentials out of logs and Code: se
OverviewCompany Overview gains three capabilities that give admins a direct read on who uses Pipefy, how licenses are distributed, and how much AI is being consumed. You track users by status and role, see AI credit consumption almost instantly in Single Tenant structures, and export API usage reports with a single click. What's new?Users Usage Stats: a dedicated user view inside Company Overview, available in the Users tab. It shows the total number of users across the ecosystem, the split between paid and free users, users inactive for more than 60 days, and distribution by role. Near real-time AI credit usage charts for Single Tenant: credit consumption by agents and assistants now appears almost instantly in Single Tenant structures too, in the same AI monitoring panel. API export available to everyone: the API usage export button is now available across the enterprise base. You download the consumption report with a single click, straight from the API visibility panel. How does th
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.