Integrations & API tokens

talksprout can create issues in Linear, GitHub, and Azure DevOps directly from any feedback submission. Each integration requires an API token from the respective service. This guide covers how to generate the right token with the minimum permissions needed.

Linear

talksprout uses your personal Linear API key to create issues in a team you specify.

1. 1

   Open Linear API settings

   Go to linear.app/settings/api. You need to be signed in to your Linear account.

2. 2

   Create a personal API key

   Under Personal API keys, click Create key. Give it a descriptive label — e.g. talksprout — so you can identify and revoke it independently later.

   Security note — Use a Personal API key, not an OAuth application key. Personal keys are scoped to your account and easier to audit and revoke.
3. 3

   Copy the key

   The key is only shown once. Copy it immediately and paste it into the Linear connect modal in talksprout.

4. 4

   Fetch your team

   After pasting the key in talksprout, click Fetch teams. talksprout will query Linear with your key and show a dropdown of teams you have access to. Select the team where issues should be created and click Save.

GitHub

talksprout uses a fine-grained personal access token to create issues in a single repository.

1. 1

   Open the token creation page

   Go to github.com/settings/personal-access-tokens/new (GitHub → Settings → Developer settings → Fine-grained tokens → Generate new token).

2. 2

   Configure the token

   Fill in the following:

   • Token name — e.g. talksprout
   • Expiration — set a reasonable expiry (90 days or 1 year). Tokens should not be permanent.
   • Resource owner — your account or the org that owns the repository
   • Repository access — choose Only select repositories and select the single repo where issues should be created
3. 3

   Set permissions

   Under Repository permissions, find Issues and set it to Read and write. That is the only permission talksprout needs. Leave all other permissions as No access.

   Security note — Do not use a classic personal access token with the repo scope — that grants full read/write access to all your repositories. Fine-grained tokens scoped to a single repo are significantly safer.
4. 4

   Generate and copy

   Click Generate token. Copy it immediately — GitHub will not show it again. Paste it into the GitHub connect modal in talksprout along with the repository owner and name.

Azure DevOps

talksprout uses a Personal Access Token to create Issues in an Azure DevOps project. Issues are the default work item type on Basic process boards.

1. 1

   Open Azure DevOps

   Sign in at dev.azure.com and navigate to your organisation.

2. 2

   Create a Personal Access Token

   Click your avatar in the top-right corner and choose Personal access tokens → New Token. Give it a descriptive name — e.g. talksprout — and set the shortest expiry that works for your team.

   Under Scopes, select Custom defined then find Work Items and enable Read & write only. Leave all other scopes unchecked.

   Security note — Do not use Full access scope — that grants talksprout (and anyone who obtains the token) access to your entire Azure DevOps organisation. Work Items read & write is the only permission needed.
3. 3

   Copy the token

   Click Create and copy the token immediately — Azure DevOps will not show it again.

4. 4

   Enter the details in talksprout

   In the Azure DevOps connect modal, enter:

   • Personal Access Token — the token you just copied
   • Organization — the name from dev.azure.com/{organization}
   • Project — the name of the project where issues should be created

   talksprout will create all work items as Issues — the default type on Basic process boards. If your project uses a different process template (Agile, Scrum), the issue type may not exist and creation will fail.