Skip to content
Reloqui Docs

Connect integrations

Connectors feed the evidence pipeline. Reloqui supports twelve source types, all managed from Integrations.

Source types

Section titled “Source types”
Category Sources
Source control GitHub, GitLab, Bitbucket, Azure DevOps
Issue trackers Jira, Linear
Delivery CI/CD (Jenkins/CircleCI/Buildkite…), Deployments (ArgoCD/Helm/K8s), Registry (Docker Hub/GHCR)
Infrastructure Terraform (Terraform Cloud/HCP)
Reliability Incidents (PagerDuty, Opsgenie)
Testing Synthetic — a built-in generator for demos and trials

Add a connector

Section titled “Add a connector”

Integrations → Add integration. Pick a source, give it a name, and provide its config:

  • GitHub / GitLab / Bitbucket / Azure DevOps — a token (PAT / app password) and repo/org identifiers.
  • Jira / Linear — site + API token, with an optional project/team key allow-list to avoid key collisions.
  • CI/CD / deployment / registry / Terraform / incident — usually webhook-only; you get a generated webhook URL + secret to paste into the source.

Two ways evidence arrives

Section titled “Two ways evidence arrives”
  1. Webhooks (push) — the source calls a Reloqui endpoint the moment something happens. Signatures/tokens are validated and the raw payload is archived before processing. Endpoints answer in well under 5 seconds and process asynchronously.
  2. Polling & sync (pull) — a scheduler pulls each connector on its own cadence (config.pollIntervalMinutes), and you can trigger an on-demand Sync or a time-window backfill/replay any time.

Webhook setup

Section titled “Webhook setup”

Each connector’s page shows exact instructions for its source, including the generated URL and secret:

  • GitHub — HMAC-signed (X-Hub-Signature-256); handles pull_request, push, create, workflow_run, deployment_status, package.
  • GitLab — X-Gitlab-Token; handles push, MR, pipeline, deployment.
  • Jira — token in the URL (?token=…); issue and version events.
  • Generic sources — POST /api/v1/webhooks/{source}/{connectorId}?token=… with a documented JSON contract, or native vendor payloads (Docker Hub push, Terraform Cloud run notifications, PagerDuty v3, Opsgenie).

Field mapping & attribution

Section titled “Field mapping & attribution”

Evidence is attributed to a service by matching repository URL (or serviceSlug in generic payloads). For Terraform, a workspace → service map on the connector links a workspace to a service. Connectors can also remap custom payload keys onto the generic contract via config.fieldMap.

Resilience

Section titled “Resilience”
  • Circuit breakers — per-connector, Redis-backed (opens after repeated failures, half-open probe to recover). Surfaced on the connector status.
  • Rate limiting — Jira 429/Retry-After is honored and backs off.
  • Dead-letter queue — failed deliveries are captured and can be replayed or discarded by an operator (see Operations).

Sync & backfill

Section titled “Sync & backfill”
  • Sync now — pull recent history for a connector on demand.
  • Backfill / replay — re-pull a time window: POST /api/v1/admin/replay { "integrationId": "int_…", "since": "2026-01-01T00:00:00Z" }. Idempotent — stable dedup keys prevent duplicates.
Section titled “Related”