AActionAWS BedrockUpdated May 2026

How do I call Bedrock's unified Converse API?

Short answer: Drop the "AWS Bedrock → Bedrock Converse" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 AWS Bedrock actions

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Bedrock Converse support batch operations?

Yes. Run Bedrock Converse inside a Loop node to process arrays. Tiny Command handles AWS Bedrock's rate limits automatically so you don't have to throttle manually.

More actions