Skip to main content

Connect Planhat to Perplexity

Give Perplexity governed access to Planhat’s 10 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Planhat to Perplexity in four steps

Admins approve the server once. Everyone in Perplexity then gets it through the same governed connection.

  1. 1

    Add Planhat to Runlayer

    Planhat isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Perplexity to Runlayer

    Users add the Runlayer Plugin to Perplexity by following Runlayer’s setup guide. Perplexity reaches Planhat’s 10 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Perplexity setup guide
  3. 3

    Sign in to Planhat

    Sign in the way Planhat requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Planhat from Perplexity

    Planhat’s approved tools appear in Perplexity. Every call is checked against policy and recorded.

Tools

10 Planhat tools in Perplexity

Runlayer policy decides which of these Perplexity users can call.

  • Create document

    Create a new document (page) in Planhat.

  • Create model record

    MODEL: "Company", PARAMETERS: {"name": "Acme Corp", "domain": "acme.com"}

  • Delete model record

    Delete existing record.

  • Get document

    Retrieve a document (page) by its ID, including its full content.

  • Get model action parameters

    Returns field metadata (names, types, required flags) for a data model.

  • Get model record

    Get single record by ID.

  • List model records

    MODEL: "Company", LIMIT: 20

  • Search documents

    Search documents (pages) by text.

See all 10 Planhat tools

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 Planhat 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

Find another combination