はじめに
対話型AIプラットフォーム
チャットボットの概要
自然言語処理(NLP)
ボットの概念と用語
クイックスタートガイド
プラットフォームへのアクセス
ボットビルダーの操作
リリースノート
最新バージョン(英語)
以前のバージョン(英語)
廃止機能(英語)
コンセプト
設計
ストーリーボード
ダイアログタスク
ダイアログタスクとは
ダイアログビルダー
ノードタイプ
インテントノード
ダイアログノード
エンティティノード
フォームノード
確認ノード
ロジックノード
ボットアクションノード
サービスノード
Webhookノード
スクリプトノード
グループノード
エージェント転送ノード
ユーザープロンプト
音声通話プロパティ
イベント ハンドラー
ナレッジグラフ
ナレッジグラフの抽出
ナレッジグラフの構築
ボットにナレッジグラフを追加
グラフの作成
ナレッジグラフの構築
既存のソースからFAQを構築
特性、同義語、停止用語
変数ネームスペースの管理
更新
ノード間の質問と回答の移動
用語の編集と削除
質問と応答の編集
ナレッジグラフの分析
通知タスク
スモールトーク
デジタルスキル
デジタルフォーム
デジタルビュー
デジタルビューとは
パネル
ウィジェット
トレーニング
トレーニングとは
機械学習
機械学習とは
モデル検証
ファンダメンタルミーニング
ナレッジグラフ
示唆
ランキングおよび解決
NLPの詳細設定
NLPのガイドライン
インテリジェンス
インテリジェンスとは
コンテキスト
コンテキストインテント
割り込み
複数インテントの検出
エンティティの変更
デフォルトの会話
センチメント管理
トーン分析
テストとデバッグ
ボットと会話
発話テスト
バッチテスト
会話テスト
デプロイ
チャネル
公開
分析
ボットの分析
NLPメトリクス
会話フロー
Usage Metrics
封じ込め測定
カスタムダッシュボード
カスタムダッシュボードとは
メタタグ
カスタムダッシュボードとウィジェット
ユニバーサルボット
ユニバーサルボットとは
ユニバーサルボットの定義
ユニバーサルボットの作成
ユニバーサルボットのトレーニング
ユニバーサルボットのカスタマイズ
他言語の有効化
ストア
プラントと使用
Overview
Usage Plans
Support Plans
Invoices
管理
ボット認証
複数言語対応ボット
個人を特定できる情報の編集
ボット変数の使用
IVRのシステム連携
一般設定
ボット管理
ハウツー
会話スキルの設計
バンキングボットを作成
バンキングボット – 資金の振り替え
バンキングボット – 残高を更新
ナレッジグラフを構築
スマートアラートの予約方法
デジタルスキルの設計
デジタルフォームの設定方法
デジタルビューの設定方法
データテーブルのデータの追加方法
データテーブルのデータの更新方法
Add Data from Digital Forms
ボットのトレーニング
示唆の使用方法
インテントとエンティティのパターンの使用方法
コンテキスト切り替えの管理方法
ボットのデプロイ
エージェント転送の設定方法
ボット関数の使用方法
コンテンツ変数の使用方法
グローバル変数の使用方法
Web SDK Tutorial(英語)
Widget SDK Tutorial(英語)
ボットの分析
カスタムダッシュボードの作成方法
カスタムタグを使ってフィルタリング
管理
ボット管理者コンソール
ダッシュボード
ユーザーの管理
ユーザーの管理
グループの管理
ロール管理
ボット管理モジュール
登録
ユーザーの招待
招待状の一括送信
ユーザーデータのインポート
Active Directoryからユーザーを同期
セキュリティ/コンプライアンス
シングル サインオンの使用
セキュリティ設定
Billing(日本未対応)
  1. ホーム
  2. Integrations
  3. Configuring the Freshservice ITSM Action

Configuring the Freshservice ITSM Action

The XO Platform lets you easily connect the Freshservice integration to allow you to create, view, update, and delete tickets in the system to manage your IT services. Click the Freshservice link to learn more.

This document explains the Freshservice configuration steps to enable, authorize, configure, and install the pre-built templates.

Authorizations Supported

The Kore.ai XO Platform supports basic authentication to allow Freshservice 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 Freshservice 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 Freshservice app to access an access token at runtime. To learn more about Freshservice account types, see Freshservice Documentation.

Step 1: Enable the Freshservice Action

Prerequisites:

Before enabling the Freshservice action, complete the following prerequisites:

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

Steps to enable the Freshservice action:

  1. Go to Build > Integrations > Actions.
  2. Once you click the Actions menu, all integrations are shown in the Available region. Select the Freshservice 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 Freshservice action using developer credentials:

  1. Go to Build > Integrations > Actions and select the Freshservice action.
  2. In the Configurations dialog, select the Authorization tab.
  3. 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 Freshservice account.
    • API Key – The secret API key of your Freshservice account.
  4. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

    Note: The Freshservice 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 Freshservice 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 Freshservice action at a user level:

  1. Go to Build > Integrations > Actions and select the Freshservice 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 Freshservice 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 Yes; some tasks will have tenancy URLs, and the user must provide the URLs to authenticate successfully.
      • Base URL – Enter the base tenant URL for the Freshservice instance.
      • Authorization Check URL – Enter the authorization check URL for your Freshservice 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 Freshservice Action Templates

Once you have configured a Freshservice 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 Freshservice ITSM Action

The XO Platform lets you easily connect the Freshservice integration to allow you to create, view, update, and delete tickets in the system to manage your IT services. Click the Freshservice link to learn more.

This document explains the Freshservice configuration steps to enable, authorize, configure, and install the pre-built templates.

Authorizations Supported

The Kore.ai XO Platform supports basic authentication to allow Freshservice 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 Freshservice 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 Freshservice app to access an access token at runtime. To learn more about Freshservice account types, see Freshservice Documentation.

Step 1: Enable the Freshservice Action

Prerequisites:

Before enabling the Freshservice action, complete the following prerequisites:

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

Steps to enable the Freshservice action:

  1. Go to Build > Integrations > Actions.
  2. Once you click the Actions menu, all integrations are shown in the Available region. Select the Freshservice 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 Freshservice action using developer credentials:

  1. Go to Build > Integrations > Actions and select the Freshservice action.
  2. In the Configurations dialog, select the Authorization tab.
  3. 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 Freshservice account.
    • API Key – The secret API key of your Freshservice account.
  4. Click Enable. When you configure the action for the first time, the Integration Successful pop-up is displayed.

    Note: The Freshservice 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 Freshservice 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 Freshservice action at a user level:

  1. Go to Build > Integrations > Actions and select the Freshservice 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 Freshservice 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 Yes; some tasks will have tenancy URLs, and the user must provide the URLs to authenticate successfully.
      • Base URL – Enter the base tenant URL for the Freshservice instance.
      • Authorization Check URL – Enter the authorization check URL for your Freshservice 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 Freshservice Action Templates

Once you have configured a Freshservice 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.
メニュー