Skip to main content
Back to Search AI connectors list Wrike is a task management and collaboration platform for planning, tracking, and managing work. The Search AI Wrike connector ingests tasks from Wrike, enabling search across task details, updates, and assignments.
SpecificationDetails
Repository typeCloud
Supported contentTasks
RACL supportYes
Content filteringNo

​
Prerequisites

Search AI connects to Wrike via OAuth 2.0. Register an OAuth client app in Wrike and obtain a Client ID and Client Secret before configuring the connector.

​
Registering a Client App in Wrike

  1. Go to Apps & Integrations > API Apps.
  2. Enter the app name and click Create new. Wrike generates a Client ID and Client Secret.
  3. Add the redirect URI for your region or deployment:
    • JP Region: https://jp-bots-idp.kore.ai/workflows/callback
    • DE Region: https://de-bots-idp.kore.ai/workflows/callback
    • Prod: https://idp.kore.com/workflows/callback
  4. Save the Client ID and Client Secret for use during connector configuration.

​
Configuring the Wrike Connector in Search AI

  1. Go to the Wrike Connector and select the Authorization tab.
  2. Enter the following details and click Connect.
    FieldValue
    NameUnique name for the connector
    Authorization TypeOAuth 2.0
    Grant TypeAuthorization Code
    Client IDClient ID from the Wrike OAuth app
    Client SecretClient Secret from the Wrike OAuth app

​
Content Ingestion

The content field of each ingested document includes task descriptions, status updates, comments, sub-tasks, and priority levels. Additional metadata fields capture the project the task belongs to, the assignee, the task creator, and creation and update dates. Sub-tasks associated with a task are included in the ingestion. If custom fields are configured in the Wrike account, all relevant custom field data is ingested into the raw_data field and the csf field of the document. Use the Document Workbench to extract and transform this data as needed.

​
RACL Support

Tasks in Wrike are organized under Spaces or Projects within an Organization. Permissions can be set at the user level or group level. User-level permissions: The sys_racl field contains the email addresses of the following users for each task:
  • Task assignees
  • Task authors
  • Task followers
  • Shared users (users with explicit access to the task)
Group-level permissions: When a task is shared with a group, the sys_racl field contains the Group ID. Use the Permission Entity APIs to associate users with the group entity.