Connectors

100+ connectors. One spine. Always included.

Everything you already run, joined onto one record per customer — revenue, code, errors, feedback, behaviour, spend. Connectors are always included — no per-connector fee: you pay for modules, not for plugging in your own stack.

Watch: connect Stripe — revenue lands on the customer record · Example data

Watch: connect Stripe — revenue lands on the customer record · Example data from the Brightline demo workspace

How it works

Connect once. The 360 fills itself in.

Plug in your stack and the joins are already written underneath. Click through what happens.

Connect

Plug in your stack

  • Stripe, GitHub, Linear, Jira, Slack and dozens more
  • Connect in minutes and see the join on real data

Sync

It keeps itself current

  • Analytics and monitoring sync hourly; the rest daily
  • Resync any connection on demand

Health

You can see it working

  • Connected, error and stale health chips
  • Click a state to filter, or sync now per tile

The 360

Each panel switches on

  • The joins are written underneath, ready
  • A 360 panel lights up as its connector ships

Connectors included, no per-connector fee.

The full catalog

All 116 connectors, 18 categories

Every source that lands on the spine — free to connect during early access.

Identity & Auth

Who your users are — registered accounts from your auth provider land as People → End-users, and a work-domain email mints the parent Account. No SDK identify() required.

  • Clerk

    Registered users → End-users. Instance Secret Key; a work-domain email also lands the Account.

  • WorkOS

    Enterprise users from WorkOS User Management → End-users, deduped with your SDK identities.

  • Auth0

    Auth0 tenant users → End-users via a read-only Management API (M2M) app.

  • AWS Cognito

    A Cognito user pool → End-users. IAM access key + region + pool id, signed server-side.

Payments & Billing

What you earn — paying accounts, MRR, churn.

  • Stripe

    Subscriptions, invoices, MRR — the revenue node of the spine.

  • RevenueCat

    Mobile subscriptions across App Store and Google Play in one feed.

  • Paddle

    Merchant-of-Record billing — VAT and subscriptions handled for you.

  • Lemon Squeezy

    MoR billing for SaaS and digital products.

  • Chargebee

    Subscription billing for mid-market and complex pricing.

  • Recurly

    Recurring billing with deep retention and dunning tooling.

  • Braintree

    PayPal-owned card processing for enterprise checkout.

  • Square

    POS and online payments under one account.

  • Adyen

    Enterprise payments across cards, wallets, and regions.

  • GoCardless

    Direct-debit collection for EU and UK subscriptions.

Code & Infrastructure

Your architecture — repos, deploys, edge.

  • GitHub

    Repos, PRs, issues — the engineering source of truth.

  • GitLab

    Projects, MRs, pipelines — gitlab.com or self-managed.

  • Bitbucket

    Atlassian-hosted Git — repos onto the spine via App Password.

  • Vercel

    Frontend hosting + deploys; pulls projects, branches, builds.

  • Netlify

    Frontend hosting; pulls sites and deploys.

  • Cloudflare

    DNS, Workers, Pages — edge and infra.

  • CircleCI

    CI/CD pipeline runs land on the spine as deployments — build/test/deploy status joined to the release.

  • Jenkins

    Self-hosted CI — Jenkins builds land as deployments on the spine (base URL + API token).

Datastores & Databases

