Amplitude, without opening Amplitude.

Funnels, retention and revenue, answered in the thread that asked.

Analytics & BI27 reads

Add to Slack for free Browse all integrations

In your channel

“@Ray what does our signup funnel look like this month?”

What Ray can and cannot do in Amplitude

Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.

Runs on its own

What Ray reads in Amplitude

Funnels, retention curves and event segmentation over any date range
Active users, sessions per user and average session length
Revenue and lifetime value: ARPU, ARPPU and the totals behind them
The event and user property taxonomy, cohorts, and one user's activity

Reading changes nothing, so Ray never stops to ask whether it may look something up.

Asks first, every time

What Ray answers with

Ray reads Amplitude and answers from it in the thread. Writing to Amplitude is not switched on yet, so there is nothing here to approve.

Not on the list

Things Ray is never handed

These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.

Send, upload or identify events, which would put invented data in your analytics
Create, rename or delete event types, categories, annotations or cohorts
Delete users, merge two user identities, or change who is in a cohort

How Ray works with Amplitude

No workflow to build, and nothing to maintain when the work changes.

01
Connect Amplitude
Amplitude has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
03
Ray answers where you asked
Ray only reads Amplitude, so there is nothing here to approve. It looks up what it needs and replies in the thread.

and the rest

Priya

@Ray the checkout bug is back. Take a look in Amplitude, and tell Dana it is being looked at.

Ray

Checked Amplitude. The spec was last edited on Tuesday and the open question about refunds is still unanswered.

What does connecting Amplitude to Ray actually do?

Ray is an AI teammate that works in your team chat, on Slack today. Connect Amplitude and it can do the Amplitude part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.

It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.

Amplitude has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Amplitude. Every write still stops for approval first.

Security and permissions

You paste the Amplitude key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
An admin, or whoever connected it, can disconnect Amplitude in a message. Uninstall Ray and every connection it held is revoked.

How Ray handles your data