LinkedIn, without opening LinkedIn.
Company page performance, and how big an ad audience actually is.
- Free to start
- No card
- Reads only, nothing to approve
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own LinkedIn details, and Ray takes it from there.
@Ray how big is the audience if we target platform engineers in Spain?
@Ray how did the company page do last month?
@Ray which of our posts got the most engagement this quarter?
@Ray can we target by job title as well as seniority?
What Ray can and cannot do in LinkedIn
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
11 reads wired, and nothing that writes.
Runs on its own
What Ray reads in LinkedIn
- Company page stats, follower counts, and post performance
- Ad targeting facets and the audience sizes behind them
- Your own profile and network size
Reading changes nothing, so Ray never stops to ask whether it may look something up.
No send, no spend
What Ray answers with
Ray reads LinkedIn and answers from it in the thread. Writing to LinkedIn 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.
- Post or share anything
- Comment on a post
- Delete a post
How Ray works with LinkedIn
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect LinkedIn
One click, right where you asked. Ray posts a connect card, you authorise LinkedIn with your own account, and the work you asked for picks up where it left off.
- 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 LinkedIn, so there is nothing here to approve. It looks up what it needs and replies in the thread.
Priya
@Ray the checkout bug is back. Take a look in LinkedIn, and tell Dana it is being looked at.
Ray
Checked LinkedIn. The spec was last edited on Tuesday and the open question about refunds is still unanswered.
Ray uses LinkedIn together with the rest of your tools.
One ask can read LinkedIn, 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 LinkedIn to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect LinkedIn and it can do the LinkedIn 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.
Every person on the team connects their own LinkedIn account, so Ray can only reach what that person can already reach, and the history in LinkedIn shows who actually asked.
Security and permissions
- You authorise LinkedIn on its own login screen. Your password never passes through Ray.
- 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.
- Disconnect LinkedIn in a message, or uninstall Ray and every connection it held is revoked.
LinkedIn and Ray, answered
The questions teams ask before they connect LinkedIn. Every answer is how this integration is built rather than a promise about it.
More marketing & ads integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in LinkedIn.
Free to start, no credit card, and it asks before it acts.