Overview
Map shows, starting from the pipe you have open, everything it connects to. With this update, those connections now include your iPaaS integrations too, a new connection type alongside pipe, automation, and field connections. So in one place, you see which pipes exchange data with other pipes and databases via integration. And loading is faster, even on pipes with many connections.
What's new?
- Integrations on the Map: your iPaaS connections now appear as their own connection type, next to your pipe, automation, and field connections.
- Faster loading: densely connected pipes stay smooth and legible, even on maps with many elements.
- Which flows appear: the Map shows integrations on the connections between two pipes or databases. An integration flow appears when it touches at least two of them. Flows that only read from or write to a single pipe, such as a Pipefy to Slack alert, will not appear.
How does this help?
- You see the real process, not what you remember of it: integration flows appear alongside the design, without opening each recipe separately.
- Dependencies become visible before you make a change: you can tell which integrations touch a pipe before editing phases or fields.
- Auditing and maintenance get simpler: it's clear which pipes and databases are connected via integration.
Use cases
1. A Pipe Admin auditing Accounts Payable. The process receives invoices from an external ERP via iPaaS and returns payment status. On the Map, the admin sees the integration connection between the payments pipe and the vendors database and spots dependencies before changing any field.
2. A Builder documenting employee Onboarding. The flow integrates the hiring pipe with the roles database and an external HR system. The Map immediately shows which iPaaS connections exist, and the builder records the real design without relying on memory or a side spreadsheet.
3. An Operations team planning a change to Procurement. Before restructuring phases, the team checks the Map to see which integrations touch the quotes pipe and the orders pipe, and measures the change's impact before executing it.
Most relevant for
- Pipe Admins
- Builders
- Operations teams
- IT Leaders
