Integrations

On this page

• Available now
  • Jira (Growth/Scale)
  • Linear (Growth/Scale)
  • Slack (Growth/Scale)
  • Discord anomaly alerts (Scale)
  • Email (All plans)
  • REST API (Growth / Scale / Enterprise)
  • SSO/SAML (Enterprise)
• Coming soon
• Build your own

Available now

Jira (Growth / Scale)

Settings → Ticketing Integration → select Jira.

You will need:

• Site URL — https://your-org.atlassian.net
• Email — the email address of a Jira service account that has permission to create issues in the target project
• API Token — generate one at id.atlassian.com/manage-profile/security/api-tokens
• Default Project Key — the short prefix on your issue numbers (e.g. ENG if tickets are ENG-123)

Once saved, every time a finding is assigned to an owner in OpsCurb, a Jira issue is created automatically with the resource details, monthly waste, priority, and a due date. Ticket status syncs back in real-time if you register the webhook (POST /api/webhooks/jira), or once daily via the reconciliation job.

See How to turn AWS cost findings into Jira tickets for a full walkthrough.

Linear (Growth / Scale)

Settings → Ticketing Integration → select Linear.

You will need:

• API Key — generate one in Linear under Settings → API → Personal API keys
• Default Team Key — the identifier of the Linear team issues should go to (e.g. ENG)

Routing rules let you send findings with specific AWS resource tags to different teams and pre-assign them to a particular engineer (using their Linear user UUID).

Slack (Growth/Scale)

Settings → Slack Integration → Connect Slack (OAuth). OAuth stores workspace token + channel integration automatically. Optionally enable assignee DMs (bot scopes: chat:write, users:read, im:write, channels:read). This is a one-time setup per customer Slack workspace, done by a workspace admin. Step-by-step guidance: Onboarding Guide.

Discord anomaly alerts (Scale)

Create a webhook in Discord (Server Settings → Integrations → Webhooks), then in OpsCurb open Settings → Anomaly Alerts → Notification Channels and paste the webhook URL.

Email (All plans)

Configure email recipients in:

• Settings → Weekly Digest (weekly summary email)
• Settings → Anomaly Alerts (cost spike alerts)

REST API (Growth / Scale / Enterprise)

Use your Supabase access token and hit the API directly:

curl -H "Authorization: Bearer <SUPABASE_ACCESS_TOKEN>" \
  https://<your-railway-backend>/api/ai/preferences

See API Documentation for the full reference.

SSO/SAML (Enterprise)

Supports Okta, Azure AD, Google Workspace, OneLogin, and custom SAML 2.0. Email sales@opscurb.com to get set up.

Coming soon

Build your own

The REST API covers AI, scans, deep inspect, forecasting, and tagging workflows. See API Documentation. For Enterprise custom integrations (dedicated webhooks, custom data formats), email sales@opscurb.com.

Want something that's not listed? Email sales@opscurb.com with the tool name and your use case.