By using AWS re:Post, you agree to the Terms of Use

Import Contact Flow via CLI or UI

0

Has anyone found that using the import/export of a contact flow works but to export a contact flow and then use the AWS CLI create-contact-flow to import it into another environment I received an application exception.

It looks like the CLI/API expect a different json format compared to the export/import which may make adding this step to a pipeline difficult.

Any views/feedback would be welcome

3 Answers
0

So the export/import format of the JSON is different from the UI so you cannot use the AWS CLI/ Connect API to import the file.

So you need to use the describe-contact-flow CLI/API to get the correctly formatted JSON and then use the create/update contact flow CLI/API for it to work. It will not work by using the UI Import facility.

answered 2 years ago
0

m66rus wrote:
So you need to use the describe-contact-flow CLI/API to get the correctly formatted JSON and then use the create/update contact flow CLI/API for it to work. It will not work by using the UI Import facility.

That won't work across instances either since the ARNs for all prompts, flows, queues etc. will be different in the described flow vs the created/updated flow (they differ across instances). So you need to list all prompts, flows, queues, lambdas in each instance then match them up somehow (e.g. by Name), then replace all ARNs in the flow JSON with the corresponding resource ARNs from the instance you are updating

answered 2 years ago
0

Yes you are correct, the ARN need parsing but I was having an issue just getting it to import but found that I was wasn't handling the format of the contents attribute. In terms of replacing the ARN i am working on a script to replace those.

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions