Introduction

UnifyApps connects to n8n and returns the agents that account hosts, so they can be inventoried, monitored and brought under policy alongside every other platform you run.

n8n hosts automation workflows. The sweep reads each workflow and returns every AI Agent node it contains as an agent, so a connection that returns nothing usually means no workflow contains an AI Agent node.

What UnifyApps discovers

Discovery reads the platform's own APIs through a connection your tenant already holds. Each agent it returns becomes a record in the Agent Registry, and the traces those agents produce are collected from that point on.

Capability support

Note: n8n traces need instrumentation. A sweep finds the AI Agent nodes inside your n8n workflows, but traces only arrive once n8n is instrumented: run n8n from the custom Docker image with instrumentation.js, as described on the agent's Setup tab, then generate an API key there. Until then the agent stays Setup Pending.

Before you begin

1. Create the connection first — Discovery sweeps a connection your tenant already holds. It does not collect credentials. See Create a Connection.

2. Know which account or environment you are scanning — One connection covers one. Separate production and test environments need one connection each.

3. Agree the identity's scope — Discovery sees exactly what the connection identity can list. A narrow identity produces an inventory that looks complete and is not.

Add the connection

Step 1: Open + Add Application in Discovery

Step 2: Select n8n

Step 3: Choose the connection type

Observe · Advisory is selected by default. You can choose Control · Enforced instead if you want Block and Mask to take effect.

Step 4: Choose the connection and click Connect

Verify

The new row shows PLATFORM as n8n and STATUS as Connected. DISCOVERED populates once the first sweep completes.

Open the connection to see its Assets table. Everything arrives Excluded — discovered but not governed — until you register it. See Register Discovered Agents.

Limitations

1. Actions depend on the tier you choose — On Observe · Advisory only Flag takes effect. On Control · Enforced, Block and Mask take effect too.

2. Coverage stops at the connection's permissions — Assets the identity cannot list will not appear, and their absence is not reported.

3. An empty sweep is common and often correct — Only AI Agent nodes inside workflows are returned. Confirm against the instance before treating an empty result as a fault.

Troubleshooting

The sweep completed but DISCOVERED is empty. Either the account genuinely hosts none, or the connection identity cannot list them. Check the second before concluding the first.

Fewer assets than the platform's own console shows. Scope. Confirm the connection covers the whole boundary you intend to govern.

Assets appear but never accumulate traces. Check LAST TRACE against known usage before treating it as a telemetry fault.

A Block control never blocks. Expected on an Observe · Advisory connection — check the connection type. See Connection Types.