Requirements for the data actions integration


Note: This article applies to the AWS Lambda, Microsoft Dynamics 365, PureCloud, Salesforce, web services, and Zendesk data actions integrations.

This article lists all third-party and PureCloud requirements to run a data actions integration.

AWS account

PureCloud

  • A PureCloud organization.
  • The following permissions (at a minimum) selected for the administrator of the integration and actions:
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more installed AWS Lambda data action integrations. For more information, see Add a data actions integration.
  • An IAM role added to the integration credentials in PureCloud.

For more information about the integration, see About the AWS Lambda data actions integration.

Microsoft Dynamics 365

  • A user able to access any data that you want to make available to the Microsoft Dynamics 365 data action integration.

    Use this user’s credentials for the Microsoft Dynamics 365 credentials when you add the integration to your PureCloud organization. For more information, see Add a data action integration.

  • The integration registered in Azure Active Directory.

    Use the application ID that is created when you add the integration to your PureCloud organization. For more information, see Register the integration and Add a data actions integration.

PureCloud

  • A PureCloud organization. 
  • The following permissions (at a minimum) selected for the administrator of the integration and actions: 
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more installed Microsoft Dynamics 365 data action integrations. For more information, see Add a data actions integration.

For more information about the integration, see About the Microsoft Dynamics 365 data actions integration.

PureCloud

  • A PureCloud organization.
  • A PureCloud OAuth client to authorize access to the Platform API.

    When you add a PureCloud data actions integration, you must add OAuth credentials to the integration configuration. For more information, see Create an OAuth client and Authorization (Developer Center). 

  • The following permissions (at a minimum) selected for the administrator of the integration and actions:
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more PureCloud data actions integrations. For more information, see Add a data actions integration.
  • Actions that access the Platform API with the HTTP methods GET, PUT, POST, or PATCH.

For more information about the integration, see About the PureCloud data actions integration.

Salesforce

Note: If you do not select these settings in Salesforce, all data actions associated with the integration will fail.
  • A user (preferably a system admin) able to access any standard and custom fields that are used in PureCloud.

    Associate this user with a profile in Salesforce that has the following settings selected:

    • API Enable 
    • View All (for accounts, cases, and contacts) 

    When you add the integration in PureCloud, use this user’s credentials for the Salesforce credentials. For more information, see Add a data actions integration.

PureCloud

  • A PureCloud organization. 
  • The following permissions (at a minimum) selected for the administrator of the integration and actions: 
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more installed Salesforce data action integrations. For more information, see Add a data actions integration.

For more information about the integration, see About the Salesforce data actions integration.

Web service

  • A web service that supports the following items:
    • JSON-based web service calls.
    • No authentication, Basic authentication, user-defined authentication, or user-defined (OAuth) authentication. For more information, see Credential types.
    • HTTP methods GET, PUT, POST, or PATCH.
    • An HTTPS endpoint on port 443. 
      Note: The integration does not support other ports. For more information, see Can we call a web service running on a port other than 443?.

PureCloud

  • A PureCloud organization.
  • The following permissions (at a minimum) selected for the administrator of the integration and actions:
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more installed web services data action integrations. For more information, see Add a data actions integration.
  • Authentication credentials added to the integration configuration in PureCloud, if required for the web service.

For more information about the integration, see About the web services data actions integration.

Zendesk

  • A verified user in Zendesk (preferably an administrator for access control purposes).

    Use this user’s ID for the Zendesk credentials when you add the integration to your PureCloud organization. For more information, see Add a data actions integration.

  • An API token.

PureCloud

  • A PureCloud organization. 
  • The following permissions (at a minimum) selected for the administrator of the integration and actions: 
    Notes:
    • Depending on where you access the permissions in PureCloud, the permission names appear in different formats.
    • Instead of selecting individual integrations > action permissions, you can select Integrations > Action > All Permissions. This permission grants administrators access to all permissions—current and future—involving actions.

    • Integrations > Integration > Edit and View

      These permissions allow administrators to edit and view integrations.

    • Integrations > Action > Add, Delete, Edit, Execute, and View

      These permissions allow administrators to add, delete, edit, test, and view custom actions.

  • One or more installed Zendesk data action integrations. For more information, see Add a data actions integration.

For more information about the integration, see About the Zendesk data actions integration.