Skip to main content
Orizon supports integrations with GitHub, GitLab, and Azure DevOps. Connecting one of these providers to a project lets you sync issues as requirements and receive real-time webhook events when issues change, pull requests open, or CI/CD pipelines run.

GitHub

Sync issues as requirements. Receive events for issues, pull requests, pushes, and workflow runs.

GitLab

Sync issues as requirements. Receive events for issues, merge requests, pushes, and pipelines.

Azure DevOps

Sync work items as requirements. Receive events for work items, builds, and git pushes.

​
Connecting an integration

Each project supports one active integration at a time.
1

Connect your account in Settings

Before linking an integration to a project, you need to authorize Orizon to access your provider. Go to Settings and navigate to the tab for GitHub, GitLab, or Azure DevOps. Follow the OAuth connection flow for your provider.
If your account is already connected in Settings, it will show as Connected on the integrations page and you can skip this step.
2

Open your project's integrations page

Navigate to your project, then go to Settings → Integrations in the project navigation.
3

Select a provider

The integrations page shows the three available providers. Providers for which your account is already connected show a Connected badge and an Enable for this Project button. Click it to open the integration configuration form.If your account is not connected yet, click Connect in Settings to authorize it first.
4

Configure the integration

In the configuration form, provide the repository owner and repository name (for GitHub and GitLab) or the organization and project details (for Azure DevOps). You can use your existing OAuth connection or provide a Personal Access Token manually.
5

Save

Orizon tests the connection and saves the configuration. After saving, a Webhook URL and Webhook Secret are generated for your project.

​
What syncs

Once an integration is active, you can trigger a manual sync from the integrations settings page:
Orizon fetches all issues from the connected repository and maps them to requirements:
  • Issue title → requirement title
  • Issue body → requirement description
  • Issue labels → requirement priority and status
  • Issue number → external ID, with a link back to the GitHub issue
Re-syncing updates existing requirements rather than creating duplicates, matching on external ID.
Orizon fetches all issues from the connected GitLab project and maps them to requirements using the same field mapping as GitHub. The external ID is the GitLab issue IID, and a direct link back to the GitLab issue is stored.
Orizon fetches work items from the connected Azure DevOps project. Work item titles, descriptions, and state map to requirement fields. The work item ID is stored as the external ID with a link back to Azure DevOps.

​
Webhooks

Webhooks let Orizon receive real-time events from your provider without polling. After connecting an integration, Orizon generates a unique webhook URL for your project.

​
Setting up webhooks

1

Copy the webhook URL

On the integrations settings page, the Webhook URL field shows the URL for your project. Click Copy to copy it to the clipboard. The URL has the form:
https://qa.orizon.sh/api/integrations/{provider}/webhook?project={projectId}
2

Configure the webhook in your provider

In your GitHub repository, go to Settings → Webhooks → Add webhook. Paste the URL into Payload URL. Set Content type to application/json. Paste the webhook secret from Orizon into the Secret field. Select the events you want to send — at minimum, Issues, Pull requests, Pushes, and Workflow runs.

​
Supported webhook events

EventWhat Orizon does
issues (opened)Creates a new requirement
issues (edited / closed)Updates the existing requirement
pull_request (opened / synchronize)Creates a test run record linked to the PR
pushStores commit data and links commits to requirements or test cases referenced in the commit message
workflow_run (completed)Creates a test run record with pass/fail status from the workflow conclusion

​
Webhook delivery log

The integrations settings page shows the last 10 webhook events received for your project. Each entry shows the source, event type, processing status (Processed, Pending, or Failed), and timestamp. Use this log to verify that your webhook is configured correctly and events are arriving as expected.

​
Disconnecting an integration

To remove an integration from a project:
1

Open the integrations settings page

Navigate to your project’s Settings → Integrations.
2

Click Manage

On the active integration card, click Manage to open the configuration form.
3

Disconnect

Use the disconnect option in the configuration form. This removes the integration from the project and clears the webhook secret.
Disconnecting an integration does not delete requirements that were previously synced from it. Those requirements remain in the project and retain their external ID and URL fields.
After disconnecting, you can connect a different provider or re-connect the same one with new credentials.