(Published) |
(Published) |
||
Line 5: | Line 5: | ||
|ComingSoon=No | |ComingSoon=No | ||
|Section={{Section | |Section={{Section | ||
− | |sectionHeading=Provisioning AI Connector | + | |sectionHeading=Provisioning AI Connector webhook to Digital Channels |
|alignment=Vertical | |alignment=Vertical | ||
− | |structuredtext=To receive and analyse chat messages, AI Connector functions as a webhook for Digital Channels | + | |structuredtext=To receive and analyse chat messages, AI Connector functions as a webhook for interactions in Digital Channels. As Digital Channels is unaware of where AI Connector is available, register AI Connector with Digital Channels. This process includes two parts: |
#{{Link-SomewhereInThisVersion|anchor=Verify|display text=Verify AI Connector Webhook|manual=DCPEGuide|topic=ProvisionAIConnector}} | #{{Link-SomewhereInThisVersion|anchor=Verify|display text=Verify AI Connector Webhook|manual=DCPEGuide|topic=ProvisionAIConnector}} | ||
Line 13: | Line 13: | ||
{{AnchorDiv|Verify}} | {{AnchorDiv|Verify}} | ||
− | ===Verifying AI Connector | + | ===Verifying AI Connector webhook=== |
AI Connector webhook is deployed at <code>'''${CONF.athena.server.apiPrefix}/agent-assist-chat/messages'''</code> | AI Connector webhook is deployed at <code>'''${CONF.athena.server.apiPrefix}/agent-assist-chat/messages'''</code> | ||
− | Verifying the webhook returns the HTTP status code as '''200''' with status ''''' | + | Verifying the webhook returns the HTTP status code as '''200''' with status '''''PAYLOAD_SIGNATURE_CHECK_FAILED''''' |
{{AnchorDiv|Register}} | {{AnchorDiv|Register}} | ||
− | ===Registering | + | ===Registering webhook to Digital Channels=== |
The webhook target name for Digital Channels is '''ai-connector''' | The webhook target name for Digital Channels is '''ai-connector''' | ||
− | It is a one-time process (per contact center) required to ensure that the AI Connector webhook URL is known and trusted to Digital Channels service. | + | It is a one-time process (per contact center) required to ensure that the AI Connector webhook URL is known and trusted to Digital Channels service. For registering the AI Connector webhook, send a request with the admin-level access credentials to Digital Channels. |
Request: | Request: |
Latest revision as of 04:55, August 17, 2022
Difference between revisions of "PEC-DC/Current/DCPEGuide/ProvisionAIConnector"
Learn about the steps involved in provisioning Digital Channels AI Connector.
Provisioning AI Connector webhook to Digital Channels
To receive and analyse chat messages, AI Connector functions as a webhook for interactions in Digital Channels. As Digital Channels is unaware of where AI Connector is available, register AI Connector with Digital Channels. This process includes two parts:
Verifying AI Connector webhook
AI Connector webhook is deployed at ${CONF.athena.server.apiPrefix}/agent-assist-chat/messages
Verifying the webhook returns the HTTP status code as 200 with status PAYLOAD_SIGNATURE_CHECK_FAILED
Registering webhook to Digital Channels
The webhook target name for Digital Channels is ai-connector
It is a one-time process (per contact center) required to ensure that the AI Connector webhook URL is known and trusted to Digital Channels service. For registering the AI Connector webhook, send a request with the admin-level access credentials to Digital Channels.
Request:
curl --request POST 'https://{nexusUrl}/nexus/v3/provisioning/services/{ccid}/WebhookTransportTarget-ai-connector' \
--header 'Authorization: Bearer {accessToken}' \
--header 'Content-Type: application/json' \
--data '{
"url": "{AI Connector webhook URL}"
}'