How does OCNORA authenticate with HashiCorp Consul?

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

What can I automate with HashiCorp Consul?

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

What if the HashiCorp Consul operation I need is not listed?

Where HashiCorp Consul 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 HashiCorp Consul?

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

How are HashiCorp Consul 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.

HashiCorp Consul

Business appsBearer tokenConnection test available

Catalog, health and KV on Consul.

OCNORA ships 4 typed HashiCorp Consul 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 HashiCorp Consul

Before you connect HashiCorp Consul

Authentication: Bearer token
Credential: the ACL token (optional), 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 HashiCorp Consul

Operations, grouped by what they do to your data.

Read and search 1

List Services

Other operations 3

A sample HashiCorp Consul workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no HashiCorp Consul trigger is needed.
2
List Servicesconsul.list_services
List catalog services.
3
KV Getconsul.kv_get
Read one key from the KV store.

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