How does OCNORA authenticate with Amazon Lex Runtime 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 Lex Runtime Service?

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

What if the Amazon Lex Runtime Service operation I need is not listed?

Where Amazon Lex Runtime 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 Lex Runtime Service?

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

How are Amazon Lex Runtime 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 Lex Runtime Service

Amazon Web ServicesAPI keyConnection test available

Read get session from Lex Runtime Service (SigV4).

OCNORA ships 2 typed Amazon Lex Runtime 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 Lex Runtime Service

Before you connect Amazon Lex Runtime 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 Lex Runtime Service

Operations, grouped by what they do to your data.

Read and search 1

Get Session

Other operations 1

Write Action

A sample Amazon Lex Runtime Service workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Lex Runtime Service trigger is needed.
2
Get Sessionlex_runtime.get_session
Returns session information for a specified bot, alias, and user ID.
3
Write Actionlex_runtime.call
Run one of 4 write actions on Lex Runtime Service.

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