Forge Logger Docs← Back to app

Integrations

Integrations connect Forge Logger to external issue trackers and notification services. When configured, bug reports can be exported as issues or notifications automatically or manually.

Supported providers

ProviderWhat it does
GitHubCreates a GitHub Issue in the configured repository
GitLabCreates a GitLab Issue in the configured project
JiraCreates a Jira ticket in the configured project
DiscordSends a formatted message to a Discord webhook URL
WebhookSends a POST request with the report payload to a custom URL

Setting up an integration

Navigate to your project’s Settings page and open the Integrations section.

GitHub

  1. Click Add GitHub Integration
  2. Provide:
    • Repository — e.g. owner/repo (in the config object)
    • Access token — a GitHub personal access token with repo scope (stored encrypted)
  3. Set upload mode to manual or automatic
  4. Save

GitLab

  1. Click Add GitLab Integration
  2. Provide:
    • Project ID — the GitLab project ID
    • GitLab URL — your GitLab instance URL (for self-hosted)
    • Access token — a GitLab personal access token with api scope
  3. Save

Jira

  1. Click Add Jira Integration
  2. Provide:
    • Project key — the Jira project key (e.g. GAME)
    • Jira URL — your Jira instance URL
    • Email and API token — Jira credentials
  3. Save

Discord

  1. Click Add Discord Integration
  2. Provide:
    • Webhook URL — a Discord webhook URL for the target channel
  3. Save

Webhook

  1. Click Add Webhook Integration
  2. Provide:
    • URL — the endpoint that will receive POST requests
    • Secret — optional shared secret for request signing
  3. Save

Upload modes

ModeBehavior
ManualReports are exported only when you click “Export” on a report
AutomaticEvery new report is automatically exported to the configured provider

Managing integrations

  • Enable / Disable — toggle an integration without removing it
  • Update — change the configuration or credentials
  • Delete — remove the integration entirely

Security

  • Integration secrets (tokens, API keys, webhook secrets) are encrypted at rest using GCP Cloud KMS envelope encryption.
  • The hasSecret flag indicates whether a secret is configured.
  • The secretFingerprint shows a hash of the stored secret for verification.
  • Secrets are never returned in API responses — only the fingerprint is visible.