How does OCNORA authenticate with Amazon Q Connect?

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 Q Connect?

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

What if the Amazon Q Connect operation I need is not listed?

Where Amazon Q Connect 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 Q Connect?

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

How are Amazon Q Connect 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 Q Connect

Amazon Web ServicesAPI keyConnection test available

Read list assistants, list contents, list content associations from QConnect (SigV4).

OCNORA ships 4 typed Amazon Q Connect 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 Q Connect

Before you connect Amazon Q Connect

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 Q Connect

Operations, grouped by what they do to your data.

Read and search 3

Other operations 1

Write Action

A sample Amazon Q Connect workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Q Connect trigger is needed.
2
List Assistantsqconnect.list_assistants
Lists information about assistants.
3
Write Actionqconnect.call
Run one of 55 write actions on QConnect.

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

Amazon Q Connect questions

How does OCNORA authenticate with Amazon Q Connect?: 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 Q Connect?: 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
What if the Amazon Q Connect operation I need is not listed?: Where Amazon Q Connect 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 Q Connect?: Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Amazon Q Connect 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 Amazon Q Connect 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