Home / Connectors / GitHub
Developer systems · Governed n8n fabric

GitHub × ServAI

Connect GitHub to the ServAI Data Intelligence Role Pack with explicit data boundaries, read-only execution, human approval and traceable evidence.

Start a connection assessmentAll connectors
CategoryDeveloper systems
Connection routeGoverned n8n fabric
Data modeRead-only
Publish authoritySeparate human release
What can be connected

The GitHub data you approve—not the whole account.

ServAI can read approved repositories, issues, pull requests and delivery metrics. An administrator defines the allowed datasets, fields, query windows and sensitivity ceiling. Exact availability depends on the customer’s GitHub plan, permissions and source configuration.

Boundary ruleThe agent cannot select an arbitrary account, table or resource from its prompt. Scope must be registered and approved first.
What Data Intelligence can do
  • Analyse approved engineering delivery measures
  • Compare work flow, review and release trends
  • Expose freshness and coverage limitations
  • Draft engineering dashboards with lineage
How the connection works

Configured, admitted and health-gated.

Implementation differs by connector state. These are the actual boundaries for this ServAI catalogue entry.

01

Grant entitlement

The customer grants least-privilege OAuth or an API credential and keeps it outside the agent prompt.

02

Review the n8n workflow

Nodes, pagination, rate limits, retries, transformations and resource scope are reviewed in customer-owned n8n.

03

Pin and admit the route

ServAI records the production HTTPS endpoint, workflow ID, SHA-256 digest and HMAC signing, then requires passing health.

Governed path

From source to a verifiable dashboard.

Connecting a source does not grant authority to change data, define metrics or publish.

  1. 01Configure connection
  2. 02Review & admit
  3. 03Approve meaning
  4. 04Read-only query
  5. 05Dashboard & evidence
  6. 06Different-person verify
  7. 07Separate release
What you need

Deployment requirements

  • Customer-owned n8n and a production workflow
  • Least-privilege OAuth or API entitlement
  • HTTPS, HMAC signing, workflow ID and pinned digest
  • Human owner for review, admission and health monitoring
What this connector cannot do

Fixed boundaries

  • ServAI does not write to GitHub or change source records.
  • No self-admission, self-approval of metrics or self-verification of dashboards.
  • The agent cannot submit raw SQL or arbitrary resource names.
  • A catalogue listing never means a customer connection is operating.
Status truth

Customer setup required

The customer control surface shows actual per-tenant state: operational, needs attention, or catalogued—not live. ServAI never turns a logo into a connection claim.

OperationalAdmitted and health passing
Needs attentionConfiguration, health or entitlement needs action
Catalogued—not liveNo admitted customer connection
GitHub + Data Intelligence Role Pack

Start with data scope—not a connector logo.

We will establish route state, requirements, human ownership and data boundaries before treating the connection as ready.

Start a connection assessmentExplore the Role Pack