How does OCNORA authenticate with AWS Cost Explorer?

With a stored API key credential, shaped {"access_key_id", "secret_access_key"}. A connection test can check it when you add it.

What can I automate with AWS Cost Explorer?

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

What if the AWS Cost Explorer operation I need is not listed?

Where AWS Cost Explorer 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 AWS Cost Explorer?

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

How are AWS Cost Explorer 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.

AWS Cost Explorer

Amazon Web ServicesAPI keyConnection test available

Query AWS spend by period and dimension (SigV4).

OCNORA ships 2 typed AWS Cost Explorer 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 AWS Cost Explorer

Before you connect AWS Cost Explorer

Authentication: API key
Credential: {"access_key_id", "secret_access_key"}
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 AWS Cost Explorer

Operations, grouped by what they do to your data.

Read and search 1

Get Cost

Other operations 1

Write Action

A sample AWS Cost Explorer workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Cost Explorer trigger is needed.
2
Get Costcost_explorer.get_cost_and_usage
Query AWS spend over a date range.
3
Write Actioncost_explorer.call
Run one of 16 write actions on Cost Explorer.

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 2