Skip to main content
Tekma integrations let a workspace owner connect a team tool, then let capture editors send a reviewed report to that tool. The normal delivery is a text item with a sanitized source URL, capture kind, saved title and description, optional context, and a private Tekma link. It does not upload the recording, screenshots, comments, network payloads, or console logs. The person who opens the external item still needs Tekma access to open that private link.

​
Before you connect

Only a workspace owner can connect, manage, replace, or disconnect an integration. Members can use the configured destination when they have permission to edit the capture. Viewers cannot discover writable destinations or send. Availability of the OAuth button depends on the deployment’s configured OAuth client; a token option may be available even when OAuth is not. A connection is workspace-scoped and stores one active destination per provider. Credentials are not displayed again after saving.

​
Connect an app

  1. Open Settings → Integrations for the intended workspace.
  2. Choose Connect next to a provider. If a connection already exists, choose Manage.
  3. Choose Continue to [provider] for the provider authorization flow when it is offered, or choose Use a token instead and enter the token. Tekma verifies the credential before saving it.
  4. Enter the provider-specific destination fields shown by Tekma. Examples include a GitHub owner/repository, a Linear team ID, a Jira site URL and project key, a Notion database ID, or a Slack channel ID. Do not substitute a display name where the form asks for an ID.
  5. Choose Connect [provider] for a new connection or Save destination when an existing OAuth authorization only needs a destination. The row changes to Connected when setup is complete. A row marked Needs setup still needs its destination.
Choose Manage to change a destination without replacing credentials. Choose Disconnect to remove the Tekma connection; this does not revoke a provider token, so revoke a personal token at the provider separately. Reconnecting OAuth may bind a new provider identity and invalidate old provider-specific discovery choices.

​
Send and review a report

  1. Open a saved capture that you can edit and choose Send to app.
  2. Select the connected provider. Wait for Loading preview… to finish; use Retry preview if the destination metadata cannot load.
  3. Review the generated title, saved description, destination and provider fields. Provider forms expose only fields supported for that destination. Edit visible fields hides optional controls and clears their values; changing a destination clears destination-specific selections.
  4. Choose the provider’s exact send label, such as Send to GitHub, Send to Linear, Send to Jira, or Send to Slack. Nothing is created by merely opening the menu.
  5. Use the returned external URL to confirm the item. If the response says delivery was not confirmed, inspect the provider before sending again; Tekma does not automatically retry an uncertain create.
The available guides describe field limits, role differences, privacy, and recovery for GitHub, GitLab, Linear, Jira, Asana, ClickUp, Notion, Azure DevOps, Slack, Sentry, and Intercom. Sentry is read-only and is not listed in the ordinary Send to app menu. Intercom is a separate recording-request workflow.

​
Result and access

Issue and task providers receive the report text and private capture link. The destination item does not grant access to Tekma. Revoking a Tekma link prevents later reads but cannot retract text or copies already accepted by the external service. A successful provider response is recorded as a delivery receipt. Some providers are read back and compared with the requested fields; an item may already exist when a network timeout occurs, so inspect before retrying.