はじめに
対話型AIプラットフォーム
チャットボットの概要
自然言語処理(NLP)
ボットの概念と用語
クイックスタートガイド
プラットフォームへのアクセス
ボットビルダーの操作
リリースノート
最新バージョン(英語)
以前のバージョン(英語)
廃止機能(英語)
コンセプト
設計
ストーリーボード
ダイアログタスク
ダイアログタスクとは
ダイアログビルダー
ノードタイプ
インテントノード
ダイアログノード
エンティティノード
フォームノード
確認ノード
ロジックノード
ボットアクションノード
サービスノード
Webhookノード
スクリプトノード
グループノード
エージェント転送ノード
ユーザープロンプト
音声通話プロパティ
イベント ハンドラー
ナレッジグラフ
ナレッジグラフの抽出
ナレッジグラフの構築
ボットにナレッジグラフを追加
グラフの作成
ナレッジグラフの構築
既存のソースからFAQを構築
通知タスク
スモールトーク
デジタルスキル
デジタルフォーム
デジタルビュー
デジタルビューとは
パネル
ウィジェット
トレーニング
トレーニングとは
機械学習
機械学習とは
モデル検証
ファンダメンタルミーニング
ナレッジグラフ
示唆
ランキングおよび解決
NLPの詳細設定
NLPのガイドライン
インテリジェンス
インテリジェンスとは
コンテキスト
コンテキストインテント
割り込み
複数インテントの検出
エンティティの変更
デフォルトの会話
センチメント管理
トーン分析
テストとデバッグ
ボットと会話
発話テスト
バッチテスト
会話テスト
デプロイ
チャネル
公開
分析
ボットの分析
NLPメトリクス
会話フロー
Usage Metrics
封じ込め測定
カスタムダッシュボード
カスタムダッシュボードとは
メタタグ
カスタムダッシュボードとウィジェット
LLM and Generative AI
Introduction
LLM Integration
Kore.ai XO GPT Module
Prompts & Requests Library
Co-Pilot Features
Dynamic Conversations Features
Guardrails
ユニバーサルボット
ユニバーサルボットとは
ユニバーサルボットの定義
ユニバーサルボットの作成
ユニバーサルボットのトレーニング
ユニバーサルボットのカスタマイズ
他言語の有効化
ストア
プラントと使用
Overview
Usage Plans
Support Plans
Invoices
管理
ボット認証
複数言語対応ボット
個人を特定できる情報の編集
ボット変数の使用
IVRのシステム連携
一般設定
ボット管理
ハウツー
会話スキルの設計
バンキングボットを作成
バンキングボット – 資金の振り替え
バンキングボット – 残高を更新
ナレッジグラフを構築
スマートアラートの予約方法
Integrations
Actions
Actions Overview
Asana
Configure
Templates
Azure OpenAI
Configure
Templates
BambooHR
Configure
Templates
Bitly
Configure
Templates
Confluence
Configure
Templates
DHL
Configure
Templates
Freshdesk
Configure
Templates
Freshservice
Configure
Templates
Google Maps
Configure
Templates
Here
Configure
Templates
HubSpot
Configure
Templates
JIRA
Configure
Templates
Microsoft Graph
Configure
Templates
Open AI
Configure
Templates
Salesforce
Configure
Templates
ServiceNow
Configure
Templates
Stripe
Configure
Templates
Shopify
Configure
Templates
Twilio
Configure
Templates
Zendesk
Configure
Templates
Agents
Agent Transfer Overview
Custom (BotKit)
Drift
Genesys
Intercom
NiceInContact
NiceInContact(User Hub)
Salesforce
ServiceNow
Configure Tokyo and Lower versions
Configure Utah and Higher versions
Unblu
External NLU Adapters
Overview
Dialogflow Engine
Test and Debug
デジタルスキルの設計
デジタルフォームの設定方法
デジタルビューの設定方法
データテーブルのデータの追加方法
データテーブルのデータの更新方法
Add Data from Digital Forms
ボットのトレーニング
示唆の使用方法
インテントとエンティティのパターンの使用方法
コンテキスト切り替えの管理方法
ボットのデプロイ
エージェント転送の設定方法
ボット関数の使用方法
コンテンツ変数の使用方法
グローバル変数の使用方法
ボットの分析
カスタムダッシュボードの作成方法
カスタムタグを使ってフィルタリング
Data
Overview
Guidelines
Data Table
Table Views
App Definitions
Data as Service
Build a Travel Planning Assistant
Travel Assistant Overview
Create a Travel Virtual Assistant
Design Conversation Skills
Create an ‘Update Booking’ Task
Create a Change Flight Task
Build a Knowledge Graph
Schedule a Smart Alert
Design Digital Skills
Configure Digital Forms
Configure Digital Views
Train the Assistant
Use Traits
Use Patterns
Manage Context Switching
Deploy the Assistant
Use Bot Functions
Use Content Variables
Use Global Variables
Use Web SDK
Build a Banking Assistant
APIs & SDKs
API Reference
API Introduction
Rate Limits
API List
koreUtil Libraries
SDK Reference
SDK Introduction
Web SDK
How the Web SDK Works
SDK Security
SDK Registration
Web Socket Connect and RTM
Tutorials
Widget SDK Tutorial
Web SDK Tutorial
BotKit SDK
BotKit SDK Deployment Guide
Installing the BotKit SDK
Using the BotKit SDK
SDK Events
SDK Functions
Installing Botkit in AWS
Tutorials
BotKit - Blue Prism
BotKit - Flight Search Sample VA
BotKit - Agent Transfer

