Connect your existing tools.

Settings → Integrations → Slack → Add to Slack. Approve in Slack and choose the channel to post into, that single step connects the channel webhook and 1:1 DMs together. No webhook URLs or tokens to copy.

In Slack, go to Apps → Incoming Webhooks → Add to Slack, pick the channel to post into, and copy the webhook URL (it starts with https://hooks.slack.com/services/…).

Settings → Integrations → Slack. Paste the URL, optionally label the channel, and choose which alerts to send (critical findings, cost anomalies). Save, then use Send test to confirm.

Go to api.slack.com/apps → Create New App → From scratch, name it (e.g. “trueno”), and select your workspace.

Under OAuth & Permissions → Bot Token Scopes, add users:read and users:read.email (match the assignee by email; Slack requires both together), chat:write (send the message), and im:write (open the DM).

Click Install to Workspace and authorize. Copy the Bot User OAuth Token. It starts with xoxb-.

Settings → Integrations → Slack direct messages. Paste the xoxb- token, enable “DM on assignment,” and use DM me a test. Assignees are matched by their trueno profile email. If someone isn’t in the Slack workspace under that email, their DM is quietly skipped (the channel alert still fires).

In PagerDuty, open the service → Integrations → Add an integration → Events API v2, and copy the Integration/Routing Key.

In Opsgenie, create an API integration (or use Teams → Integrations) and copy its API key.

Settings → Integrations → On-call. Pick the provider, paste the key, enable it, and send a test page. Critical findings will open an incident automatically.

Create a fine-grained or classic PAT with issues: write on the target repo. In trueno pick GitHub, enter the repo as owner/name, and paste the token.

Create an API token at id.atlassian.com → Security → API tokens. In trueno pick Jira and enter your site URL (https://your-site.atlassian.net), the project key (e.g. OPS), the Atlassian account email, and the token. Issues are created as type Task.

Create a personal API key at Linear → Settings → API, and copy the team’s UUID. In trueno pick Linear, paste the team id and the API key.

Settings → Integrations → API keys → Create key. Copy it immediately; it’s shown once. Call the API with Authorization: Bearer <key>.

GET /api/v1/findings, /recommendations, /resources, and /accounts, all org-scoped to your key, with ?limit and per-endpoint filters. The full schema is published as OpenAPI 3.1 at /api/v1/openapi.json.

Add an endpoint under Webhooks and pick events (critical finding, cost anomaly). Each POST is signed: X-Trueno-Signature: sha256=<hmac> over the raw body, keyed by the signing secret shown at creation. Verify it before trusting the payload.

Every delivery is logged under Recent deliveries. A failed delivery (non-2xx or timeout) is retried automatically with exponential backoff, so a brief outage on your side doesn’t drop the event.