How does OCNORA authenticate with Argo CD?

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

What can I automate with Argo CD?

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

What if the Argo CD operation I need is not listed?

Where Argo CD 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 Argo CD?

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

How are Argo CD 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.

Argo CD

Business appsBearer tokenConnection test available

List and sync Argo CD applications.

OCNORA ships 3 typed Argo CD 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 Argo CD

Before you connect Argo CD

Authentication: Bearer token
Credential: the auth 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 Argo CD

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Sync Application

A sample Argo CD workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Argo CD trigger is needed.
2
Get Applicationargocd.get_application
Fetch one application.
3
Sync Applicationargocd.sync_application
Trigger a sync (optionally pruning).

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 3

Argo CD questions

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