AWS Bedrock
AWS Bedrock managed LLM inference
AWS Bedrock is the AWS-managed LLM platform — provides hosted access to Anthropic Claude, Meta Llama, Mistral, Cohere, AI21, Amazon Titan, and Stable Diffusion models via a single API, integrated with AWS IAM and VPC for enterprise-grade compliance. Tiny Command exposes three actions, no triggers: Converse (the unified Conversation API that works across all chat-capable models on Bedrock with the same message-array shape — the recommended path for new workflows), Invoke Model (Raw) (the model-specific Invoke API for cases that need model-specific parameters Converse doesn't expose), Knowledge Bases Retrieve (RAG against a Bedrock Knowledge Base — semantic search over your indexed documents, returns relevant chunks with citations for downstream LLM grounding). The connection uses AWS IAM credentials (access key + secret) with bedrock:InvokeModel and bedrock-runtime:* permissions, plus the region (Bedrock is regional; models available vary by region — us-east-1 and us-west-2 have the broadest catalog). The Converse API is the right default for cross-model workflows since it abstracts away model-specific quirks.
Do anything AWS Bedrock 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 |
|---|---|
| Bedrock Converse | The model-agnostic chat API — same message-array shape works across Claude, Llama, Mistral, and other chat-capable Bedrock models. Swap models with a single parameter change. The recommended default for new Bedrock workflows since it abstracts away model-specific request quirks. |
| Invoke Model (Raw) | Model-specific Invoke API for cases where the unified Converse API doesn't expose what you need (e.g., specific Claude-only parameters, specific generation modes for image/embedding models). Each model has its own request shape — check Bedrock's per-model docs. |
| Knowledge Bases Retrieve | Semantic-searches a configured Bedrock Knowledge Base (which sits on top of S3-stored documents indexed into a vector store) and returns the most relevant chunks with citations. Saves you from building and managing your own RAG ingestion pipeline. |
Pre-built AWS Bedrock workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
AI-triage every AWS Bedrock event, ping the right channel only when it matters.
Every event matching a filter, appended to a running spreadsheet.
Turn AWS Bedrock into a Notion-backed source of truth, auto-tagged.
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 Bedrock once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every AWS Bedrock 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 Bedrock integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect AWS Bedrock to Tiny Command?
What AWS Bedrock triggers does Tiny Command support?
What AWS Bedrock actions can I run from a workflow?
Is the AWS Bedrock integration real-time?
Do I need to write code to use AWS Bedrock with Tiny Command?
How much does the AWS Bedrock integration cost?
More communication apps people connect.
Same category as AWS Bedrock, ordered by how often teams pair them. Hover the carousel to pause.
Do more with AWS Bedrock.
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.
