How does OCNORA authenticate with AWS Step Functions?

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 Step Functions?

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

What if the AWS Step Functions operation I need is not listed?

Where AWS Step Functions 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 Step Functions?

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

How are AWS Step Functions 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 Step Functions

Amazon Web ServicesAPI keyConnection test available

Start and inspect Step Functions executions (SigV4).

OCNORA ships 3 typed AWS Step Functions 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 Step Functions

Before you connect AWS Step Functions

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 Step Functions

Operations, grouped by what they do to your data.

A sample AWS Step Functions workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Step Functions trigger is needed.
2
Describe Executionstep_functions.describe_execution
Read an execution's status and output.
3
Start Executionstep_functions.start_execution
Start a state-machine execution.

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