ADMINISTRATION
Intro to Bots Admin Console
Administration Dashboard
User Management
Managing Your Users
Managing Your Groups
Role Management
Manage Data Tables and Views
Bot Management
Enrollment
Inviting Users
Sending Bulk Invites to Enroll Users
Importing Users and User Data
Synchronizing Users from Active Directory
Security & Compliance
Using Single Sign-On
Two-Factor Authentication for Platform Access
Security Settings
Cloud Connector
Analytics for Bots Admin
Billing
  1. ホーム
  2. Integrations
  3. Configuring the Freshdesk Action

Configuring the Freshdesk Action

The XO Platform lets you easily connect the Freshdesk integration to create, view, update, search and delete tickets. Click the Freshdesk link to learn more.

This article explains how to authorize and enable the Freshdesk action and install the pre-built templates.

Authorizations Supported

The Kore.ai XO Platform supports basic authentication to allow Freshdesk integration to exchange data. For more information, read the Bot Authorization Overview article.

The Kore.ai XO Platform supports the following authorization types for the Freshdesk integration:

  • Pre-Authorize the Integration – To make the integration process smoother for developers and customers, you can pre-authorize it by providing the necessary authorization credentials to obtain the access token.
  • Allow Users to Authorize the Integration – This method requires the end user to provide credentials during the conversation for authorization. This authorization process involves requesting permission for Kore.ai’s Freshdesk app to access an access token at runtime. To learn more about Freshdesk account types, see Freshdesk Documentation.

Step 1: Enable the Freshdesk Action

Prerequisites:

Before enabling the Freshdesk action, complete the following prerequisites:

  • If you don’t have Freshdesk account credentials, create a developer account in Freshdesk and note down login credentials. Use the Freshdesk Documentation for more information.
  • Copy the API Key and Domain name of your Freshdesk account and keep them for future use to enable the integration.

Steps to enable the Freshdesk action:

  1. Go to Build > Integrations > Actions.
  2. Once you click the Actions menu, all integrations are shown in the Available region. Select the Freshdesk action.

Pre-authorize the Integration

Basic Auth
You can authorize the integration using your credentials. The developer authorization lets you authorize the integration with preconfigured Kore.ai’s app with the Basic Auth option.

Steps to authorize a Freshdesk action using developer credentials:

  1. Go to Build > Integrations > Actions.
  2. Select the Freshdesk action in the Available Actions region.
  3. In the Configurations dialog, select the Authorization tab.
  4. Enter the following details:
    • Authorization Type – Select the Pre-authorize the Integration option, and then select the Basic Auth option.
    • User Sub Domain – The domain name of the Freshdesk account.
    • API Key – The secret API key of your Freshdesk account.
  5. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

    Note: The Freshdesk action is moved from Available to Configured region.

Allow End User to Authorize

You can authorize the integration at a user level with their login credentials. The user authorization process involves requesting permission for Kore.ai’s Freshdesk app to access an access token at runtime. You can also use the basic auth profile to let a user configure the integration at runtime.

Steps to authorize a Freshdesk action at a user level:

  1. Go to Build > Integrations > Actions and select the Freshdesk action.
  2. In the Configurations dialog, select the Authorization tab.
  3. Enter the following details:
    • Authorization Type – Select the Allow Users to Authorize the Integration option, and then select the Basic Auth option.
    • Create your authorization profile to obtain an access token and use it to complete integration without using Kore.ai’s Freshdesk app for authorization. To create a profile, click the Select Authorization drop-down and select the Create New option.
    • Select the type of authorization mechanism. For example, select the Basic Auth option. To create Basic Auth profiles, see Bot Authorization Overview.
    • Enter the following authentication credentials for the Basic Auth mechanism:
      • Name – Enter the name for the Basic Auth profile.
      • Select No for the tenancy URLs option.
      • Base URL – Enter the base tenant URL for the Freshdesk instance.
      • Authorization Check URL – Enter the authorization check URL for your Freshdesk instance.
      • Description – Enter the description of the basic authentication profile.
      • Click Save Auth to save the authorization profile.
      • Select the new Authorization Profile, which you created to complete integration.
  4. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

