Overview
Map 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 one click.
- Thicker, darker lines mean more cards were created through that connection.
- Dashed lines mark connections with no cards created in the period.
- The eye icon in the legend hides connections with zero cards, so you can focus on the ones that matter.
- Hovering over a pipe shows the exact number of cards created on each of its connections.
- Card volume counts new cards created already connected through a pipe connection or connection field, in the last 30 days. Connecting an existing card or updating an already connected card does not count. It is a record of what was created, not of what is still connected: if a card is disconnected later, it still counts.
How does this help?
- Much faster opening on complex processes: since only the first layer loads up front, you are not waiting on connections you might not even need in that session.
- Spot connections that might be outdated: old automations, pipes that changed purpose, or connections nobody remembers creating tend to show up as dashed lines, so you know where to start reviewing the process instead of checking every connection one by one.
- See where the process actually flows: thicker, darker lines point to the connections carrying the most traffic, helping you prioritize where it is worth investing in automation or review.
- Targeted exploration with context kept: connection markers show you where to investigate, and expanding does not reload the map, so you keep your position and everything you already explored.
Use cases
Admin auditing a procurement process before simplifying the flow: the admin turns on Card volume on Map for the main pipe and notices a connection to a legacy approval pipe shows up dashed, with no cards created in the last 30 days. They hide zero card connections with the eye icon, use that as the starting point for the review, and check with the process team whether the connection still makes sense before removing it.
Builder checking the impact of a field change before publishing: before changing a connected field in a vendor onboarding pipe, the builder opens Map and immediately sees the first layer of connections. They turn on Card volume, notice one of the marked connections has a thick, dark line, and hovering confirms over two hundred cards were created through it in the period. With that number, they decide to test the change in staging before publishing to production.
Process manager deciding where to invest in automation: opening Map for a customer service process with several connections, the manager turns on Card volume and quickly identifies which connection accounts for the most cards created that month. They direct the team to review that automation first, instead of spreading effort evenly across connections that are barely used.
Implementation consultant running a discovery session with a customer: during the session, the consultant opens Map for a core process and expands only the pipes the customer asks about, since the initial load is fast even in large workspaces. They turn on Card volume to show the customer, with real numbers, which connections carry the process today and which were created in past projects and no longer receive cards.
Most relevant for
- Pipe Admins
- Builders
- Process managers
- Implementation consultants
Plans and availability
This feature is being rolled out gradually to all accounts.
