{"product_id":"amazon-bedrock-multi-agent-support-triage-slack-in-n8n","title":"Amazon Bedrock Multi-Agent Support Triage + Slack in n8n","description":"\u003ch3\u003eRoute customer questions to the right Amazon Bedrock specialist—then post the answer to Slack automatically\u003c\/h3\u003e\n\u003cp\u003eThis n8n workflow triages every incoming chat message with \u003cstrong\u003eAmazon Bedrock AgentCore Multi-Agent\u003c\/strong\u003e and routes it to the best-matching specialist agent. It then posts the specialist’s response to your selected \u003cstrong\u003eSlack\u003c\/strong\u003e channel, keeping per-customer context shared across agents.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eReceives an n8n Chat message\u003c\/strong\u003e and starts a run tied to that chat input.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSets customer context\u003c\/strong\u003e values (including the agent name, a customer\/actor ID derived from the chat session, the question text, and the target Slack channel).\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRuns Amazon Bedrock AgentCore triage\u003c\/strong\u003e to classify the request (e.g., \u003cstrong\u003eanalysis\u003c\/strong\u003e, \u003cstrong\u003eadvice\u003c\/strong\u003e, or \u003cstrong\u003eresearch\u003c\/strong\u003e) and provisions a \u003cstrong\u003eshared harness\u003c\/strong\u003e with managed memory when needed.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eParses and validates JSON output\u003c\/strong\u003e from the triage step; if parsing fails, it falls back to the \u003cstrong\u003eresearch\u003c\/strong\u003e category.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eRoutes to the matching AgentCore specialist\u003c\/strong\u003e using the \u003cstrong\u003esame harness ARN\u003c\/strong\u003e and \u003cstrong\u003eactor ID\u003c\/strong\u003e so the specialist agents share customer memory.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eCleans and posts a formatted Slack message\u003c\/strong\u003e that indicates which specialist answered and includes the customer ID.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eTurn support chat into \u003cstrong\u003especialized Bedrock responses\u003c\/strong\u003e without manual assignment.\u003c\/li\u003e\n  \u003cli\u003eHandle mixed requests (analysis, advice, research) by automatically selecting the right AgentCore specialist.\u003c\/li\u003e\n  \u003cli\u003eSupport SaaS teams who want \u003cstrong\u003eSlack-first\u003c\/strong\u003e visibility of triaged answers per customer.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAmazon Bedrock AgentCore\u003c\/strong\u003e: triage agent + three specialist agents (Analysis with code interpreter, Architecture with AWS skills, and Research) sharing a managed-memory harness.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSlack integration\u003c\/strong\u003e: posts results to a configurable channel (via Slack OAuth).\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003en8n nodes\u003c\/strong\u003e: set, code, slack, switch, sticky note, and n8n-nodes-langchainchat trigger.\u003c\/li\u003e\n\u003c\/ul\u003e\n\u003cp\u003e\u003cstrong\u003eSetup note:\u003c\/strong\u003e configure the Amazon Bedrock AgentCore API credential on the triage and all specialist nodes, then connect Slack and invite the bot to your target channel.\u003c\/p\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":45812010025139,"sku":"N8N-17966","price":72.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/j1eHpA9uXN6BUggKGVpQk_tDbwHC8D.png?v=1786352920","url":"https:\/\/buyflowscripts.com\/products\/amazon-bedrock-multi-agent-support-triage-slack-in-n8n","provider":"N8N Commerce","version":"1.0","type":"link"}