Where your product's data actually lives — Postgres, MySQL, Mongo, key-value, vector. Schema + access posture on the spine, not customer rows.

  • Supabase

    Postgres, Auth, Storage — schema and access posture.

  • Firebase

    Realtime DB, Auth, Cloud Functions — Google's BaaS.

  • PostgreSQL (any host)

    Direct Postgres via connection string — RDS, self-hosted, Render, Railway, Fly. Format-only validation; credentials secured.

  • Neon

    Serverless Postgres with branching. Live API ping — counts your projects.

  • Vercel Postgres

    Vercel-managed Postgres (powered by Neon). Live API ping via Vercel access token.

  • CockroachDB Cloud

    Distributed Postgres-compatible — multi-region by default. Live API ping lists clusters.

  • MySQL (any host)

    Direct MySQL/MariaDB via connection string. Format-only validation; credentials secured.

  • PlanetScale

    Serverless MySQL with Vitess branching. Live API ping with Service token.

  • MongoDB Atlas

    Document database — Atlas-managed clusters. Public+private API key pair, validated live against the Atlas Admin API (digest auth); counts your projects.

  • DynamoDB

    AWS key-value / document store. Access key + secret + region, validated live via a SigV4-signed ListTables; counts your tables.

  • Convex

    Reactive backend-as-service — deployment URL + admin key. Live version-endpoint ping.

  • Upstash Redis

    Serverless Redis — cache, queue, rate-limit. Live REST API lists your databases.

  • Redis Cloud

    Managed Redis (Redis Inc.). Account key + secret key; live API lists subscriptions.

  • Pinecone

    Vector database for embeddings / RAG. Live API counts your indexes.

  • Weaviate

    Open-source vector database (cloud or self-hosted). Cluster URL + API key; readiness endpoint ping.

  • Qdrant

    Open-source vector database with hybrid search. Cluster URL + API key; live collections list.

Cloud & AI Cost

What you spend — cloud bills, AI usage, storage.

  • AWS Cost Explorer

    AWS spend by service and tag.

  • Google Cloud Billing

    GCP spend by service, pulled from your BigQuery billing export.

  • Azure Cost Management

    Azure spend by resource group.

  • Anthropic

    Claude API usage and spend per model.

  • OpenAI

    OpenAI API usage and spend per model.

  • OpenRouter

    Multi-model AI gateway usage.

Product Analytics

Behaviour — events, sessions, retention.

  • PostHog

    Self-host or cloud — events, sessions, flags.

  • Amplitude

    Product analytics for retention and funnels.

  • Mixpanel

    Event tracking and cohort analysis.

  • Google Analytics 4

    Website behaviour and audiences.

  • Segment

    Customer data pipeline — fan-in events from many sources.

  • Heap

    Register Heap as a known analytics source for this product (metadata-only — events flow through your existing Heap pipeline).

Customer Conversation

Voice of customer — tickets, chat, calls.

  • Intercom

    Chat, tickets, conversations from customers.

  • Zendesk

    Support tickets and macros.

  • Help Scout

    Lightweight ticketing and shared inbox.

  • Slack

    Pull product-relevant threads (feedback, incidents) onto the spine as signal — not a replacement for company Slack.

  • Front

    Shared-inbox conversations land as insights on the spine, joined to the customer who wrote in.

  • Freshdesk

    Freshworks support tickets land as insights, joined to the requester — 360 without leaving ProductOS.

  • Gladly

    Customer-centric support — Gladly conversations land as insights, welded to the customer profile.

  • Aircall

    Aircall call logs land as insights on the spine, joined to the contact who called.

  • Kustomer

    Kustomer conversations land as insights, welded to the customer profile via the JSON:API include.

  • Gorgias

    Gorgias tickets land as insights on the spine, joined to the requester (subdomain SSRF-guarded).

  • Dixa

    Dixa conversations land as insights on the spine, joined to the customer who wrote in.

Design

Where the team designs — files land on the spine as design work items, linkable to features and tasks.

  • Figma

    Pick a team and the projects whose files belong to this product — every file lands as a 'design' work item on the spine.

Feedback & Discovery

Where the voice of customer lives today — migrate the corpus to the spine in one move so insights join revenue, code, and work.

  • Productboard

    Pick which Productboard products feed this one — notes from the trailing 90 days land as insights on the spine, in one move.

  • Canny

    Posts, votes, and boards land as insights on the spine — the public feedback portal becomes one source feeding the Insights feed.

  • Notion

    Pick which Notion databases feed this product — PRDs, specs, and discovery notes land as insights on the spine.

  • Featurebase

    Posts and upvotes from your Featurebase board land as insights on the spine — Canny-shape parity for teams on Featurebase instead.

  • Trustpilot

    Public reviews land as insights on the spine — honest, star-rated customer sentiment about your product, joined to features and accounts (bad reviews float into triage).

