Integrations

Integrations connect Viberglass to the systems your team already uses for source control, ticketing, and chat. The Integrations page (Platform sidebar → Integrations) is where you configure them, and the project's Settings → Integrations sub-page is where you link an integration to a particular project.

Available Integrations

• GitHub — SCM. Native GitHub Issues integration with webhook support and pull-request linking. Supports inbound webhooks (issues become tickets) and outbound feedback (job started/job ended comments back to the issue).
• Slack — Ticketing. Handle /viberator slash commands and thread approvals and is the easiest way to manage tickets for non-admin/non-developer users. See Slack for the more information flow.
• Custom Webhook — Inbound. Receive tickets from any external system via a simple JSON webhook. Configure as many independent endpoints as you need; each one has its own URL, secret, and delivery history. Outbound destinations let you forward job_started / job_ended events to your own systems with optional HMAC signing.
• Shortcut — Ticketing. Project management integration for software teams (formerly Clubhouse).

Configuring GitHub

GitHub is the most common integration. To connect a repository:

1. Open Integrations in the global sidebar.
2. The GitHub tile shows Connected if it has been configured before. Click Manage to open its detail page.
3. Inbound webhook. Click Create GitHub Inbound Webhook. Fill in the routing scope (Viberglass project + GitHub owner/repo) so inbound issues land in the right project. The page generates a unique webhook URL and a webhook secret.
4. In GitHub, open Settings → Webhooks for the repository. Use the generated URL as the Payload URL, set content type to application/json, paste the secret into the Secret field, and enable the events you need (issues, issue_comment, pull_request, etc.).
5. Integration credentials. Under Integration Credentials, click Add Credential and pick the secret holding your GITHUB_TOKEN. The token must allow comments on issues, label updates, branch creation, and push access. The credential becomes selectable from the project's SCM Execution settings.
6. Outbound feedback. The integration always sends job_started and job_ended updates back to the originating issue once a project is mapped. The mapping is configured implicitly when you save an inbound webhook for that repository.
7. Delivery history is shown on the same page so you can debug failed inbound deliveries.

Configuring Slack

Slack as a ticketing integration handles /viberator slash commands and thread approvals and is the easiest way to manage tickets for non-admin/non-developer users. See Slack for the more information flow.

Configuring a custom webhook

The Custom Webhook integration is the escape hatch for any system Viberglass doesn't speak natively.

Inbound

1. Open the Custom Webhook tile and click Create custom inbound endpoint.
2. Each endpoint produces its own URL and HMAC signing secret.
3. POST application/json payloads to the URL. Sign the raw request body with HMAC-SHA256 using the endpoint secret and pass the signature in the configured header.
4. Inbound deliveries appear in the Delivery history panel with status and any error messages.

Linking an integration to a project

Configuring an integration globally is not enough — you also need to link it to each project. Open the project, then Settings → Integrations to mark one as the primary ticketing integration and one as the primary SCM integration.

A project's primary SCM integration is what the Project settings sub-page reads from when you pick the SCM Integration dropdown and the Integration Credential dropdown — those are the credentials a clanker uses when it clones, commits, and pushes.

Removing or rotating credentials

Credentials live on the integration, not on the project. To rotate a token:

1. Open Integrations → GitHub (or whichever integration).
2. Find the credential under Integration Credentials.
3. Click Edit to set a new secret reference, or Delete to remove it (and recreate later).

Tokens are stored as references to entries in the Secrets page. To change the actual secret value, edit the secret in the Secrets page — the integration credential automatically picks up the new value.