Pipedrive, without opening Pipedrive.
Deals moving down the pipeline, and what moved them.
- Free to start
- No card
- Every write waits for you
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Pipedrive details, and Ray takes it from there.
@Ray which deals slipped a stage this week and who owns them?
@Ray add a note to the Northwind deal with what we agreed on the call.
@Ray create a follow-up activity on every deal that has gone quiet for two weeks.
@Ray what is in the pipeline for this quarter, by stage?
What Ray can and cannot do in Pipedrive
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
195 reads wired, 119 actions that wait for a human.
Runs on its own
What Ray reads in Pipedrive
- Deals with their stages, values, and the pipeline they sit in
- Persons, organizations, leads, and the notes against them
- Activities, calls, and what is due this week
- Products, quotes, goals, and the reporting behind them
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Create or update a deal, and move it to another stage
- Add or update a person, an organization, or a lead
- Schedule an activity, and mark one done
- Add a note to a deal, person, or organization
- Create products, pipelines, stages, and filters
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
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.
- Read or change roles and permission sets
- Download the contents of an attachment
- Read back access tokens
- Delete a deal, person, organization, or anything in bulk
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Pipedrive actions Ray can take, each one stopping in the thread with the real content before it happens.
- Pipedrive: add activity type
- Pipedrive: add an activity
- Pipedrive: add an organization
- Pipedrive: add a deal
- Pipedrive: add a person
- Pipedrive: add call log
- Pipedrive: add call log audio file
- Pipedrive: add channel
- Pipedrive: add dealfields options
- Pipedrive: add deal discount
Pipedrive: add activity type
Showing Name and Icon key, each carrying the exact content that will land.
How Ray works with Pipedrive
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Pipedrive
Pipedrive 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
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Pipedrive, and tell Dana it is being looked at.
Pipedrive: add activity type
- Waiting on
- your approval
Ray uses Pipedrive together with the rest of your tools.
One ask can read Pipedrive, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Pipedrive to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Pipedrive and it can do the Pipedrive 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.
Pipedrive 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 Pipedrive. Every write still stops for approval first.
Security and permissions
- You paste the Pipedrive 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 Pipedrive in a message. Uninstall Ray and every connection it held is revoked.
Pipedrive and Ray, answered
The questions teams ask before they connect Pipedrive. Every answer is how this integration is built rather than a promise about it.
More crm & sales integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Pipedrive.
Free to start, no credit card, and it asks before it acts.
By adding Ray, you accept the Terms and Privacy Policy.