Platform

Integrations

Connect source control, issue tracking, and notification systems.

Overview

Integrations connect the Zof Console to source control, issue tracking, CI/CD systems, notification channels, and cloud services. Connected integrations enable traceability from code changes to validation runs, automated pipeline triggers, and operational notifications to team channels.

Each integration documents required permissions, OAuth scopes, setup steps, and operational limitations. Availability varies by provider and organization configuration, verify connection status in the Console before documenting team runbooks.

Integration credentials are organization-scoped secrets managed through Admin Center and integration settings. Rotate credentials according to corporate security policy and monitor audit logs for connection changes.

Who should read this

  • Platform engineers, DevOps teams, and administrators connecting Zof to the broader engineering toolchain.

Prerequisites

  • Admin Center or integration management permission in the Zof Console
  • Provider admin access to authorize OAuth applications or install webhooks
  • Documented list of required integrations aligned to CI/CD and notification runbooks

When to use this workflow

  • Onboarding new team members to Zof terminology and workflows
  • Authoring internal runbooks aligned with Console labels
  • Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Inventory integration requirements

Identify source control, CI/CD, issue tracking, and notification systems requiring Zof connectivity.

Document data flows, what metadata transits between systems and retention implications.

Obtain security approval for OAuth scopes and webhook payload contents.

Open Integrations in the Console

Navigate to Platform → Integrations in the Zof Console.

Review available providers and connection status for your organization.

Select the integration to configure and read provider-specific prerequisites.

Authorize and configure connection

Complete OAuth authorization or API credential entry following provider prompts.

Specify repositories, projects, or channels subject to integration scope limits.

Test connection health using built-in validation before enabling dependent workflows.

Enable workflow features

Configure CI/CD triggers mapping pipeline events to Console runs or gate evaluations.

Enable issue creation or linking from Test Health failures where supported.

Route notifications to team channels for runs, gates, and approval requests.

Validate end-to-end behavior

Execute a test pipeline run or manual trigger confirming Console receives events.

Verify run results, metadata, and links appear correctly in external systems.

Document integration behavior and failure modes in team runbooks.

Maintain and rotate credentials

Monitor integration health dashboards and audit logs for authorization failures.

Re-authorize OAuth tokens before expiration according to provider policies.

Revoke integrations promptly when repositories decommission or teams reorganize.

Key concepts

Organization scope
All Zof Console and API operations are isolated to your authenticated tenant.
Governed execution
Agent output and remediation follow policy packs with human approval when configured.

Best practices

  • Use separate integration connections per environment, staging versus production pipelines.
  • Scope OAuth permissions to minimum repositories and projects required.
  • Include integration status checks in deployment runbooks before release-critical validation.
  • Never embed integration secrets in source control, use Console-managed credentials.
  • Review connected integrations quarterly and remove unused providers.

Common issues

OAuth authorization fails or loops
Verify callback URLs, provider app registration, and admin consent requirements for enterprise OAuth apps.
Pipeline triggers not starting Console runs
Confirm webhook delivery, API key permissions, and mapping configuration between pipeline branches and Console projects.
Stale token causes silent integration failure
Re-authorize connections proactively before token expiry. Monitor audit logs for authentication error patterns.

Was this page helpful?

Integrations | Zof AI Documentation