List Constraints

org_policy.list_constraints
ActionGoogle Cloudconnection required

Calls Organization Policy GET /v2/projects/{projectsId}/constraints.

Lists constraints that could be applied on the specified resource.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Organization Policy
Secret shape
{"client_id", "client_secret", "refresh_token"}
Config it needs
project_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
page_size
Size of the pages to be returned.
numberNo50≥ 1—
page_token
Page token used to retrieve the next page.
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "page_size": 50
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
constraints
array—
nextPageToken
string—
{
  "constraints": [],
  "nextPageToken": "",
  "ok": false
}

See List Constraints run in a workflow.

In a technical demo we add the Google Organization Policy connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.