Monitoring & errors

The #1 dev signal — errors and incidents land as work items on the spine, per-product issue feed.

  • PagerDuty

    Incidents → work items on the spine — operational health and MTTR, joined to the deploy or feature that paged on-call. Pick which services feed this product; a read-only API key is enough.

  • Freshservice

    Freshservice ITSM tickets → work items on the spine — internal operations joined to features and releases (subdomain SSRF-guarded).

  • Datadog

    Monitors + incidents → work items on the spine — operational health joined to the deploy that broke.

  • New Relic

    Alert issues → work items on the spine, joined to features and deploys.

  • Bugsnag

    Errors → work items on the spine; per-project error feed joined to releases.

  • Rollbar

    Active items → work items on the spine — errors joined to the deploy that shipped them.

  • Opsgenie

    Alerts → work items on the spine — on-call signal joined to the deploy or feature that paged.

  • incident.io

    Incidents → work items on the spine — MTTR and status joined to the release that caused them.

  • Grafana

    Alert rules + firing alerts → work items on the spine (self-hosted or Grafana Cloud).

Flags & Experiments

Mirror your flag platform onto the spine — visibility, not eval. Native /api/flags/eval stays the source of truth for production traffic.

  • LaunchDarkly

    Mirror LD projects' flags onto the spine as work items — see what's live without leaving ProductOS. Eval traffic stays on LD.

  • Statsig

    Mirror Statsig feature gates onto the spine — visibility for the team without touching the eval path.

  • Split

    Mirror Split (Harness FME) feature flags onto the spine as work items — visibility, not eval.

  • Amplitude Experiment

    Mirror Amplitude Experiment flags + experiments onto the spine as work items.

Mobile app stores

Ratings, reviews, and store signal — the only feedback channel where your mobile users actually leave a voice. Lands as insights on the spine.

  • App Store Connect

    iOS customer reviews land as insights, with star rating + territory in the title. Mints a 10-min JWT per request; .p8 + Issuer ID + Key ID needed.

  • Google Play Console

    Android user reviews land as insights — reviews from the trailing 7 days per Google's API window, refreshed on every sync.

Research & Surveys

Customer research and structured surveys → insights on the spine, joined to features and accounts.

  • Typeform

    Survey responses land as insights on the spine — discovery research, NPS, exit interviews all in one feed.

  • Dovetail

    Research notes and project transcripts land as insights — qualitative research joins the unified Feed.

  • Delighted

    NPS + CSAT responses land as insights on the spine, joined to the respondent — the score is in the title.

  • Sprig

    Sprig study responses land as insights on the spine — product-research signal joined to the respondent when an email is captured.

  • Maze

    Maze usability-test results land as insights on the spine — product-research signal joined to the respondent when captured.

  • SurveyMonkey

    SurveyMonkey survey responses land as insights on the spine, joined to the respondent when the email is collected.

Async stack & automation

Background jobs, async video, community channels, and the universal-glue layer — all the things that fire outside business hours but should be visible on the spine.

  • Inngest

    Background-job events land as tasks on the spine — the firehose of what your async workloads are doing, joined to features and customers.

  • Loom

    Paste Loom share URLs and each lands as an insight on the spine, joinable to features. Uses Loom's public oEmbed — no token, works for any shared Loom.

  • Discord

    Product-discussion channels → conversation signal on the spine. Bot token + server id; channels are picked per product. Not a full Slack replacement — focused signal capture.

  • Zapier

    Outbound HMAC-signed webhooks — Zapier's Catch Hook trigger (and Make, n8n, custom backends) consumes them natively. Subscribe to spine events; we fire on every match.

  • Inbound webhooks

    A per-org receiver URL any tool (or Zapier / Make / n8n) can POST JSON to — mapped onto spine events. The long-tail catch-all, no bespoke connector needed.

