Amazon SQS

Amazon Web ServicesAPI keyConnection test available

Send and receive messages on Amazon SQS (SigV4).

OCNORA ships 3 typed Amazon SQS 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.

Before you connect Amazon SQS

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 SQS

Operations, grouped by what they do to your data.

Create and send 1

Read and search 1

Other operations 1

A sample Amazon SQS workflow

  1. 1
    A core trigger
    Start the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon SQS trigger is needed.
  2. 2
    List Queuessqs.list_queues
    List the SQS queues in the connection's region, optionally filtered by name prefix. Account-level, so it does not need a queue_url.
  3. 3
    Receive Messagessqs.receive_messages
    Receive messages from an AWS SQS queue.

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.

Amazon SQS questions

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