How does OCNORA authenticate with AWS User Notifications?

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 User Notifications?

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

What if the AWS User Notifications operation I need is not listed?

Where AWS User Notifications 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 User Notifications?

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

How are AWS User Notifications 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 User Notifications

Amazon Web ServicesAPI keyConnection test available

Read list notification configurations, list event rules from Notifications (SigV4).

OCNORA ships 3 typed AWS User Notifications 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 User Notifications

Before you connect AWS User Notifications

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 User Notifications

Operations, grouped by what they do to your data.

Read and search 2

Other operations 1

Write Action

A sample AWS User Notifications workflow

1
A core trigger
Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS User Notifications trigger is needed.
2
List Event Rulesnotifications.list_event_rules
Returns a list of EventRules according to specified filters, in reverse chronological order (newest first).
3
Write Actionnotifications.call
Run one of 20 write actions on Notifications.

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