DEVELOPERS · INTEGRATIONS · CONNECTORS

Integrations.

Connectors for the systems your team already runs. Release gates, proof archives, incident response, and the channels operators watch — wired with verified payloads.

Plan a pilot Open the docs

EVENT · WEBHOOK · CONNECTOR · SIGNED

SHIPPING

16 connectors

Already wired into the release path. Typed payloads, signed delivery, evidence attached.

6 mature

Production-grade connectors covering release gates, archives, and operator channels.

Connected workflows keep their receipts.

Whether the connector is native or a raw webhook, downstream tools still understand what fired, what changed, and what should happen next.

STEP 01

WHAT WE LISTEN FOR

Choose events

Decide which events matter: run.completed, review.escalated, export.ready, or alert.created.

→

STEP 02

WHAT WE WIRE

Register destinations

Configure connectors or webhook endpoints with the scopes and verification rules your program requires.

→

STEP 03

WHAT WE PRESERVE

Keep evidence attached

Every downstream notification still points back to the run, proof bundle, and audit trail that triggered it.

CONNECTOR GROUPS

Grouped around the real work.

The catalog is easier to scan when it matches how teams work — releases, data, incidents, collaboration, observability.

CI / CD

4 CONNECTORS

Gate releases with evaluation results before code or model changes ship.

Data and storage

4 CONNECTORS

Archive exports, results, and proof where analysts and auditors already look.

Incident response

2 CONNECTORS

Turn critical failures and escalation events into tickets, alerts, and response workflows.

Team channels

3 CONNECTORS

Push the right summary and proof link into the channels that keep operators aligned.

Observability

3 CONNECTORS

Stream health and run updates into the dashboards teams already trust during release windows.

SELECTED CONNECTOR

Inspect the quickstart.

CONNECTOR

GitHub Actions

Gate releases with evaluation results before code or model changes ship.

DOCS

/developers/integrations

PRIMARY USE

Connected workflow · proof attached

NEXT STEP

Pair quickstart with webhook verification

github-actions.ts

● QUICKSTART

await client.integrations.github.dispatchWorkflow({ owner: 'aura', repo: 'evals', workflowId: 'ci.yml', ref: 'main' });

RAW WEBHOOK

Verify the signature. Route the event.

One handler. HMAC-signed delivery. Same response shape as the SDK. Archive, alert, or route from a single endpoint.

webhook-handler.ts

● SIGNED

import { createHmac } from "crypto";

app.post("/webhooks/auraone", (req, res) => {
  const signature = req.headers["x-auraone-signature"];
  const expected = createHmac("sha256", process.env.AURAONE_WEBHOOK_SECRET!)
    .update(JSON.stringify(req.body))
    .digest("hex");

  if (signature !== expected) return res.status(401).end();

  if (req.body.event === "run.completed") {
    archiveToS3(req.body.data.evidenceUrl);
    postToSlack(req.body.data.summary);
  }

  res.status(200).json({ received: true });
});

INTEGRATIONS

Wire the stack. Keep the proof.

Map your connector choices, webhook events, and review outputs to a concrete docs path or a pilot engagement.

↳ STARTS WITH

Pick the events. Choose the destinations. Verify the signature once.

↳ LEAVES WITH

Connected workflows, proof attached, evidence routed downstream.

Plan a pilot Open the docs