Integrations: Jira, GitHub, Slack and more

Integrations: Jira, GitHub, Slack and more

Findings are only useful once they reach the tools your team already works in. Open Config → Integrations to connect Vooki Pro to your issue tracker and chat.

Ticketing

Five platforms are supported: Jira, GitHub Issues, Linear, GitLab and Azure DevOps. Each has its own tab, and the setup is the same for all of them:

  1. Enter the connection details and a token.
  2. Click Test Connection. Vooki Pro loads your projects, repositories or teams so you can pick from a list.
  3. Choose the destination and the issue or work-item type.
  4. Save, and mark the platform active.
PlatformWhat you need
JiraSite URL (for example https://yourcompany.atlassian.net), account email and an Atlassian API token. Then pick the project and issue type.
GitHubA personal access token that can create issues on the target repositories.
LinearAn API key from Linear settings. Then pick the team.
GitLabhttps://gitlab.com or your self-hosted URL, and an access token with issue-creation scope.
Azure DevOpsOrganisation, project, and a personal access token with work-item permissions.

Once connected, click Create Ticket on any finding. The title, severity, affected URL, description, remediation and request/response evidence are filled in for you.

Notifications

  • Slack: paste an incoming webhook URL from your Slack app. Alerts go to that webhook's channel.
  • Generic webhook: any HTTPS endpoint. Vooki Pro POSTs findings to it, so you can route them anywhere.

Notifications are what make scheduled scans worth having: an overnight scan that finds something critical can say so before anyone opens the app.

Practical advice

  • Triage before you file. Mark false positives first, or your team will have to close those tickets by hand.
  • Use a scoped token that can create issues, not administer the repository.
  • Notify on severity, not everything. People mute a channel that receives every Info finding.

Full reference: Integrations (docs)