integrations

The stack an investigation reads.

Hinto pulls from the services you connect and posts back where your team already works. You choose what to connect and can disconnect any of them from Settings at any time.

investigation pipeline

Intake, evidence, then handoff.

Intake

Slack
SlackRequired

Evidence

GitHub
GitHub
Sentry
Sentry
Browser SDK
Browser SDK

Handoff

Linear
Linear
MCP
MCP
  • Slack

    Slack

    Required

    Tickets start in the channels you choose.

    Reads
    Selected channel messages and thread context.
    Writes
    Findings and status updates back into the thread.
  • GitHub

    GitHub

    Read-only code at the commit that was live.

    Reads
    Repository files and commit history through a scoped GitHub App.
    Writes
    Nothing. Hinto never writes to your repo.
  • Sentry

    Sentry

    Errors and stack traces for the ticket window.

    Reads
    Matching errors from your connected Sentry account.
    Writes
    Nothing. Separate from the Sentry project Hinto uses for its own crashes.
  • Browser SDK

    Browser SDK

    Session evidence from your product.

    Reads
    Visit events from @gethinto/browser-sdk in your web app.
    Writes
    Nothing. Records what a user did, not what they typed.
    Read the setup guide
  • Linear

    Linear

    Escalations land as issues with evidence attached.

    Reads
    Team and project metadata for filing.
    Writes
    Linear issues with cause, confidence, and the evidence bundle.
  • MCP

    MCP

    Pull investigations into Cursor or Claude Code.

    Reads
    Investigations, connections, and setup state over MCP.
    Writes
    Connection and configuration changes your agent requests.
    Read the setup guide

What we do not connect

Hinto is Slack-first today. There is no inbound email channel and no sync with other helpdesk or observability tools.

Start free trial