After you add and activate a data actions integration, you can create or update an interaction flow in Architect that uses the static or custom actions associated with the integration. For more information, see Add a data actions integration,Example call flow, and How many seconds before a data action times out?.

The following steps describe how to use a static or custom action in an inbound call flow. The steps are similar for other interaction flow types in Architect.

1. Open Architect.
2. Create or update a flow.
   
   • Create a flow.
     
     1. Click Add.
     2. In the Create Flow dialog box, add a name for your flow.
     3. Click Create Flow.
   • Update a flow.
     1. Click a flow that you want to update.
3. Add a data 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 Data Action to the editor.
4. Configure the Call Data Action.
   1. In the Call Data Action design form, select the Category of the data action that you want to use in the flow.

      The category is the name of the integration in your Genesys Cloud organization. 

   2. Select the Data Action that you want to use.
   3. Under Inputs, define the variable for the items that appear. 

      For the Microsoft Dynamics 365, Salesforce, Zendesk data actions integrations, the properties that appear under Inputs depends on what data action you selected. For example, if you select a data action the retrieves information by phone number, then the PHONE_NUMBER box appears. For information about how the integrations convert phone numbers in the PHONE_NUMBER box, see Phone number searches.

      For the Adobe, AWS Lambda, Google, Genesys Cloud, and web services data actions integrations, the properties that appear come from the request schema that you created for the data action.

For more information about Architect, including how to design interaction flows, see Architect overview.

For more information about the integrations, see About the data actions integrations.