Use bridge actions in Architect for connectors


Note: This article applies to the web services data dip connector.

After you add a bridge action in PureCloud, create a call flow in Architect that uses the bridge action for the web services data dip connector. For more information, see Add a bridge action and Example call flow.

Tip: Before using Architect, upgrade to the most recent version of the Bridge Server and the connector. For more information, see Upgrade a Bridge Server and Upgrade a Bridge Connector.

  1. Open Architect.
  2. Create or update a flow.
    • Create a flow.
      1. Click Add.
      2. Add a name for your flow in the Create Flow dialog box.
      3. Click Create Flow.
    • Update a flow.
      1. Click a flow that you want to update.
  3. Add a bridge action.
    1. From Toolbox, expand the Task category and drag a Task to the editor.
    2. Open the task.
    3. From Toolbox, expand the Data category and drag a Call Bridge Action to the editor.
  4. Configure the Call Bridge Action.

    The steps differ for default connector actions and custom connector actions.

    • Default connector actions
      1. In the Call Bridge Action design form, select the Category of the bridge action that you want to use in the flow.
      2. Select the Bridge Action that you want to use.
      3. Under Inputs, define the variable for the properties that appear.

        The properties that appear under Inputs depend on what connector action is associated with the bridge action that you selected. For example, if the bridge action that you selected is associated with the connector action GetContactByPhoneNumber, then the PhoneNumber box appears.

      4. (Optional) Under Inputs, define the variable for CustomAttribute.

        Use a custom attribute to retrieve additional information from your CRM or third-party system. For example, define a variable (such as member_level) in the CustomAttribute box to return the member level associated with an account, case, or contact.

        1. Add an attribute supported by your web service to the CustomAttribute box under Inputs in Architect, for example, support_level.
        2. Add a name to the CustomAttribute box under Outputs in Architect.

          A prefix indicating the type of connector action appears before the name of the CustomAttribute box. In the example. Account. appears for the connector action GetAccountByPhoneNumber.

          Add any name for the custom attribute you want after the prefix Flow., for example, Flow.supportLevel. To perform a task, for example, to decide if a caller is a gold member (Flow.supportLevel == “gold”), use this output term in your call flow.

        Click image to enlarge.

        Call flow in Architect with custom attribute

    • Custom connector actions
      1. In the Call Bridge Action design form, select the Category of the bridge action that you want to use in the flow.
      2. Select the Bridge Action that you want to use.
      3. Under Inputs, define the values for the properties that appear.

        The properties that appear come from the request schema that you created for the bridge action. 

      4. Under Outputs, define the values for the properties that appear.

        The properties that appear come from the response schema that you created for the bridge action.

      Note: For more information about Architect, including how to design call flows, see the Architect documentation.

For more information about the connector, see About the web services data dip connector.