Contact Flow ARN Parameterizer
Moving a Contact Flow from Dev to Prod? Every embedded ARN breaks the import. Paste your flow JSON and this tool replaces every Queue, Lambda, Lex Bot, Prompt, and Flow ARN with a clean named placeholder — so you can import anywhere with a simple find-and-replace.
Drop your Contact Flow JSON here
Supports Amazon Connect exported Contact Flows and Modules
Re-hydrate: Substitute Target-Account ARNs
Already have your parameterized JSON and the real ARNs from the target account? Paste both below and this will substitute them automatically — no manual find-and-replace needed.
From Broken Import to Clean Deployment
Three steps to make your Contact Flow fully portable across AWS accounts and regions.
Export your Contact Flow from Amazon Connect
In the Amazon Connect console, open the Contact Flow editor, click the menu (⋮) and choose Export flow. You'll get a .json file.
Upload or paste it here and click "Parameterize ARNs"
The tool scans the JSON for every ARN — Queues, Lambda functions, Lex Bots, Prompts, and other Contact Flows — and replaces each with a descriptive placeholder like {{Queue_CustomerSupport}}.
Download the parameterized JSON and the mapping CSV
In your target account, collect the matching ARN for each placeholder. Either edit the mapping CSV directly, or paste both the parameterized JSON and the mapping into the Re-hydrate section below to substitute everything automatically — then import the flow.
Your Data Stays Local
All ARN detection and replacement runs entirely in your browser using JavaScript. The Contact Flow JSON never touches our servers.
All ARN Types Detected
Queues, Routing Profiles, Lambda Functions, Lex Bots (V1 & V2), Prompts, Contact Flows, Modules, Hours of Operation, Phone Numbers (V1 & V2), Quick Connects, Security Profiles, Users, Task Templates, Views, Evaluation Forms, Amazon Q in Connect (Wisdom), and any other arn:aws:* resource via a generic fallback rule — nothing is ever silently skipped.
Intelligent Naming
Placeholders are generated from the resource name embedded in the ARN, not a generic counter — making the parameterized JSON human-readable and self-documenting.
Duplicate-Safe
When the same ARN appears multiple times in a flow (common for shared queues), the tool uses a single placeholder everywhere — keeping the output consistent and the mapping table clean.
Frequently Asked Questions
Everything you need to know about parameterizing Amazon Connect Contact Flows.
arn:aws:* pattern found in the JSON via a generic fallback rule.
{{Queue_CustomerSupport}}) with the correct ARN from the new environment. Then import the updated JSON into Amazon Connect via the flow editor.
Placeholder,ARN (or the CSV this tool exports, with the last column filled in with the target ARNs), and it substitutes everything automatically — flagging any placeholder that doesn't have a matching row so you don't miss one.