Recently active topics

OverviewMap is a new way to see how a pipe connects to the rest of your Pipefy environment. Open any pipe, click the Map tab, and instantly see everything it influences and is influenced by: other pipes, databases, connection types, and how many connections exist, all laid out in one clear, navigable picture. What's new?  New Map tab, available right next to the Flow tab on any pipe. A visualization with the open pipe at the center and everything it connects to around it. Connection types and counts, showing not just what connects but how. No setup required: just open the pipe and click Map. How does this help?Faster audits: understand in seconds what a pipe sends, receives, and triggers, without opening process after process. Easier onboarding: when you inherit a process someone else built, you see its dependencies before making any change. Safer change decisions: before editing a field or automation, you see exactly which pipes and databases would be affected. Use cases1. A process a

OverviewWhen you open the detail drawer for an execution in AI Agent Logs, the corresponding row is now highlighted in the list, keeping a clear reference between what you're reviewing in detail and where that execution sits in the list. What's new?  The selected execution's row is visually highlighted in the list whenever the detail drawer is open, in AI Agent Logs. How does this help?Constant visual reference: you can immediately tell which execution you're reviewing, even while switching between the list and the detail drawer. Less rework in long reviews: in long lists of executions, you don't lose track of where you left off when returning to the list. Faster diagnosis: comparing agent decisions across nearby executions becomes more direct, without having to reidentify the row every time you switch context. Most relevant forAI Administrators Operations Teams Support Analysts

OverviewCompany Overview now gives you a proactive view of the companies approaching their usage limits, giving IT Admins more control to anticipate needs and manage the health of the Pipefy ecosystem across the entire organization. What's new?Inside the Usage Stats view, you'll now find:Top limit reaching companies: a dedicated breakdown showing which organizations are closest to hitting their usage thresholds, right inside the usage stats panel. Integration Usage Stats: a dedicated view to track volume, health, and consumption of automated connections across all organizations, in one place. How does this help?Proactive consumption management: spot which companies are close to their limits and plan tier adjustments in advance. Monitor integration health without juggling multiple sources: see volume and consumption of automated connections centralized in a single screen. Make governance decisions backed by real data: adjust tiers, permissions, or internal processes based on actual cons

OverviewTest Behavior lets you simulate the execution of an individual AI Agent behavior directly in the AI Agent Builder, before publishing it to production. You can adjust and validate prompts in a test environment, without affecting real cards or processes. What's new?  Simulate the execution of an individual behavior right from the AI Agent Builder Test prompts before publishing a behavior Validate how a behavior responds to different scenarios Verify the execution flow without impacting production How does this help?Shortens the prompt iteration cycle: validate and refine prompts quickly, without relying on multiple publish cycles Removes production risk: test behaviors without affecting real cards or processes during validation Increases agent reliability: confirm behavior across different scenarios before putting it into real use Use cases1. Support ticket triage agent: before publishing a behavior that classifies tickets by urgency, the Support team uses Test Behavior to simula

OverviewAI Agent Alerts via Webhook delivers real-time notifications for every AI Agent execution in Pipefy, whether it succeeds or fails. You configure a webhook endpoint per pipe and start receiving execution results automatically, with context on what the agent did and why it failed. What's new?AI Agent execution webhook: configure an endpoint via the Pipefy API with the agent.ai_execution event to receive alerts for every execution, both successes and failures. Full execution payload: each notification includes status (success or failed), duration, card and pipe data, and whether the agent performed an action. Detailed failure context: when an agent fails, the payload includes the agent's full reasoning — every step it took and where it stopped, so you can identify the root cause without manual investigation. Filters by status, trigger, and outcome: each webhook can be configured with specific filters, delivering only the relevant alerts for that pipe. Requires Pipe Admin or Servic

OverviewAnthropic is now an available provider in BYOM (Bring Your Own Model). You can connect your own Claude models to Pipefy using your API key and choose which model each AI Agent uses. Companies that already run Claude internally can now power their Pipefy Agents with the same models, under their own credentials. What's new?  Anthropic as a BYOM provider: available in the provider carousel, in the Admin Panel, alongside the existing providers. 3 Claude models available: Haiku 4.5, Sonnet 4.6, and Opus 4.8. Setup by Org Admins: in the Admin Panel, just enter a Name, your API Key, and select the model version. Model selection per Agent Behavior: Pipe Admins choose which Claude model to use in each Behavior, based on what each workflow needs. Full configuration management: create, edit, and delete your Anthropic provider configuration whenever you need. How does this help?Standardize your AI stack: if your company has adopted Claude, your Pipefy Agents run on the same models, with go

