Test data actions for integrations

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

You can test data actions for the data actions integrations.

Test draft custom actions for validation or execution errors. For more information, see .
Test published custom actions for help debugging issues.
Test static actions to see if the action works as expected with your CRM.
Test custom auth actions to see what information the action returns. For more information, see and .

Note: For security purposes, when the web services data actions integration tests custom auth actions for the User Defined (OAuth) credential type or custom actions for User Defined and User (OAuth) credential types, the integration redacts all credential information. For more information about credential types, see .

Warning: Do not include sensitive data in your action. Test displays the entire request and response payload under Operations, including sensitive data.

On the Setup page, click the Test tab. For more information, see .
Test runs various operations to check for errors.
Under Input, add information for the fields that appear.
These fields are defined in the Input Contract. For custom actions, if you completed the Input Contract but no fields appear here, then refresh your browser. For more information, see .
Keep Flatten output selected.
This selection flattens the data returned from the Output Contract. For more information, see .
Note: Most Genesys Cloud applications use flattened data.
Click Run Action.
The action executes in test mode, which reports test results at each operation. The test stops after the first failure. For more information about failures, see .
Note: For Genesys Cloud Function data action, the test returns the last 4 KB of the log files generated by console statement within the code. These logs are available only during the testing phase of the data action.
Information about the AWS Lambda and web services data actions integrations and Google Cloud Functions
- Running the action hits your AWS Lambda function, your Google Cloud Functions, or your external web service.
- The test execution of a data action that calls Google Cloud Functions converts the stringified JSON response to JSON.
- If testing returns errors for items that are correct, such as “Invalid JSON” for correct JSON, the transfer encoding that your web service and Genesys Cloud uses could be incompatible. For more information, see .

For more information, see and .

For more information about the integrations, see .

[NEXT] Was this article helpful?

Get user feedback about articles.