Programmatically manage contact flows with new HAQM Connect APIs

HAQM Connect, an easy to use contact center service, allows contact center managers to build contact flows in a single user interface. Typically, contact centers have more than one contact flow that serve a number of different purposes. However, there are often cases in which certain aspects of one contact flow must be replicated in another. For example, if you would like to store customer data during a call you must invoke the same AWS Lambda function across multiple different contact flows. Performing these tasks manually is prone to error, time consuming to replicate flows, and also leads to inconsistent configuration.

Today, AWS launched new contact flow APIs for HAQM Connect that will help perform these operations programmatically and enable customers to automate these tasks. Customers will be able to replicate flows across instances using a CI/CD pipeline, as opposed to manually performing these tasks. This also enables HAQM Connect administrators to have faster and robust mechanism to innovate, deliver value, and better experience for their customers.

In this blog, you learn how to leverage HAQM Connect contact flow APIs to automate create, read, update, and publish functions through a web-based user interface (UI). This is easily deployed from an AWS CloudFormation template.

Prerequisites

• An AWS account
• An existing HAQM Connect instance
• Access to AWS services
  • AWS IAM with access to create policies and roles
  • HAQM CloudFront with access to create a distribution
  • HAQM S3 with access to create buckets
  • AWS CloudFormation to run the stack
• AWS IAM access and secret key credentials

Overview of solution

This solution leverages the new APIs with the help of a front-end Web UI developed and provided in the CloudFormation template. The UI uses the AWS SDK for JavaScript and APIs to access contact flows in the source and destination HAQM Connect instances. We can then use the UI to make API calls to back up the contact flows in JSON format in the DynamoDB table and also replicate contact flows from source to destination instance using the same JSON.

Walkthrough

Steps:

1. Click to Launch the CloudFormation Template
2. Select next at the bottom of the screen:
3. Enter a Stack Name (e.g. contactflowapiblog) and click next to continue:
4. On the next page, leave everything default and click next to continue
5. On the following page, check the radio button for acknowledgement of statement, and then click on create stack button.
6. Wait for confirmation that the stack creation is complete.
7. Access the CloudFront Web UI to access the portal
8. Configure the source and destination HAQM Connect instances
9. Get all the contact flows in each instance
10. Test and validate the solution by performing actions on both HAQM Connect instances

Note: All resources must be created in US West (Oregon) Region

Launch the Contact Flow APIs User Interface Website

1. 1. Go to the AWS CloudFormation service in the AWS Console and click on the stack you just created.
   2. Go to the outputs section of the newly created Stack and copy the CloudFrontEndpoint URL. Paste this in a browser window to access the HAQM Connect contact flows APIs Website, which shows the source HAQM Connect instance on the left and destination instance on the right.
   3. Next, configure the AWS IAM credentials. Click on AWS Configurations on the left and input all the required information (All Fields are mandatory) to access the two HAQM Connect instances and click on save configurations.

1. 1. Click the details link for one of the contact flows listed to see the formatted JSON view of the contact flow.
   2. Select the change name icon for one of the listed contact flows and change the name to something new as depicted here. Once you click rename contact flow, it modifies the contact flow in that HAQM Connect instance and displays the updated contact flow name in the list without requiring a browser refresh.
   3. Promote the renamed contact flow to the destination HAQM Connect Instance:
      1. 1. The promote function copies or creates an identical contact flow from the source instance on the left to the destination instance on the right. The UI enumerates all the required dependencies or other contact flows required for the flow being copied or created to function properly.

      

      1. Select the update contact flow button to run the promotion of the contact flow. If the target HAQM Connect instance does not have a contact flow with the same name it alerts with the prompt below. You can select Ok to create a new contact flow with the intended name, or select Cancel to abort the promotion of the flow.
   4. If you Select OK, you should see the same contact flow exists in both HAQM Connect Instances.

1. 1. You can back up selected contact flows in the DynamoDB table by clicking on the backup selected flows and then verify the DynamoDB to ensure the flows are backed up.

1. 1. We also create a new flow in the source or the destination instance through the UI. We demonstrate creating an agent whisper flow.
      • Click on create contact flow button.
      • In the pop-up screen, please make sure you have the correct instance and type of flow selected. Give a name and description to your flow and copy the flow in the JSON format in the body of the screen. Click create contact flow to create the flow.

1. You can see now that we have the Flow created in the list “XXXXX”.

Cleaning up

To avoid incurring future charges, delete the resources that you created by visiting AWS CloudFormation.

Conclusion

This post demonstrated how to leverage the new contact flow APIs to read all the contact flows across the two HAQM Connect instances and perform following functions programmatically, instead of logging in to the web interface and walking through a multi-step process.

This enables customers to orchestrate these activities in their CI/CD pipeline and also comply with some of the compliance requirements from BCP perspective.

1. Use a web interface (GUI) to list all contact flows in 2 different HAQM Connect instances leveraging APIs
2. How to get a JSON output of each contact flow and rename individual contact flows in either Instance.
3. How to back up contact flows in the source or production HAQM Connect instances.
4. Create new contact flows in either of the instances

To learn more about how this solution was built and see how the APIs were executed, refer to the GitHub repo.