Google Sensitive Data Protection (DLP)
Discover and protect your sensitive data (Google OAuth2).
OCNORA ships 6 typed Google Sensitive Data Protection (DLP) operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Sensitive Data Protection (DLP)
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Sensitive Data Protection (DLP)
Operations, grouped by what they do to your data.
Create and send 1
Read and search 2
Delete and cancel 1
Other operations 2
A sample Google Sensitive Data Protection (DLP) workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Sensitive Data Protection (DLP) trigger is needed.
- 2Get Dlp Jobdlp.get_dlp_jobGets the latest state of a long-running DlpJob.
- 3Create Dlp Jobdlp.create_dlp_jobCreates a new job to inspect storage or calculate risk metrics.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 6
- Create Dlp JobCreates a new job to inspect storage or calculate risk metrics.dlp.create_dlp_job
- Deidentify ContentDe-identifies potentially sensitive info from a ContentItem. This method has limits on input size and output size.dlp.deidentify_content
- Delete Dlp JobDeletes a long-running DlpJob.dlp.delete_dlp_job
- Get Dlp JobGets the latest state of a long-running DlpJob.dlp.get_dlp_job
- Inspect ContentFinds potentially sensitive info in content. This method has limits on input size, processing time, and output size.dlp.inspect_content
- List Dlp JobsLists DlpJobs that match the specified filter in the request.dlp.list_dlp_jobs
Google Sensitive Data Protection (DLP) questions
- How does OCNORA authenticate with Google Sensitive Data Protection (DLP)?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Sensitive Data Protection (DLP)?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Sensitive Data Protection (DLP) operation I need is not listed?
- Where Google Sensitive Data Protection (DLP) has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Sensitive Data Protection (DLP)?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Sensitive Data Protection (DLP) calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Sensitive Data Protection (DLP) workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.