Skip to content

Add Integration

2 min read

Use Add Integration from the workspace Integrations page to connect Hawzu with an external tool.


Select Add Integration to open the add window. Use search to find a tool, then select it.

Hawzu currently supports:

  • Jira
  • GitHub
  • GitLab
  • Jenkins
  • Azure DevOps
  • Slack
  • Linear

GitHub Actions and GitLab CI are no longer separate tiles. GitHub and GitLab are each one integration whose capabilities you choose — see Integrations Overview.


The first step lets you add optional details:

  • Integration Name
  • Description
  • Project Scope

Project scope can be All Projects or Selected Projects. If you choose selected projects, pick the projects where the integration should be available.

GitHub and GitLab also ask What should this integration do? here — tick Issues, the CI capability, or both.


The next step shows the credentials required by the selected tool. Examples include:

  • Jira site URL, email address, and API token
  • GitHub — no credentials to enter; you are taken to GitHub to install the Hawzu GitHub App
  • GitLab — authorize with GitLab, or supply an instance URL and personal access token
  • Jenkins URL, username, and API token
  • Azure DevOps organization URL and personal access token
  • Slack bot token
  • Linear API key

Follow the on-screen instructions for the selected tool.


Use Test Connection after entering credentials. Hawzu shows whether the connection succeeded or failed.

If the connection fails, review the credentials, token permissions, and URL values before trying again.


Some integrations need additional settings after a successful connection.

Issue-tracking tools ask for default issue creation settings, such as a project, repository, issue type, work item type, team, state, or labels.

GitHub and GitLab ask which repositories or projects this workspace uses, so test runs offer a short list rather than everything the provider allows. See Repositories and Projects in Use.

Slack asks for a channel and notification preferences.


Save is available after the connection is successful and required tool-specific settings are complete.

After saving, the integration appears in the Integrations table with its scope, status, and configuration details.