Integrations

More growth from the tools you already use.

The clues to missed revenue are spread across your systems. Refix connects the evidence, so an investigation can follow the opportunity wherever it leads.

  • Metabase
  • Amplitude
  • Redshift
  • BigQuery
  • Google Sheets
  • Stripe
  • Shopify
  • Tableau
  • Jira
  • PostHog
  • Mixpanel
  • Postgres
  • Snowflake
  • Salesforce
  • Slack
  • Power BI
  • Linear
  • Supabase
  • Google Analytics
  • ClickHouse
  • Databricks
  • Google Ads
  • HubSpot
  • Meta Ads
  • Looker
  • Zendesk

Used by teams at

Follow the evidence across your existing stack.

  • Investigate across your data

    Understand how product activity relates to revenue, using the analytics and databases your team already relies on.

  • Take the next step

    Turn a finding into work in a connected tool, with actions governed by your workspace's approval settings.

  • Bring in the business context

    Search Notion, Google Drive, and Confluence for the decisions behind the numbers, so the investigation starts with your team's context.

Connected evidence

Find the opportunity between your systems.

Interest in one tool can look healthy while revenue in another stays flat. Refix follows the relevant records across sources to investigate the gap, using read-only access for analysis.

  • BigQuery, Snowflake, Postgres, and other databases
  • PostHog, Mixpanel, Amplitude, and Google Analytics
  • Revenue context from Stripe, Salesforce, and HubSpot

From finding to work

Put the next step where your team can act on it.

A finding has more value when someone can take it forward. Refix can create a ticket in a connected tool and include the context behind the recommendation. You set the approvals it needs.

  • Tickets in connected tools such as Linear and Jira
  • A clear description of the proposed action
  • Approval controls set by your workspace

Security and control, built in.

Choose what Refix can access and set the approvals it needs. Review the data and reasoning behind its recommendations.

Read-only by design

Writes are refused at the database, not left to the model.

Approvals you control

Require your team's approval before Refix takes action in connected tools.

Roles for every teammate

Decide who connects data, approves actions, and manages billing.

Usage you can see

Daily credit use, with an alert before you reach your limit.

Zero data retention

Model providers keep nothing and never train on your data.

  • AICPA SOC 2 SOC 2 Type II*
  • ISO/IEC 27001 2022 ISO/IEC 27001*

* SOC 2 Type II audit under observation. ISO/IEC 27001 certification in progress.

Self-hosting

Connect your tools to Refix in your own cloud.

Run the Refix agent on your own Kubernetes cluster. Your platform team controls access and model connections, with our engineers helping you deploy.

  • Helm chart for your Kubernetes cluster
  • Your model keys or LLM gateway
  • Slack sign-in or your identity provider
  • Network access controlled by your firewall
  • Application updates you approve
  • Controls for reporting back to Refix

Questions about integrations.

Connecting your stack and choosing what Refix can do.

Talk to a human

Which tools does Refix connect to?

Connect warehouses and databases such as BigQuery, Snowflake, and Postgres, or analytics tools including PostHog, Mixpanel, Amplitude, and Google Analytics. Stripe and Salesforce add revenue context. Slack, Linear, Jira, and HubSpot bring the work into your team's tools.

Can Refix change data in our warehouse?

Refix uses read-only access for warehouse and database investigations. Give the connection read-only credentials scoped to the data you want it to use.

How do actions in other tools work?

Refix proposes or performs actions according to your workspace's approval settings. When approval is required, your team reviews the request before it runs.

Do we need to move our data into Refix?

No. Refix queries connected sources where they are. Your existing tools remain in place.

What happens after I connect a source?

Refix starts learning what the source contains and how to use it. That understanding supports your questions and ongoing investigations, including work that spans other connected tools.

Your next growth hire isn't a person.