When process knowledge stays in the head of the person who built it, understanding a connection or investigating a request's path depends on finding that person. With AI Agents acting within the flow, visibility becomes essential to keeping track of operations.
The improvements presented at Pipefy Updates let you follow the same pipe at three levels: the ecosystem, the structure, and the card. You will see how these perspectives work together to assess changes, share process knowledge, and investigate actions, including integrations with external systems.
Understand connections before making a change
A purchasing process might connect to supplier records and other company processes. Before changing the flow, the person maintaining it needs to know which connections exist and what could be affected.
Map displays the pipes and databases connected to a pipe and the connection methods, such as automations, integrations, and connection fields. It respects existing access permissions and does not require a separately configured map to start understanding the ecosystem.
Card Volume adds another question: which connections do cards move through? Line thickness and colors represent volume ranges, while connections with no traffic appear as dashed lines. Counts cover the last 30 days, and hovering over a connection reveals the exact number.
Together, these views help you assess the impact of a change. A busy connection deserves attention because of its volume. A connection with no traffic during the period needs context: it may support an occasional scenario. Map provides evidence for that assessment, while the decision stays with the people who understand the process.
Explore Map and its connections, in Portuguese.
Make the structure clear to the next process owner
Once you understand the surrounding ecosystem, look inside the pipe. Someone taking over a process needs to recognize its phases and what happens automatically between them, even if they were not involved in building it.
Flow View brings the structure into a diagram, including phases, forms, automations, and AI Agents. Instead of mentally piecing these elements together, the team has a visual reference for discussing how the process works.
In the purchasing example, imagine a request has moved to an unexpected phase. Flow View helps locate the relevant automation and understand where it fits in the design. It also supports the transfer of knowledge from the person who built the process to the person operating it.
Other improvements support structural maintenance. The Automations view can be sorted by update time, while the Conditionals Editor displays rules in execution order with explicit AND/OR logic. These capabilities make it easier to read how the process is organized.
Explore Flow View, in Portuguese, and the updated Conditionals Editor, in Portuguese.
Follow who acted on each card
The diagram explains how a process was built. To understand what happened with a particular request, turn to the card Timeline, which brings together its history from creation to the final phase.
Each event identifies whether a person, an automation, or an AI Agent performed the action. A phase change can therefore be connected to its actor, without relying only on the memory of someone who followed the request.
Records also make failed executions and executions with no action visible, with access to logs related to the card. When a request does not advance as expected, this history helps locate the event that needs investigation. During an audit, it distinguishes human actions from automatic ones.
Timeline supports understanding what happened and accessing the records. The team can then use that evidence to investigate the responsible configuration in the appropriate context.
Learn about tracking automations and agents in Timeline, in Portuguese.
Extend visibility to external connections
Monitoring continues when a process connects to other systems. In Pipefy Integrations, credentials are protected with encryption, without needing to appear in code or execution records.
The processing dashboard lets teams filter executions and check statuses, errors, and the queue. Automatic queuing handles excess work during periods of higher volume. In the editor, testing a step with one click shows its result and output, helping validate the connection before continuing to build.
The full screen experience provides more room to work on a flow. Pipefy Connector also lets builders select which data each query returns, so an integration retrieves the information relevant to its purpose.
For a process that queries supplier data, for example, the team can validate an integration step and inspect its output before continuing to build. Credential security, monitoring, and testing become part of the same maintenance routine.
Explore the Pipefy Integrations improvements, in Portuguese, and data selection in Pipefy Connector, in Portuguese.
Work with cards in bulk
When operations need to migrate thousands of requests or send data to a BI tool, bulk operations bring that work together. An import can create or update up to 10,000 cards from a file. Exporting gathers cards into a single file using the selected filters.
This lets teams handle a large update or an extraction for analysis as one operation. The team determines which data should enter the process and which selection is needed for analysis.
From the ecosystem to a request's history
Map, Flow View, and Timeline provide complementary references: what is connected, how the process is built, and who acted on each card. Pipefy Integrations extends this visibility to external connections.
Think of a process you work with and which of those questions needs an answer first.
Keep exploring Pipefy Updates
Return to the event recap or explore the other journeys:
