AWS SQS
AWS SQS queue messaging
AWS SQS (Simple Queue Service) is the AWS-managed message-queue service — the standard durable async-messaging primitive for decoupling services on AWS. Tiny Command exposes three actions, no triggers (SQS doesn't push messages; consumers pull via polling, which is the core of SQS's design): Send Message (push a message into a queue, with optional message_attributes and a delay_seconds for delayed delivery), Receive Messages (long-poll for up to 10 messages; returns immediately if messages are available, waits up to 20 seconds for new arrivals if not), Delete Message (acknowledge a received message so it doesn't redeliver after the visibility timeout). The connection uses AWS IAM credentials (access key + secret) or IAM role assumption with sqs:* permissions on the target queue. The standard pattern: a Tiny Command webhook trigger receives an event, Send Message pushes it to SQS for durable async processing by a downstream consumer; or a scheduled trigger fires Receive Messages every N seconds to drain a queue into a Tiny Command-orchestrated workflow.
Do anything AWS SQS can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Delete SQS Message | Acknowledges a received SQS message so it doesn't redeliver after the visibility timeout. Must call this within the visibility timeout window or SQS re-delivers the message to another consumer. |
| Receive SQS Messages | Long-polls the queue for up to 10 messages. Pass wait_time_seconds=20 for full long polling (waits up to 20s for new messages to arrive on quiet queues) — reduces empty-receive costs significantly. Schedule this on a cadence to drain a queue from a workflow. |
| Send SQS Message | Sends a message to a Standard or FIFO queue with optional delay (delay_seconds) for delayed delivery and message_attributes for typed metadata that subscribers can filter on. The standard hook for decoupling: webhook trigger → push to queue → external worker consumes. |
Pre-built AWS SQS workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect AWS SQS once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every AWS SQS field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the AWS SQS integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect AWS SQS to Tiny Command?
What AWS SQS triggers does Tiny Command support?
What AWS SQS actions can I run from a workflow?
Is the AWS SQS integration real-time?
Do I need to write code to use AWS SQS with Tiny Command?
How much does the AWS SQS integration cost?
More communication apps people connect.
Same category as AWS SQS, ordered by how often teams pair them. Hover the carousel to pause.
Do more with AWS SQS.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