OverviewTest Action, already available for Generate with AI automations, now extends to Move Card automations. The test lets you simulate execution against the real pipe configuration and instantly see whether it would pass or fail, with the actual reasons why. No cards are moved and no data changes: it's pure validation before you publish anything. What's new?   Test Action for Move Card automations, available directly from the automation configuration. Click Test Action, select a card for the test, click Run Test, and get the result. Instant pass or fail result, with the exact failure reason: incorrect conditional fields, missing required fields, empty, nonexistent, or archived fields, or incorrect destination phase. How does this help?Confidence to publish: you validate the automation against the real pipe configuration, with no need to simulate in a separate environment. Cuts cascading risk: since Move Card triggers a chain of downstream automations, testing before publishing preve

OverviewContinuing the series of updates for AI Agents, we are introducing a new native action: Create connected card.This functionality significantly expands the orchestration capabilities of AI within Pipefy, enabling agents to not only manage an isolated workflow but also connect multiple processes end-to-end while maintaining full traceability. What’s new?AI Agents can now execute five core actions within the platform:Update card fields Create a card Move card Create a record Create a connected card (New) With this update, agents can create new cards in different pipes and automatically establish a link (connection) to the source card, ensuring that information flows between departments with full visibility. How it helpsCross-process Orchestration: connect distinct workflows, such as Sales and Finance, by creating dependent cards automatically. End-to-End Automation: enables AI to initiate new stages in secondary pipes based on the context of the primary process. Data Traceability:

OverviewThree areas updated in this release: a cleaner, more navigable flow editor, new native integrations, and — the most significant addition — you can now create AI flows and run AI Agents directly inside the Integrations Hub. What changed?Editor and navigationThe action bar (Retry, Move flow) now appears as a floating toolbar when an item is selected More screen space, unified scroll, and sticky headers on the canvas Renaming a connection no longer breaks dependent flows — references now use a stable internal identifier AI Agents in flowsYou can now create AI flows and run AI Agents inside the integrations editor Automation flows can trigger and orchestrate agents directly within the pipelineWe're working to connect AI Pieces directly to Pipefy AI Credits, bringing everything into one unified experience. This is expected to be available in the coming weeks. New integrationsJira Data Center — on-premise support with PAT tokens Gitea — self-hosted Git integration SavvyCal — scheduli

OverviewAs part of our ongoing improvements to the Integrations Hub, we're bringing back the Templates feature — now with more visible entry points integrated into the platform's navigation. What's new?The feature is available in two places in the interface, whether you're just getting started or already have flows set up. Empty state: when you open the Integrations Hub with no flows created, the welcome screen offers a "Use Templates" option directly Flow list: under the "+ Create New" button, "Start from Template" is available at any time How does this help?Reduces setup time: start from a ready-made model instead of building from scratch, using structures that are already validated Makes it easier to discover use cases: explore integrations and automations you might not have considered building on your own Most relevant forNew Integrations Hub users Operations teams Pipe Admins Builders looking to speed up flow creation

OverviewThe API Usage Stats dashboard has been updated to deliver granular visibility into API call consumption. You can now view daily usage through a chart, identify spikes by operation or access token, and project costs before the billing cycle closes — without relying on support tickets or manual log analysis. What's new?Daily column chart displaying consumption for the current month Daily usage averages for cost projection and anomaly detection Filter and group by Operation Name or Access Token — identifying exactly which system, script, or integration is generating each call How does this help?Drastically cuts investigation time: what previously required hours of manual log analysis is now identified visually in seconds Enables frictionless governance: admins audit integrations and correct consumption deviations without opening a support ticket Most relevant forIT administrators managing API integrations Operations leaders with multiple active automations Developers connecting ex

OverviewStarting today, all Personal Access Tokens (PATs) must have a billing organization assigned. This ensures every API call is correctly attributed to the account responsible for the costs with full visibility in the admin dashboard. What's new?New tokens: selecting a billing organization is now a required step at creation Existing tokens: 45-day window for manual configuration; after the deadline, the system assigns an organization automatically API usage is now consolidated per organization in the admin dashboard How does this help?Cost visibility per organization: every API call is attributed to the correct account, with no ambiguity Centralized management for multiple accounts: teams running sub-accounts can consolidate all billing under a single parent organization Simplified auditing: the admin dashboard accurately reflects who consumes what — useful for cost reviews and access governance Use casesIT team managing system integrations via API: with mandatory attribution, each

