deploy Amazon Connect contact flow content directly via the API
domain: aws.amazon.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Author or export the flow logic as Amazon Connect Flow language JSON
Call CreateContactFlow to register a new flow with an InstanceId and Type, or use an existing ContactFlowId
Call UpdateContactFlowContent with InstanceId, ContactFlowId, and the Content JSON string to push the flow logic
Use UpdateContactFlowMetadata for name/description changes and UpdateContactFlowModuleContent for reusable modules
Call DescribeContactFlow to confirm the deployed content matches what you pushed
Publish or version the flow in the admin console if your workflow distinguishes draft from published content
Known gotchas
Content has a 256,000 character maximum — large visually-built flows can exceed this and need to be split into modules
UpdateContactFlowContent returns an empty 200 body on success, so confirm success with a follow-up DescribeContactFlow rather than parsing the response
Hand-written flow language JSON must exactly match Connect's schema; structural errors surface as generic validation failures rather than pinpointed line errors
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?