Inspect Content
dlp.inspect_content
ActionGoogle Cloudconnection required
Calls Sensitive Data Protection (DLP) POST /v2/projects/{projectsId}/content:inspect.
Finds potentially sensitive info in content. This method has limits on input size, processing time, and output size.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Sensitive Data Protection (DLP)
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
body Request body (GooglePrivacyDlpV2InspectContentRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
result | object | — |
{
"ok": false,
"result": {}
}Related Google Sensitive Data Protection (DLP) nodes
See Inspect Content run in a workflow.
In a technical demo we add the Google Sensitive Data Protection (DLP) connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.