Deidentify Content

dlp.deidentify_content

ActionGoogle Cloudconnection required

Calls Sensitive Data Protection (DLP) POST /v2/projects/{projectsId}/content:deidentify.

De-identifies potentially sensitive info from a ContentItem. This method has limits on input size and output size.

Ask about Google Sensitive Data Protection (DLP)All Google Sensitive Data Protection (DLP) nodes Provider API docs ↗

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 (GooglePrivacyDlpV2DeidentifyContentRequest) as JSON.	object	No	—	—	—

Output

One shape.

result

Field	Type	Example
ok	boolean	—
overview	object	—
item	object	—

{
  "item": {},
  "ok": false,
  "overview": {}
}

Related Google Sensitive Data Protection (DLP) nodes

See Deidentify 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.

Book a technical demo Talk to sales