Work & Issues

Existing trackers — import work onto the spine; coexist now, migrate to native PM when ready.

  • Linear

    Import Linear issues onto the spine so work joins revenue, code, and customers — coexist with native PM, migrate when ready.

  • Jira

    Import Jira issues onto the spine for teams not ready to leave Atlassian — the cross-spine join works on day one, no migration required.

  • Asana

    Import Asana tasks (per project) onto the spine — work joins revenue, code, and customers.

  • ClickUp

    Import ClickUp tasks (spaces → lists) onto the spine as work items.

  • monday.com

    Import monday.com board items onto the spine as work items — pick the boards that feed this product.

  • Shortcut

    Import Shortcut stories onto the spine — engineering work joins the cross-spine view.

  • Aha!

    Import Aha! features (per product) onto the spine as work items, joined to releases and customers.

  • Height

    Import Height tasks (per list) onto the spine — work joins the cross-spine view.

  • Wrike

    Import Wrike tasks (per folder/project) onto the spine — auto-routes US or EU datacenter.

Customer Success & Calls

Revenue-intelligence calls and CS-health signals land as insights on the spine — joined to the account and the customer who spoke.

  • Gong

    Call summaries land as insights, welded to the external participant — revenue intelligence on the spine.

  • Chorus

    ZoomInfo Chorus call signal lands as insights, joined to the customer on the call.

  • Gainsight

    CTAs + scorecard-health changes land as insights on the spine, joined to the account.

  • Vitally

    Account-health changes, conversations, and notes land as insights on the spine.

Data Pipelines

ELT/transform health on the spine — dbt runs, Fivetran + Airbyte syncs land as work items, joined to features and deploys.

  • dbt Cloud

    dbt Cloud job runs land as work items on the spine — model freshness + run status without leaving ProductOS.

  • Fivetran

    Fivetran connector sync status lands as work items on the spine — ELT health joined to the product.

  • Airbyte

    Airbyte sync jobs land as work items on the spine — pipeline runs joined to features.

Lifecycle & Audience

Email + lifecycle audiences land as People → End-users on the spine, deduped by email into the same person across sources — no SDK identify() required.

  • Klaviyo

    Klaviyo profiles → End-users on the spine, deduped by email.

  • Customer.io

    Customer.io people → End-users on the spine (US/EU region-aware).

  • Mailchimp

    Mailchimp audience members → End-users on the spine (datacenter auto-derived from key).

  • Iterable

    Iterable users → End-users on the spine (US/EU region-aware).

  • ActiveCampaign

    ActiveCampaign contacts → End-users on the spine (account API URL SSRF-guarded).

  • Braze

    Braze users from a chosen segment → End-users on the spine (US + EU REST endpoints, segment_id required).

  • Marketo

    Marketo leads from a chosen static list → End-users on the spine (Munchkin-URL SSRF-guarded, OAuth2 client-creds).

Don't see your tool?

Zapier catches the long tail today — and the catalog grows weekly. Tell us what you run and we'll wire it.

See it on your stack Get a walkthrough

← Everything in the OS

FAQ

Questions, answered

How many integrations are there, and what kinds?
116 live connectors across 18 categories — payments, code hosts, deploys, datastores, analytics, support, feedback, error tracking, feature flags and the app stores among them.

What does a connector actually bring in?
It syncs the external data onto your customer spine — payments, tickets, feedback, errors and more — linked to the matching account and product records, so it's usable across every module rather than stranded in one tool.

What does it cost to connect my stack?
Connectors are included on every plan, flat by tier (from $199/mo) — so connecting more of your stack never adds a per-connector or per-seat charge, ever.

What if my tool isn't in the catalog?
The connector catalog grows regularly, and Zapier bridges the long tail of tools that aren't natively listed yet. Tell us what you run and we'll wire it.