How does OCNORA authenticate with Amazon Forecast Query Service?

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 Amazon Forecast Query Service?

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

What if the Amazon Forecast Query Service operation I need is not listed?

Where Amazon Forecast Query Service 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 Amazon Forecast Query Service?

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

How are Amazon Forecast Query Service 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.

Amazon Forecast Query Service

Amazon Web ServicesAPI keyConnection test available

Read query forecast, query what if forecast from forecastquery (SigV4).

OCNORA ships 2 typed Amazon Forecast Query Service 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 Amazon Forecast Query Service

Before you connect Amazon Forecast Query Service

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 Amazon Forecast Query Service

Operations, grouped by what they do to your data.

Read and search 2

A sample Amazon Forecast Query Service workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Forecast Query Service trigger is needed.
2
Query Forecastforecastquery.query_forecast
Retrieves a forecast for a single item, filtered by the supplied criteria.

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