Skip to Content
DocsTools

Tools

Tools connect external services to Rhesis so you can export their content into your Knowledge base for use in test generation and other workflows.

This page covers importing knowledge into Rhesis from tools like Notion, GitHub, and Jira. If you want to call Rhesis from Cursor or Claude Code to explore endpoints and run tests, see Agent Skill instead.

Tools Page

Setting Up a Tool Connection

Every connection follows the same flow in Rhesis: on the Tools page, click Add tool connection, pick the provider, fill in the connection name, token, and any provider-specific fields listed below, then Test the connection and Save. Each provider below covers only how to generate its token and which extra fields it needs.

Notion

What's this for: Export knowledge into Rhesis
  1. Create a Notion integration at notion.so/profile/integrations/internal .
  2. In the “Content access” tab, grant access to the pages and teamspaces you want to export from — required for the integration to reach your content.
  3. In Rhesis, paste the token (starts with ntn...).

GitHub

What's this for: Export knowledge into Rhesis
  1. On GitHub, go to Settings → Developer Settings → Personal Access Tokens → Tokens (classic).
  2. Generate a classic token with the repo scope (full repository access).
  3. In Rhesis, add the repository URL and paste the token (starts with ghp...).

Jira

What's this for: Create an issue from a Rhesis task
  1. Go to id.atlassian.com/manage-profile/security .
  2. Under API tokens, click “Create API token” (not “Create API token with scopes” — Rhesis needs the classic unscoped token). Verify your identity, name the token, and set an expiration.
  3. In Rhesis, also enter your Atlassian email and workspace URL (yourorg.atlassian.net), then paste the token.

GitLab

What's this for: Export knowledge into Rhesis
  1. Go to avatar → Edit profile → Access → Personal access tokens.
  2. Generate a “Legacy token” (not “Fine-grained token”) with the api scope (or read_api for read-only). Name it and set an expiration.
  3. In Rhesis, add the project namespace (group/project, or a full project URL) and paste the token (starts with glpat-). Self-managed instances also need the GitLab API URL.

Asana

What's this for: Export knowledge into Rhesis
  1. Go to profile photo → My Settings → Apps → “Manage Developer Apps”.
  2. Under “Personal access tokens”, create a new token and copy it (shown only once).
  3. In Rhesis, paste the token. Optionally add a workspace GID to scope search and import.

Azure DevOps

What's this for: Export knowledge into Rhesis
  1. Sign in at https://dev.azure.com/{your_organization}, then go to user settings → Personal access tokens.
  2. Create a token with the required scopes (e.g. Work Items (Read)) or Full access, set an expiration, and copy it (shown only once).
  3. In Rhesis, enter your organization name (not the full URL), your Azure DevOps email, and the project, then paste the token.

Linear

What's this for: Export knowledge into Rhesis
  1. In Linear, go to Settings → Account → Security & access.
  2. Under “Personal API keys”, create an API key with an access level and copy it (shown only once, starts with lin_api_).
  3. In Rhesis, paste the token.

Shortcut

What's this for: Export knowledge into Rhesis
  1. In Shortcut, go to Settings → Your Account → API Tokens.
  2. Generate a token and copy it (grants full workspace access).
  3. In Rhesis, paste the token.

Watch this video to see how to connect your Notion workspace and export pages as knowledge sources:

Next steps

SDK EndpointsModels