Skip to main content
About the Resource Center

Add contracts to custom 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.

When creating a custom action, first add an action and then add contracts. The contracts define the information that you provide to the action for its execution and the response that it ultimately returns. For more information, see Create a custom action for integrations.

Notes:
  • You cannot change the contracts after you publish the action.
  • Contracts do not support the $ref keyword.
  1. Click the Setup tab.
  2. Click the Contracts tab.
  3. Under Input Contract, click Simple or JSON to configure the contract. Genesys recommends that you use the Simple input method.

    The input contract defines the information that you provide to the action for execution. 

    Notes:
    • The input contract accepts an object with key-value pairs. The key-value pairs are limited to the following data types: string, integer, number, Boolean, null. The input contract does not support nested objects.
    • Property names in the input contract must start with a letter (a-z, A-Z) and only contain letters, numbers (0-9), hyphens (-), or underscores (_). Do not use the reserved terms orgId, integrationId, and rawRequest, or you will overwrite existing properties with these names and cause the data action to fail.
  4. Under Output Contract, click Simple or JSON to configure the contract. Genesys recommends that you use the Simple input method.

    The output contract defines the information that the action returns after successful execution.

    Note: The output contract does not support nested arrays.

    Next, add configuration.

    For more information, see About custom actions for integrations.

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