AActionAWS BedrockUpdated September 2026

How do I call Bedrock's unified Converse API?

Short answer: You can bedrock converse in AWS Bedrock by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the AWS Bedrock Bedrock Converse action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Bedrock Converse in AWS Bedrock — start free All 3 AWS Bedrock actions

Bedrock Converse in AWS Bedrock — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Model ID model_id	options	Required	Model ID. Options: Claude Opus 4.7, Claude Sonnet 4.6, Claude Haiku 4.5 …
User Message message	string	Required	User Message (required)
System Prompt system_prompt	string	Optional	System Prompt
Temperature temperature	string	Optional	0.7
Max Tokens max_tokens	string	Optional	1024

Sample request

{
  "model_id": "{{trigger.model_id}}",
  "message": "{{trigger.message}}",
  "system_prompt": "{{trigger.system_prompt}}",
  "temperature": "0.7",
  "max_tokens": "1024"
}

Returns

{
  "usage": {
    "inputTokens": 10,
    "totalTokens": 60,
    "outputTokens": 50
  },
  "output": {
    "message": {
      "role": "assistant",
      "content": [
        {
          "text": "Sample"
        }
      ]
    }
  },
  "stopReason": "end_turn"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Bedrock Converse.

Any of these apps can fire this action as part of a workflow.

Google Sheets → AWS Bedrock

2 Google Sheets triggers

HubSpot → AWS Bedrock

18 HubSpot triggers

FAQ

Questions about Bedrock Converse.

What does the Bedrock Converse action do in AWS Bedrock?

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.

What inputs does Bedrock Converse require?

Required: Model ID, User Message. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if AWS Bedrock returns an error?

The run history shows the failed step with its input and the error message AWS Bedrock returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Bedrock Converse support batch operations?

Run Bedrock Converse inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within AWS Bedrock's rate limits.

More actions

Other AWS Bedrock actions.

Action

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.

Action

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.

Bedrock Converse in AWS Bedrock — start free