How does OCNORA authenticate with Google Cloud IDS?

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 Cloud IDS?

5 typed operations, each with a reference page listing its config fields and the shapes it emits.

What if the Google Cloud IDS operation I need is not listed?

Where Google Cloud IDS 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 Cloud IDS?

Not yet. Start from a blank workflow, or describe the workflow to Build with AI.

How are Google Cloud IDS 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.

Google Cloud IDS

Google CloudOAuth 2.0Connection test available

Cloud IDS (Cloud Intrusion Detection System) detects malware, spyware, command-and-control attacks, and other network-based threats (Google OAuth2).

OCNORA ships 5 typed Google Cloud IDS 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.

Ask about Google Cloud IDS Google Cloud IDS API docs ↗

Before you connect Google Cloud IDS

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 Cloud IDS

Operations, grouped by what they do to your data.

Create and send 1

Create Endpoint

Read and search 2

Update 1

Update Endpoint

Delete and cancel 1

Delete Endpoint

A sample Google Cloud IDS workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud IDS trigger is needed.
2
Get Endpointcloud_ids.get_endpoint
Gets details of a single Endpoint.
3
Create Endpointcloud_ids.create_endpoint
Creates a new Endpoint in a given project and location.

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 5

Google Cloud IDS questions

How does OCNORA authenticate with Google Cloud IDS?: 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 Cloud IDS?: 5 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Google Cloud IDS operation I need is not listed?: Where Google Cloud IDS 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 Cloud IDS?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Google Cloud IDS 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 Cloud IDS 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.

Book a technical demo Talk to sales