Short answer: Drop the "AWS Bedrock → Knowledge Bases Retrieve" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Knowledge Base ID knowledge_base_id | string | Required | Knowledge Base ID (required) |
Query query | string | Required | Query (required) |
Number of Results number_of_results | string | Optional | Number of Results |
{"knowledge_base_id": "{{trigger.knowledge_base_id}}","query": "{{trigger.query}}","number_of_results": "{{trigger.number_of_results}}"}
{"retrievalResults": [{"score": 0.91,"content": {"text": "..."},"location": {"type": "S3","s3Location": {"uri": "s3://x/y"}}}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.