Estimated reading time: 4 minutes
👤 For admins, super admins
🔐 Available on all plans
🎯 Anyone who needs to understand how a process relates to other pipes and databases.
How to access it
Open any pipe.
Click Map.
How to read the Map
The pipe you opened appears with the You are here tag. Everything connected to it shows up around it.
The Map reads from left to right, following the arrows: what's on the left is where the process comes from (what feeds your pipe); what's on the right is where the process goes (what your pipe feeds). That way you can see the full path, from start to finish.
The three types of connection
Every line on the Map has an icon that shows how that connection happens. Click the icon to see its details and jump straight to its settings:
Connection: a connection created manually in Connections > Manage connections.
Automation: a connection created through an automation.
Connection field: a connection created through a connection-type field.
Two pipes can have more than one connection at the same time, and each one shows up with its own icon.
Adjust what you want to see
When a pipe has a lot of relationships, the Map gets big. Use the filters to focus on exactly what you want to see at the moment.
Layer depth
Controls how far the Map reaches from where you are. Think of it as rings around your pipe:
1 level: shows only the direct neighbors — the pipes and databases connected directly to your pipe.
2 levels: shows the neighbors of your neighbors, one hop further out.
3 levels: shows the neighbors of your neighbors' neighbors, the farthest the Map goes.
Elements
Filters which connections appear on the Map.
By object:
Pipes: shows only the connected pipes.
Databases: shows only the connected databases.
By type:
Automations: shows all connections created by an automation.
Connection fields: shows all connections created through a connection field.
Connections: shows all connections created manually in Connections.
You can combine filters to zero in on exactly what you want to analyze — for example, showing only the databases connected through a connection field.
Everyday ways to use the Map
The Map is built for the moments when you need to understand the bigger picture, not just what happens inside a single pipe. The most common ones are:
You inherited a process you didn't build. You took over a pipe, joined a new team, or picked up someone else's process. Instead of opening pipe after pipe to figure out where cards come from and where they go, the Map gives you the whole chain at once.
You're about to change something and don't want to break anything. Before editing or deleting a pipe, a field, or an automation, the Map shows you what depends on it. It's the quick answer to "who else will feel it if I change this?" — and the end of post-change surprises.
A card showed up out of nowhere in another pipe. Click the connection in question and go straight to the automation or field that created it. No need to open five screens to investigate.
You want to see the whole architecture. Whether you're documenting your processes, simplifying what got too complex, or spotting orphaned and redundant connections, the Map pulls everything together onto a single surface.
Have feedback?
We'd love to hear from you. Use the Send feedback button inside the Map to tell us what's working, what isn't, and what you'd like to see next.
