Integrations
The Amplitude integrations that earn their keep (and how the catalog is organized)
Amplitude's directory lists 158 integrations at the time of writing. The useful skill isn't knowing all of them - it's knowing the six connection types they reduce to, and which three wires carry most of the value.
How is the catalog actually organized?
Ignore the logo wall; read the connection-type filter. Amplitude's own taxonomy splits the catalog into Sources, Destinations, Cohorts, Event Streaming, Raw Events, SDKs, User Properties, Group Properties, Merged User IDs, and Profile API - functionally: data flowing IN, data flowing OUT, and audiences flowing OUT. Every integration decision is one of those three sentences.
| Connection type | What it means | Ask before wiring it |
|---|---|---|
| Source | Events/users flow INTO Amplitude (CDPs, Braze Currents, server pipelines) | Does it respect your taxonomy, or dump its own event names into your project? |
| Destination / Event Streaming | Amplitude events and users flow OUT to other tools | Which events, exactly? Streaming everything is paying twice for noise. |
| Cohort sync | Behavioral audiences flow out to engagement/ad tools | One-time, scheduled, or real-time - match the sync mode to the campaign's clock. |
Taxonomy: amplitude.com/integrations (the catalog count drifts; the structure doesn't).
What does the Slack integration actually do?
More than notifications, per the docs: it unfurls chart and cohort links into detailed previews inside Slack, lets you add charts to dashboards without leaving the conversation, connects Team Spaces to specific channels with notifications when teammates publish analyses, carries tracking-plan change notifications from Amplitude Data, and routes chart alerts into channels. One documented gap: Pathfinder, Compass, and Persona charts don't unfurl.
Our field take (judgment): the unfurl is the sleeper feature. Charts that expand in-channel get discussed; links that don't get ignored - the integration is really an adoption tool wearing a notification costume.
Which integrations should a new instance wire first?
- Warehouse export (Snowflake/BigQuery/S3 destinations) - your recurring copy of event data where SQL and BI live; Snowflake syncs run on a documented ~10-minute cadence. This is also the reconciliation source your data team will demand.
- Your CDP or ingestion source, configured to your tracking plan - not its defaults. A source that renames your events has undone the taxonomy work on day one.
- Slack - cheapest adoption lever in the catalog (see above).
- Cohort syncs to your engagement stack - the point where analysis becomes action; see our Braze + Segment stack guide for the concrete wiring.
Ordering is our judgment; each integration's behavior above is documented at the linked sources.
Sources
- Amplitude integrations catalog (count + connection types)
- Amplitude docs: Integrate Slack
- Amplitude docs: Snowflake destination (recurring export)
Product capabilities change - every claim above links to the primary source it came from. Judgment calls and field observations are ours and labeled in-line.
Frequently asked questions
How many integrations does Amplitude have?+
Amplitude's own directory shows 158 results at the time of writing - a live count that drifts, so treat the number as a snapshot. More durable is the structure: every entry is a source (data in), a destination or stream (data out), or a cohort sync (audiences out).
Can Amplitude send alerts to Slack?+
Yes - chart alerts can go to one or more Slack channels, and the Slack app also unfurls chart/cohort links, posts Team Space activity to chosen channels, and carries tracking-plan change notifications. Documented exception: Pathfinder, Compass, and Persona charts don't unfurl.
Get a free, scored audit of your Amplitude instance
Send us read-only access and get a scored findings report within 48 hours: taxonomy health, duplicate events, governance gaps, and the three fixes with the highest data-trust payoff. No commitment.
Request the free audit