Postman, without opening Postman.
The collections a team keeps, and what the monitors say about them.
“@Ray did the checkout monitor pass overnight?”
What Ray can and cannot do in Postman
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 Postman
- Collections, folders, requests, responses, and their forks
- APIs, versions, schemas, and specs
- Mock servers, monitors, and monitor run results
- Comments left on any of it, and who is on the team
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 collection, folder, request, or response
- Create an API, a schema, or a spec, and update its files
- Create a mock server or a monitor, and run one
- Comment on a collection, folder, request, or response
- Fork a collection, and open a pull request between forks
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 what is inside an environment, where your API keys and tokens live
- Read collection access keys
- Publish a mock server, or create a webhook
- See billing accounts or invoices
- Delete a collection, API, workspace, or anything else
How Ray works with Postman
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Postman
Postman 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 Postman, and tell Dana it is being looked at.
Postman: create an api
- Waiting on
- your approval
What does connecting Postman to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Postman and it can do the Postman 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.
Postman 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 Postman. Every write still stops for approval first.
Security and permissions
- You paste the Postman 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 Postman in a message. Uninstall Ray and every connection it held is revoked.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Postman.
Free to start, no credit card, and it asks before it acts.