Skip to main content

Integrations and API

Workspace-level integrations live in Alerting, Integrations; machine access (tokens) lives in My account, API tokens and Settings, AI agents.

Slack​

Connect with one OAuth click (you pick the workspace and channel), and incidents arrive as a digest with Ack and Resolve buttons that act directly; the message updates so the channel sees who took it. Slash commands work too:

/wakora incidents     current incidents
/wakora hosts         fleet at a glance
/wakora ack 42        acknowledge #42
/wakora resolve 42    resolve #42

Actions are attributed to the Slack user by their linked account. "Sign in with Slack" on the login page rides the same connection. Available on Starter and above.

Microsoft Teams​

Incidents post to a channel as cards: create an incoming workflow ("when a webhook request is received") in your Teams channel and paste its URL into the Teams card. One-way today (cards with links back to the console).

Jira​

Connect Jira Cloud (site, email, API token, project) and incidents become issues two ways: a create issue button on any incident row, and optionally automatic issues for new criticals. When an incident resolves, the issue gets a resolution comment. Repeat clicks answer the existing issue instead of duplicating. Available on Pro and above.

Team webhook​

A workspace-level webhook receives published alerts as JSON, signed with a secret shown next to the row (verify the signature header on your side). Personal webhooks (per user) live in My account; status-page subscriber webhooks are separate, see Status pages.

Prometheus​

Scrape your fleet into your own Prometheus or Grafana: https://api.wakora.io/v1/prometheus with a read token exposes host meters, incident counts and usage axes, plus raw series on request. Details in the Prometheus export.

The REST API​

Everything the console shows and does, over JSON: https://api.wakora.io/v1/... with a Bearer token. Personal tokens are minted in My account, API tokens (bound to one workspace, scoped read/act/admin, never above your own role). The full endpoint list, scopes, errors and examples: API reference. Available on Pro and above.

MCP for AI agents​

Let an AI agent (Cursor, Claude, anything MCP-capable) monitor and act on your workspace: Settings, AI agents mints a team token and shows the ready client snippet for https://mcp.wakora.io. The agent gets over thirty tools, from listing hosts and querying metrics to acknowledging incidents and saving rules, under the same read/act/admin scopes. Every action is audited, and anything an AI does shows an "AI" badge on the incident instead of a person's avatar, so the timeline never lies about who acted. Available on Business and above.