Skip to main content

Connect Notion to ECA

Give ECA governed access to Notion’s 48 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Notion to ECA in four steps

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

  1. 1

    Approve Notion in Runlayer

    Add Notion from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect ECA to Runlayer

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

    ECA setup guide
  3. 3

    Sign in to Notion

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

  4. 4

    Use Notion from ECA

    Notion’s approved tools appear in ECA. Every call is checked against policy and recorded.

Tools

48 Notion tools in ECA

Runlayer policy decides which of these ECA users can call. 5 read data only and 1 can change or delete data.

  • AI search

    Notion ai search.

  • Check MCP next steps

    Finish all Notion tool calls needed for the current request, then call at most once with no arguments.

  • Convert page to skill

    Mark an existing Notion page as a skill without changing its content.

  • Create attachment

    Create an attachment and upload it to Notion.

  • Create comment

    Add a comment to a page or specific content.

  • Create database

    Creates a new Notion database using SQL DDL syntax, or a canonical typed database for tasks, projects, or skills.

  • Create file upload

    Create a short-lived URL for uploading one local file directly to Notion.

  • Create folder

    Creates an empty Notion Folder.

See all 48 Notion tools

Control

What Runlayer can see and stop in ECA

Some controls apply to every client at the gateway. Others depend on what ECA exposes to Runlayer.

  • Gateway policy (available)

    Every Notion call from ECA passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, ECA as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for ECA yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination