Skip to content
Integrations

Your stack, read together.

Connect PostHog, Amplitude, Intercom, Sentry, your call transcripts and more. Then send a theme on to your tracker.

Connect your first source See what goes in and what comes out
  • PostHog
  • Amplitude
  • Intercom
  • Call transcripts
  • Zendesk
  • Gong
  • Typeform
  • App Store reviews
  • Google Analytics
  • Sentry
  • Datadog
  • CloudWatch
  • Azure Application Insights
  • Firebase Crashlytics

Each tool keeps its own copy of the story. None of them has the whole of it.

The funnel is in one tab, the complaint in another, the error in a third. Someone has to carry them into the same room.

What goes in. What comes out.

Each source connects in a few clicks. adduce reads them together. Everything on the right cites the rows it came from.

PostHog, Amplitude, Google Analytics, Intercom, Zendesk, Gong, Call transcripts, Sentry, and Datadog connect to adduce. Out come evidence records with their sources, a finding graded by how sure it is, a brief your team reviews, an issue in Linear, Jira or GitHub Issues with its evidence in the body, and an outbound webhook to your own system.

Sources are read-only. Nothing leaves adduce unless you send it.

Every integration, by name.

What adduce reads from each source, and where a theme can go.

Product signal · reads

  • PostHogSurveys, funnels, retention
  • AmplitudeEvents, cohorts, session replays
  • IntercomClosed support conversations
  • ZendeskSolved tickets and their threads
  • GongRecorded calls, as transcripts
  • TypeformFree-text form answers
  • App Store reviewsWritten reviews, per country
  • Google AnalyticsGA4 acquisition reports
  • Call transcriptsUploaded interviews and calls

Observability · reads

  • SentryError issues, by users affected
  • DatadogMonitors and error logs
  • CloudWatchFiring alarms and log patterns
  • Azure Application InsightsFired alerts and exceptions
  • Firebase CrashlyticsCrash groups, trailing 30 days

Issue trackers and automation · writes, only when you send it

  • LinearA theme as an issue, evidence in the body
  • JiraA theme as an issue, evidence in the body
  • GitHub IssuesA theme as an issue, evidence in the body
  • Outbound webhooksSigned POSTs to an endpoint you add

Every record keeps its source.

Each keeps its source context, so every citation points back to the record it came from.

By source

PostHog1
Intercom1
Zendesk1
Sentry1

  • Nothing loses its source.

    Every record carries a link back to the row, the message or the event it came from. Open it from anywhere.

  • Different tools, one view.

    A number, a quote and an error read as one body of evidence, not four exports.

  • Gaps show.

    When a source is thin or missing, the finding says so instead of guessing.

What each connector reads

Reads only. Shows what it read.

Connecting a source changes nothing in it. The sync history on each source is the record of what adduce read.

  • Read-only, always.

    Sources are read. Nothing is written back to them.

  • Nothing leaves unless you send it.

    No theme reaches your tracker and no data reaches anyone until you choose to send it.

  • The history is the proof.

    Every run lists what it read and what it added. The first sync shows you exactly what adduce read.

Connect one source and read the first finding.

Dashboards show you numbers and leave the argument to you. adduce does the arguing, and shows its work.

Connect your first source See pricing