OverviewAgent Template suggestions in the AI Agents area are now generated by the Agents 2.0 engine. The result: templates more closely aligned with each pipe's context, higher execution capability, and less manual configuration to get a working agent up and running. What's new? Agent Template suggestions are now powered by the Agents 2.0 engine Each template comes pre-configured as an Agent 2.0 — users only need to map specific fields and set triggers to activate How does this help?Faster time to first active agent: pre-configured templates reduce setup effort Suggestions matched to the pipe's context: the engine reads the pipe's taxonomy and returns up to 6 relevant templates Use casesAutomatic triage in HR processes: an admin creates an onboarding pipe and receives a suggested agent that classifies incoming documents by type and routes them to the correct stage — no manual automation rules needed SLA monitoring in IT/ITSM operations: the agent suggested for a service desk pipe track

OverviewYou can now duplicate any chart directly from the dashboard surface in a single action. The duplicated item retains all original configurations — filters, metrics, layout — and is ready for immediate adjustments. No rebuilding required. What's new?  Duplicate option available directly from the chart menu on the dashboard Duplicated item inherits all original settings (filters, metrics, groupings) Available now, no additional setup required How does this help?Eliminates the rebuild-from-scratch effort for recurring reports that require only minor variations Reduces manual work involved in building and maintaining operational dashboards Makes it easy to create multiple versions of the same chart by adjusting only the parameters that matter Use casesWeekly report with team-level variation — duplicate a ticket volume chart, swap the department filter, and publish separate versions for each team without starting over. Period-over-period comparison — duplicate a lead time chart, adju

OverviewAdmins and Super Admins can now set every new pipe created in the organization to be private by default. The toggle lives under Organization Settings > General Settings and takes effect immediately for new pipes — no manual adjustment needed at creation time. What's new?  New toggle in General Settings (visible to Admins and Super Admins only) Every pipe created from scratch or cloned from the Template Store defaults to "Private to invited members" Organization members can see the pipe exists in the list but cannot access it without an invite Internal cloning respects the original pipe's existing permission settings Previously created pipes are not affected when the toggle is activated How does this help?Eliminates accidental exposure of sensitive data at the moment of pipe creation — the most common human error in high-volume environments Moves privacy control to the organizational layer, removing reliance on individual judgment at creation time Reduces compliance risk surf

OverviewAI Agents can now send emails directly from automated workflows using pre-configured templates. The action includes an intelligent content adjustment toggle, allowing the agent to adapt the email body based on card fields and execution context, without compromising brand consistency or template structure. What's new?AI Agents now support six actions:Update card fields Create a card Create a connected card Create a record Send an email template (new) Move card  The new action includes the "AI content adjustment" toggle: when enabled, the agent automatically adapts the template content based on the card fields and execution context. How does this help?Closes the loop between automation and human communication: the agent triggers standardized emails at the right process moment, without relying on manual input Preserves brand identity: emails are sent using pre-approved templates, eliminating off-brand or inconsistent messaging Enables human-in-the-loop approval and decision flows:

OverviewAI Agents in Pipefy now support a third knowledge source type: Plain Text. Lightweight business rules, operational instructions, and static context can be added directly in the agent interface, with no file uploads and no database connections required. What's new?  New Plain Text knowledge source option available in agent configuration Text field supports up to 3,500 characters Works alongside existing knowledge source types: Documents / PDFs, Pipes / Databases, and Plain Text (new)  How does this help?Reduces setup friction: simple rules go straight into the agent, no need to create or manage external files Speeds up operational updates: instructions change without any upload workflow or document management overhead Centralizes static knowledge: short policies and exceptions live in the same place where the agent is configured Improves response quality: plain text processes faster and with higher accuracy than equivalent PDFs Use casesCNPJ blocklists in procurement workflows.

