Skip to main content

Documentation Index

Fetch the complete documentation index at: https://koreai.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

Back to Search AI connectors list Wolken Service Desk is a cloud-based IT service management (ITSM) platform used by organisations to manage support cases, tickets, and knowledge base content. You can configure Search AI to connect to Wolken Service Desk to enable users to fetch query results using knowledge base articles and support cases from your Wolken instance.
SpecificationDetails
Repository typeCloud
Supported contentKnowledge Base Articles and Cases/Tickets
Content filteringYes (created on, updated on, case status, business unit, and custom filters)
RACL supportYes

​
Authorization Support

Search AI supports custom API-based authentication for communicating with Wolken Service Desk. Authentication requires a Host URL, Domain, Client ID, Service Account, Refresh Token, and Authorization Code associated with your Wolken instance.

​
Integration Steps

To configure Wolken Service Desk as a content source, complete the following steps.
  • Configure the Wolken Service Desk connector in Search AI
  • Set up Permissions
  • Configure Content Filters
  • Schedule Sync

​
Step 1: Configure the Wolken Service Desk Connector in Search AI

Go to Connectors under the Sources page and select Wolken Service Desk. On the Authentication tab, enter the following details and click Connect.
FieldDescription
NameA unique name for this connector instance.
Host URLThe API endpoint for your Wolken instance (for example: https://api-{domain}.wolkenservicedesk.com/wolken-secure).
DomainYour organisation’s Wolken domain (for example: your-org.wolkenservicedesk.com).
Client IDThe client identifier for your Kore.ai integration (for example: cl-your-org-xxxx).
Service AccountThe service account email used to access Wolken (for example: service_account@company.com).
Refresh TokenThe refresh token used to obtain access tokens for API calls.
Authorization CodeThe authorization code issued during the OAuth handshake with Wolken.
Once successfully authenticated, the status shows as Connected.

​
Step 2: Set Up Permissions

Go to the Permissions tab to configure access control for the ingested content. The following options are available.
  • Same users as in the source system (Restricted Access) - Applies RACL-based access control. Permissions are enforced using platform/RACL configuration. Note that permissions aren’t continuously auto-synced from Wolken; any permission changes in the source system must be updated manually via RACL configuration.
  • Everyone (Public Access) - All users are granted full access to the ingested content, overriding any previous restrictions in the connector.
Automatic permission sync is not supported for the Wolken Service Desk connector. Attachment files are not ingested as part of the connector flow.

​
Step 3: Configure Content Filters

Go to the Content Filters tab under Connector Setup to define the scope and filters for content ingestion. Filters can be applied across both knowledge base articles and cases/tickets.
Filter ParameterDescriptionExample Value
Created On (from)Only include content created on or after this date.2024-01-01
Created On (to)Only include content created on or before this date.2025-12-31
Updated On (from)Only include content last updated on or after this date.2024-01-01
Updated On (to)Only include content last updated on or before this date.2025-12-31
Case statusFilter cases by status (for example: open, closed, resolved).Open, Closed
Business unitLimit ingestion to content belonging to a specific business unit.IT Support
Custom filtersAdditional query-style filters can be configured to further narrow ingestion scope based on Wolken-specific fields.-

​
Step 4: Sync Content

After configuring the connector, go to Schedule Sync to initiate and manage content synchronization.
  • Use the Sync button for an immediate, on-demand sync.
  • Enable Schedule Sync to set up automated, recurring syncs.
The connector supports both Full Sync and Incremental Sync. During an incremental sync, only content is created or updated since the last sync is processed, reducing API load and sync time for large instances. The Schedule Sync table displays a log of all sync activity with the following details.
FieldDescription
Sync ScopeThe scope of the sync (for example, Full Sync).
Sync TypeIndicates whether the sync was On-Demand or Scheduled.
Sync StatusThe result of the sync (for example, Successful).
Triggered ByThe user who initiated the sync.
Started OnThe date and time the sync started.
Completed OnThe date and time the sync completed.

​
Content Ingestion

Once the sync is complete, go to the Content tab to review the ingested content. The tab displays the count of files that are Successful, Failed, and Skipped, along with the total number of Accessible Files. Search AI ingests two content types from Wolken Service Desk.

​
Knowledge Base Articles

The following key fields are extracted and indexed for each knowledge base article.
  • title - The title of the knowledge base article.
  • content - The body text of the article, made available for search operations.
  • doc_id - A unique identifier for the ingested article, derived from the article ID in Wolken.
  • doc_source_type - Identifies the content type as a knowledge base article.
  • doc_created_on / doc_updated_on - Timestamps capturing when the article was created and last updated in Wolken.
  • url - The URL pointing to the article in the Wolken portal, if available.

​
Cases / Tickets

The following key fields are extracted and indexed for each case or ticket.
  • title - The subject or title of the support case.
  • content - The description and case history, including relevant case updates modelled for search.
  • doc_id - A unique identifier for the ingested case, derived from the case/ticket ID in Wolken.
  • doc_source_type - Identifies the content type as a support case.
  • doc_created_on / doc_updated_on - Timestamps capturing when the case is created and last updated.
  • url - The URL pointing to the case in the Wolken portal, if available.
  • status - The current status of the case (for example: Open, Closed, Resolved).
  • business_unit - The business unit associated with the case.
Attachments associated with cases or articles aren’t ingested as separate downloadable files in the connector flow.

​
RACL Support

Search AI provides access control support for content ingested from Wolken Service Desk. The sys_racl field is used to enforce access control by associating relevant identifiers with the ingested content, ensuring that users can only access the content they’re authorised to view.
FeatureStatus
RACL SupportAvailable (can be enabled)
RACL SyncNot applicable (manual configuration required)
  • When RACL is disabled (default), all synced content is publicly accessible to all users searching the index (permission set to *).
  • When RACL is enabled, the connector uses RACL platform configuration to enforce access control. Since automatic permission sync isn’t supported, the Permission Entity APIs must be used to manually associate users with the appropriate permission entities after ingestion.
  • sys_racl can include wildcard (*) for publicly accessible content, or explicit user/group identifiers for restricted content.