How does OCNORA authenticate with Terraform Cloud?

With a stored Bearer token credential, shaped the API token, or {"token": "…"}. A connection test can check it when you add it.

What can I automate with Terraform Cloud?

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

What if the Terraform Cloud operation I need is not listed?

Where Terraform Cloud 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 Terraform Cloud?

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

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

Terraform Cloud

Business appsBearer tokenConnection test available

Queue and apply runs on Terraform Cloud / HCP Terraform workspaces.

OCNORA ships 4 typed Terraform Cloud 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 Terraform Cloud

Before you connect Terraform Cloud

Authentication: Bearer token
Credential: the API token, or {"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 Terraform Cloud

Operations, grouped by what they do to your data.

Create and send 1

Queue Run

Read and search 2

Update 1

Apply Run

A sample Terraform Cloud workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Terraform Cloud trigger is needed.
2
Get Runterraform_cloud.get_run
Fetch one run's status.
3
Apply Runterraform_cloud.apply_run
Confirm-and-apply a run awaiting approval.

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 4

Terraform Cloud questions

How does OCNORA authenticate with Terraform Cloud?: With a stored Bearer token credential, shaped the API token, or {"token": "…"}. A connection test can check it when you add it.
What can I automate with Terraform Cloud?: 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Terraform Cloud operation I need is not listed?: Where Terraform Cloud 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 Terraform Cloud?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Terraform Cloud 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 Terraform Cloud 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