> ## Documentation Index
> Fetch the complete documentation index at: https://koreai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Genesys Open Messaging

<Badge icon="arrow-left" color="gray">[Back to messaging or digital channels](/agent-platform/channels#messaging-or-digital)</Badge>

Connect Genesys Cloud Open Messaging conversations through a project-scoped webhook adapter.

<Note>Complete the Genesys Cloud Open Messaging setup before you begin. It produces the Integration ID and webhook credentials this connection needs, and determines how the connection is validated before it goes live.</Note>

## Configure the connection

To configure a Genesys Open Messaging channel, go to **Deployments** -> **Channels** -> **MESSAGING** -> **Genesys Open Messaging** -> **+ New** and complete the following steps in order.

<Steps>
  <Step title="Complete setup in Genesys Cloud">
    1. Select the Genesys Cloud region and organization for this project connection.
    2. Bind an active Genesys platform Auth Profile for outbound API calls.
    3. Copy the generated Open Messaging webhook URL into the Genesys integration.
    4. Use diagnostics to validate signature handling before enabling live traffic.
  </Step>

  <Step title="Enter connection details">
    On the **New Genesys Open Messaging Connection** page, provide a **Display Name** (up to 255 characters), then set up **Open Messaging setup**, which creates a project-owned webhook token, binds a Genesys Auth Profile, and keeps the connection in diagnostics mode until the Genesys sandbox passes.

    | Field                        | Description                                                                                                                    |
    | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
    | **Genesys Region**           | The Genesys region this connection is scoped to, for example `US East (N. Virginia)`.                                          |
    | **Genesys Organization ID**  | Your Genesys Cloud organization identifier.                                                                                    |
    | **Integration ID**           | The Open Messaging integration ID from Genesys Cloud.                                                                          |
    | **Activation Mode**          | The connection's rollout stage, for example `Diagnostics only`. Promote to live traffic only after the Genesys sandbox passes. |
    | **Genesys Auth Profile**     | The Auth Profile that authenticates this connection with Genesys Cloud. Select one from the dropdown.                          |
    | **Webhook Connection Token** | The token Genesys uses to authenticate inbound webhook requests.                                                               |
    | **Webhook Signature Secret** | The secret used to verify inbound webhook signatures.                                                                          |
  </Step>

  <Step title="Complete common connection settings">
    | Field                              | Description                                                                                                                                                                                                                                                                   |
    | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | **Environment**                    | Select an environment to follow its active deployment, or leave the default to use the working copy.                                                                                                                                                                          |
    | **Provider Verification Strength** | Controls how strictly the platform trusts the provider's identity assertions for session continuity and linking. **Weak** is the default. Choose **Strong** only for channels or providers whose identity assertions you trust for stronger continuity and linking decisions. |
    | **Initial Status**                 | **Active** connections can be used immediately. **Inactive** connections stay saved but disabled until you activate them.                                                                                                                                                     |

    Select **Create**.
  </Step>
</Steps>