HOME / PRODUCTS / UPCOMING INTEGRATIONS
Upcoming integrations
None of them is built yet. This is what we intend to build and what each one will bring onto the account record, published so you can tell us which matters and so you are not guessing at our roadmap. There are no dates here, because we do not have honest ones. What ValueRamp connects to today is a much shorter list, and it is on the platform page.
29 integrations across 5 areas. The ones customers ask for get built first — if something here decides it for you, say so on a demo and it moves up.
Conversations
Where the customer actually talks to you. Slack and Teams already read inbound; this is the other half.
| Integration | What it will give you | Direction |
|---|---|---|
| Microsoft Teams | Post back into the channel — a nudge, a plan update, a reply Vali drafted | Outbound |
| Slack | Post back into the shared channel — a nudge, a plan update, a reply Vali drafted | Outbound |
| Gmail | Connect the mailbox directly instead of forwarding to it | Two-way |
| Microsoft Outlook | The same direct connection for Microsoft 365 mail | Two-way |
Support desks
A ticket is the earliest honest signal that an account is in trouble — and today it sits in a tool the CSM never opens.
| Integration | What it will give you | Direction |
|---|---|---|
| Zendesk | Ticket volume, age and sentiment against the account, not just the requester | Inbound |
| Freshdesk | The same account-level ticket signal from Freshworks | Inbound |
| Intercom | Conversations and ticket state on the account timeline | Inbound |
| ClearFeed | Slack-first support requests, already scoped to the customer channel they came from | Inbound |
| Front | Shared-inbox conversations attached to the account | Inbound |
| Help Scout | Conversations and happiness ratings against the account | Inbound |
| Jira Service Management | Escalations, and whether engineering has actually picked one up | Inbound |
| Linear | The bug a renewal is waiting on, and its real status | Inbound |
Meetings and transcripts
Fathom is live. These are the other places a customer conversation gets recorded — the notetaker your team already pays for is the one worth connecting.
| Integration | What it will give you | Direction |
|---|---|---|
| Fireflies | Transcripts and summaries attached to the account they belong to | Inbound |
| Gong | Call recordings, and the account they were actually about | Inbound |
| Otter.ai | Transcripts against the account, for teams standardised on Otter | Inbound |
| Zoom | Cloud recordings and their transcripts | Inbound |
| Google Meet | Meet recordings and transcripts, without a separate notetaker | Inbound |
| Google Drive | Where Meet transcripts land — read them from Drive directly | Inbound |
| Microsoft Teams recordings | Teams does expose transcripts after a call — it needs your Microsoft admin to switch that access on | Inbound |
Product usage data
Adoption scoring is only as good as what it reads. These are the places product usage already lives.
| Integration | What it will give you | Direction |
|---|---|---|
| Snowflake | Query the warehouse where product events are already modelled | Read-only |
| Google BigQuery | The same, for teams on BigQuery | Read-only |
| Databricks | The same, for teams on a lakehouse | Read-only |
| Segment | Take the event stream you already emit, without building a new pipeline | Inbound |
| Amplitude | Feature adoption per account, from the tool your product team already uses | Read-only |
| Mixpanel | The same per-account feature adoption, from Mixpanel | Read-only |
Build your own
For everything not on this page, and for the integration only you need.
| Integration | What it will give you | Direction |
|---|---|---|
| Zapier | Connect ValueRamp to whatever your team already automates | Two-way |
| Make | The same, for teams on Make | Two-way |
| n8n | The same, self-hosted | Two-way |
| ValueRamp API | A documented REST API and webhooks, so you are never blocked on our roadmap | Two-way |
Every product named on this page is a trademark of its owner. They are named because we intend to connect to them; none of them endorses ValueRamp, and a name here is not a partnership. Where a logo is missing it is because we do not have that vendor’s permission to reproduce it — not because the integration is any less planned.