OverviewIT admins now have a single place to track everything that happens inside a pipe. Structural configuration changes and card activities are consolidated in one interface, with search, export, and full details on who performed each action and when — no more manually logging changes or opening items one by one. What's new?Inside the Pipe under Manage → Audit Logs:New “Configuration Changes” tab: records structural pipe changes, including AI Agents, automations, phases, fields, field conditionals, connections, members, and permissions Card Activities: key card events consolidated in the pipe log, with no need to open each card individually Resource Type column: identifies the type of resource affected by each event Sortable Time column: sort history chronologically or from most recent to oldest Full actor details: name and email of who performed each action. If the actor is an AI Agent or automation, its name is also shown 180-day history in the interface CSV export: last 30 days o

OverviewPipefy is rolling out a new Text Editor across key areas of the platform. This update brings a unified, modern content creation and editing experience: more consistent, smoother, and visually coherent no matter where you're working inside Pipefy. What's new?  New Text Editor in Portal and Interface text elements: edit instructions, descriptions, and text content through a refreshed, cleaner, and more responsive interface New Text Editor in Dynamic Fields inside Pipe phases: create and format content in dynamic fields with the same modern experience now available across the rest of the platform How does this help?Faster content creation flow: less friction when formatting instructions, descriptions, and field text inside your processes Most relevant forBuilders and Pipe admins Operations managers maintaining active flows IT, HR, and Procurement teams running Portals and Interfaces Analysts responsible for internal process documentation Plans and availabilityThis feature is being

OverviewPipefy AI Agents now include a capability that addresses one of the most critical limitations of generative AI in operations: mathematical imprecision. With Calculations & Analysis enabled, agents write and execute small programs at runtime inside a secure sandbox, delivering absolute accuracy for math, complex business logic, and data extracted from documents.  What's new? Pipe Admins enable this capability directly from the Behaviors tab of any AI Agent. "Calculations & Analysis" capability available in the Behaviors tab of any AI Agent. When enabled, the agent writes and runs code at runtime to process business logic with deterministic precision. Guaranteed mathematical accuracy: invoice totals, conversion rates, cost center splits, and penalty calculations are computed with absolute precision, with no risk of hallucination. Business logic in plain text: rules that previously lived in external spreadsheets or custom integrations can now be described directly in the a

OverviewPipefy AI Agents now connect to the broader AI ecosystem through the Model Context Protocol (MCP). With the simultaneous launch of the MCP Client and MCP Server, your Agents can call external tools directly from within their configured workflows, and Pipefy processes can be exposed as tools to third-party AI interfaces. The practical outcome: complex cross-system workflows that previously required manual coordination between platforms can now be executed entirely through natural language, with governance and traceability kept inside Pipefy. What's new?  MCP Client: enables your AI Agents to call external tools (such as Slack, Salesforce, and others) directly from within workflow behaviors configured in Pipefy, without leaving the platform. MCP Server: exposes Pipefy processes as tools that MCP-compatible AI interfaces (such as Claude Code, Cursor, and similar) can access and execute through natural language. How does this help?Eliminates silos between critical systems: your Age

OverviewAutomations now has a dedicated page in the Pipe header, right next to AI Agents. The update brings more visibility and control to anyone managing automation rules: you can navigate, search, and share automations directly, without going through intermediate menus. What's new?  Automations as a top-level page. Accessible directly from the Pipe header, next to AI Agents. This dedicated page is now the default way to manage automations. Card view. Cards that display the Event, Action, last updated date, and who last edited, so you understand what each automation does without opening it. Table view. A compact, scannable format built for pipes with many automations. Columns: Status, Automation name, Event and Action (with icon chips), Updated, and Updated by. Search, filters, and sorting at the header level. Find any automation quickly with the search bar and filters available right at the top of the page. New automation button front and center. The creation action is always visible

We are beginning the rollout of Web Search for AI Agents in Pipefy, with gradual availability throughout the month of March. OverviewWith this feature, agents can consult external information in real time to enrich decisions, validate data, and complement processes — expanding their capabilities beyond the internal information available in the pipe. What is Web Search?Web Search is an advanced tool that allows Pipefy AI Agents to perform internet searches to collect up-to-date information and context that are not available within your process.When this feature is enabled, the AI Agent can:Search for updated information on the internet Complement decisions with public data Populate fields based on external sources To activate it, access your agent in the pipe, go to the Behaviors tab, and enable the Web Search option.​​​​​ How does this help?Bring external context: allows the agent to validate information or retrieve complementary data from the web in real time. Eliminate information si