Connect Postman to Perplexity
Give Perplexity governed access to Postman’s 41 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Postman to Perplexity in four steps
Admins approve the server once. Everyone in Perplexity then gets it through the same governed connection.
- 1
Approve Postman in Runlayer
Add Postman from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect Perplexity to Runlayer
Users add the Runlayer Plugin to Perplexity by following Runlayer’s setup guide. Perplexity reaches Postman’s 41 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Perplexity setup guide - 3
Sign in to Postman
Sign in the way Postman requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Postman from Perplexity
Postman’s approved tools appear in Perplexity. Every call is checked against policy and recorded.
Tools
41 Postman tools in Perplexity
Runlayer policy decides which of these Perplexity users can call.
Create collection
Creates a collection using the [Postman Collection v2.1.0 schema format](https://schema.postman.com/collection/json/v2.1.0/draft-07/docs/index.html).
Create collection request
Creates a request in a collection.
Create collection response
Creates a request response in a collection.
Create environment
Creates an environment.
Create mock
Creates a mock server in a collection.
Create spec
Creates an API specification in Postman's [Spec Hub](https://learning.postman.com/docs/design-apis/specifications/overview/).
Create spec file
Creates a file for an OpenAPI or a protobuf 2 or 3 specification.
Create workspace
Creates a new [workspace](https://learning.postman.com/docs/collaborating-in-postman/using-workspaces/creating-workspaces/).
Control
What Runlayer can see and stop in Perplexity
Some controls apply to every client at the gateway. Others depend on what Perplexity exposes to Runlayer.
Gateway policy (available)
Every Postman call from Perplexity passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Perplexity as the client, the tool, and the policy and scanner decisions.
Managed browser extension (available)
Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.
Native enforcement adapter (not available)
Runlayer has no device-side adapter for Perplexity yet, so control happens at the gateway.
Frequently asked questions
Connect more