Product Updates

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 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

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

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

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

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

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

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

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

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

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