Step 2: Install the Freshdesk Action Templates

Once you have configured a Freshdesk integration, you can explore and install action templates.

Steps to install action templates:

  1. On the Integration Successful dialog, click the Explore Templates button to view the templates.
  2. In the Integration Templates dialog, click the Install button to begin the installation.
  3. Once the template is installed, click the Go to Dialog button to view the dialog task.
  4. Once all templates are installed, a dialog task for each template is auto-created.
  5. Select the desired dialog task from the templates and click Proceed. For example, select the Create a Ticket task.
  6. Once you click Proceed, the dialog task is auto-created, and the canvas opens with all required entity nodes, service nodes, and message scripts.

Configuring the Freshdesk Action

The XO Platform lets you easily connect the Freshdesk integration to create, view, update, search and delete tickets. Click the Freshdesk link to learn more.

This article explains how to authorize and enable the Freshdesk action and install the pre-built templates.

Authorizations Supported

The Kore.ai XO Platform supports basic authentication to allow Freshdesk integration to exchange data. For more information, read the Bot Authorization Overview article.

The Kore.ai XO Platform supports the following authorization types for the Freshdesk integration:

  • Pre-Authorize the Integration – To make the integration process smoother for developers and customers, you can pre-authorize it by providing the necessary authorization credentials to obtain the access token.
  • Allow Users to Authorize the Integration – This method requires the end user to provide credentials during the conversation for authorization. This authorization process involves requesting permission for Kore.ai’s Freshdesk app to access an access token at runtime. To learn more about Freshdesk account types, see Freshdesk Documentation.

Step 1: Enable the Freshdesk Action

Prerequisites:

Before enabling the Freshdesk action, complete the following prerequisites:

  • If you don’t have Freshdesk account credentials, create a developer account in Freshdesk and note down login credentials. Use the Freshdesk Documentation for more information.
  • Copy the API Key and Domain name of your Freshdesk account and keep them for future use to enable the integration.

Steps to enable the Freshdesk action:

  1. Go to Build > Integrations > Actions.
  2. Once you click the Actions menu, all integrations are shown in the Available region. Select the Freshdesk action.

Pre-authorize the Integration

Basic Auth
You can authorize the integration using your credentials. The developer authorization lets you authorize the integration with preconfigured Kore.ai’s app with the Basic Auth option.

Steps to authorize a Freshdesk action using developer credentials:

  1. Go to Build > Integrations > Actions.
  2. Select the Freshdesk action in the Available Actions region.
  3. In the Configurations dialog, select the Authorization tab.
  4. Enter the following details:
    • Authorization Type – Select the Pre-authorize the Integration option, and then select the Basic Auth option.
    • User Sub Domain – The domain name of the Freshdesk account.
    • API Key – The secret API key of your Freshdesk account.
  5. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

    Note: The Freshdesk action is moved from Available to Configured region.

Allow End User to Authorize

You can authorize the integration at a user level with their login credentials. The user authorization process involves requesting permission for Kore.ai’s Freshdesk app to access an access token at runtime. You can also use the basic auth profile to let a user configure the integration at runtime.

Steps to authorize a Freshdesk action at a user level:

  1. Go to Build > Integrations > Actions and select the Freshdesk action.
  2. In the Configurations dialog, select the Authorization tab.
  3. Enter the following details:
    • Authorization Type – Select the Allow Users to Authorize the Integration option, and then select the Basic Auth option.
    • Create your authorization profile to obtain an access token and use it to complete integration without using Kore.ai’s Freshdesk app for authorization. To create a profile, click the Select Authorization drop-down and select the Create New option.
    • Select the type of authorization mechanism. For example, select the Basic Auth option. To create Basic Auth profiles, see Bot Authorization Overview.
    • Enter the following authentication credentials for the Basic Auth mechanism:
      • Name – Enter the name for the Basic Auth profile.
      • Select No for the tenancy URLs option.
      • Base URL – Enter the base tenant URL for the Freshdesk instance.
      • Authorization Check URL – Enter the authorization check URL for your Freshdesk instance.
      • Description – Enter the description of the basic authentication profile.
      • Click Save Auth to save the authorization profile.
      • Select the new Authorization Profile, which you created to complete integration.
  4. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

Step 2: Install the Freshdesk Action Templates

Once you have configured a Freshdesk integration, you can explore and install action templates.

Steps to install action templates:

  1. On the Integration Successful dialog, click the Explore Templates button to view the templates.
  2. In the Integration Templates dialog, click the Install button to begin the installation.
  3. Once the template is installed, click the Go to Dialog button to view the dialog task.
  4. Once all templates are installed, a dialog task for each template is auto-created.
  5. Select the desired dialog task from the templates and click Proceed. For example, select the Create a Ticket task.
  6. Once you click Proceed, the dialog task is auto-created, and the canvas opens with all required entity nodes, service nodes, and message scripts.
メニュー