Google Policy Simulator
Policy Simulator is a collection of endpoints for creating, running, and viewing a Replay (Google OAuth2).
OCNORA ships 6 typed Google Policy Simulator 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 Policy Simulator
- 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 Policy Simulator
Operations, grouped by what they do to your data.
A sample Google Policy Simulator workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Policy Simulator trigger is needed.
- 2Get Org Policy Violations Previewpolicy_simulator.get_org_policy_violations_previewGetOrgPolicyViolationsPreview gets the specified OrgPolicyViolationsPreview.
- 3Create Org Policy Violations Previewpolicy_simulator.create_org_policy_violations_previewCreateOrgPolicyViolationsPreview creates an OrgPolicyViolationsPreview for the proposed changes in the provided OrgPolicyViolationsPreview.OrgPolicyOverlay.
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 Org Policy Violations PreviewCreateOrgPolicyViolationsPreview creates an OrgPolicyViolationsPreview for the proposed changes in the provided OrgPolicyViolationsPreview.OrgPolicyOverlay.policy_simulator.create_org_policy_violations_preview
- Create ReplayCreates and starts a Replay using the given ReplayConfig.policy_simulator.create_replay
- Get Org Policy Violations PreviewGetOrgPolicyViolationsPreview gets the specified OrgPolicyViolationsPreview.policy_simulator.get_org_policy_violations_preview
- Get ReplayGets the specified Replay. Each Replay is available for at least 7 days.policy_simulator.get_replay
- List Org Policy Violations PreviewsListOrgPolicyViolationsPreviews lists each OrgPolicyViolationsPreview in an organization. Each OrgPolicyViolationsPreview is available for at least 7 days.policy_simulator.list_org_policy_violations_previews
- List ResultsLists the results of running a Replay.policy_simulator.list_results
Google Policy Simulator questions
- How does OCNORA authenticate with Google Policy Simulator?
- 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 Policy Simulator?
- 6 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Policy Simulator operation I need is not listed?
- Where Google Policy Simulator 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 Policy Simulator?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Policy Simulator 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 Policy Simulator 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.