On July 8, 2026, Make shipped an update that most people will scroll past. It is the kind of feature that does not sound exciting until you have lived through the problem it solves. Make Grid — the visual dependency map that shows how your scenarios connect to each other — now pulls in workflows from n8n, Claude Managed Agents, and Relevance AI. Your Make scenarios, your n8n automations, your AI agents, all in one map.
If you run a single automation platform, this does not matter to you. But if you are like most teams I talk to, you have at least two. Maybe you started with Zapier for simple zaps and added n8n for the complex stuff. Maybe your dev team runs n8n self-hosted while the marketing team lives in Make. Maybe someone spun up a Claude Managed Agent for customer support and nobody documented how it connects to the rest of the stack. The automation sprawl is real, and until now, nobody could see the full picture without opening four browser tabs and drawing the connections on a whiteboard.
The problem nobody talks about
Automation tools are easy to start and hard to audit. A founder spins up a Make scenario to sync Stripe to QuickBooks. Six months later, a developer adds an n8n workflow that also touches Stripe webhooks. A marketing lead connects a Claude agent to the support inbox. Each tool works fine in isolation. The problem is that nobody has a single view of how data flows across all of them.
This is the "automation blind spot" — the gap between what each tool knows about itself and what the organization knows about its entire automation estate. When something breaks, you spend an hour tracing data through three different platforms before you find the scenario that changed a field name and broke the downstream webhook. When a compliance officer asks where customer data goes, you give a partial answer because you genuinely do not know every path.
Make Grid's cross-platform connectors close that blind spot. You connect your n8n instance, your Claude Managed Agent workspace, and your Relevance AI account, and Grid maps them all into a single dependency graph. You can see which Make scenario feeds data into which n8n workflow, which n8n workflow triggers a Claude agent, and which Claude agent writes back to a database that a Make scenario reads from.
What you can actually do with it
The feature set is practical, not flashy. Here is what landed on July 8.
Unified map. Every scenario, workflow, and agent from every connected platform shows up in one Grid view. You do not need to switch contexts. If your Make scenario sends a webhook to an n8n workflow, Grid draws the connection. If your n8n workflow calls a Claude agent via API, that shows up too.
Dependency tracing. Click on any node — a Make scenario, an n8n workflow, or a Claude agent — and Grid shows you everything upstream and downstream. Before you modify a database schema or rename a webhook endpoint, you can see exactly what will break. This is the feature that saves you from the 2 AM "why is the CEO's dashboard empty" Slack message.
AI and PII exposure mapping. Grid can highlight where personal data flows through your automations. If a Make scenario passes customer email addresses to an n8n workflow that sends them to a Claude agent, you can see that path. For anyone dealing with GDPR, CCPA, or just basic data hygiene, this is the kind of visibility that used to require a dedicated audit project.
Usage tracking by provider. Turn on Grid layers to see credit or unit consumption per provider. If your n8n executions spiked last week, Grid can connect that spike back to the specific workflow that started running ten times more often. If your Claude agent is burning through API credits, you can see which scenario is feeding it the most requests.
Cross-platform search. Search for a specific application, webhook URL, or ID across every connected platform at once. Instead of opening Make, n8n, and Relevance AI separately and searching each one, you type a query into Grid and get every reference across your entire stack.
Private spaces landed the same week
On July 17, Make shipped another feature that pairs well with the Grid update: Private Spaces. Previously, every scenario and connection in a Make organization lived in a shared workspace visible to all teammates. Private Spaces gives each member their own isolated space for scenarios and connections they do not want others to see.
The practical use case is straightforward. A contractor spins up a scenario in their private space using their own API keys. The org admin can set credit limits for that space and, on Enterprise plans, view the scenario names and modules used without seeing the actual connection credentials. When the contractor leaves, their private space goes with them, and the shared workspace stays clean.
Private Spaces are available on all Make plans. Admin visibility into private spaces requires Enterprise. This is not a feature most solo users will care about, but for agencies and teams with external collaborators, it solves a real access control problem that previously required workarounds like separate Make organizations.
The bigger picture: Make as the observability layer
The strategic play here is not subtle. Make is positioning Grid not just as a Make feature, but as a cross-platform automation observability tool. If Grid can map Make scenarios, n8n workflows, Claude agents, and Relevance AI assets, the logical next step is adding Zapier, custom webhooks, and other AI platforms. The endgame is a tool where you can see your entire automation estate — every trigger, every transformation, every API call — regardless of which platform runs it.
This matters because the automation market is consolidating around a handful of platforms, and most organizations use more than one. The old model — pick one tool and commit — is dying. The new model is polyglot automation: use Make for visual workflows, n8n for complex logic and AI agents, Zapier for the long tail of SaaS integrations, and purpose-built AI agents for specific tasks. The missing piece has always been a way to see how they all connect. Make is betting that Grid can be that layer.
What to do right now
If you run Make and at least one other automation platform, connect it to Grid. The n8n integration requires your n8n instance URL and an API key. Claude Managed Agents connects through an Anthropic API key. Relevance AI has its own connector. Setup takes about fifteen minutes per platform.
If you are on a Make plan that supports Private Spaces and you have external collaborators, enable it. The credit controls alone are worth the five minutes of configuration.
And if you have been putting off documenting your automation architecture — who connects to what, where data flows, which webhooks depend on which — Grid just did most of that work for you. Open it, take a screenshot, and share it with your team. The whiteboard approach to automation documentation was always a stopgap. This is better.
Sources: Make Help Center — July 2026 releases, Make Grid cross-platform connectors, Make Private Spaces