Notion

Introduction

The Notion integration lets AskElephant search and work with your Notion pages, databases, and page content. You can ask about Notion in Chat, and you can read from or write to Notion inside a workflow.

Notion uses two separate connections, and which one you need depends on where you want to use it. This article covers both, what the integration can and cannot do, and what to check when something is not working.

Key Terms

Integration: A connection between two tools that lets them share information and work together.

OAuth: A secure way for AskElephant to access your Notion account without storing your password.

Workspace connection: A Notion connection made by an Owner that applies to your whole AskElephant workspace. Powers workflows only.

Personal connection: A Notion connection you make yourself that applies only to your own AskElephant account. Powers Chat only.

Notion Agent: A workflow action that takes a plain-language instruction and decides which Notion operations to run.

Connecting Notion

Set up the connection that matches where you want to use Notion, or set up both.

⚠️ Important. These two connections are separate. A personal connection does not make Notion actions available in workflows, and a workspace connection does not enable Notion in Chat. If your team needs both, make both connections.

Connect for Workflows

This requires the workspace Owner role. Managers and Users cannot open Workspace Settings, so they cannot connect, reconnect, or disconnect Notion for the workspace. See Roles & Permissions.

Go to Workspace Settings → Integrations
Find Notion in the integrations list
Click Connect
Approve the connection in the Notion authorization window

Connect for Chat

Anyone can make a personal connection, whatever their role. It applies only to your own AskElephant account.

Go to Personal Settings → Integrations
Find Notion in the integrations list
Click Connect
Approve the connection in the Notion authorization window

In the Notion authorization window, pick the Notion workspace you want to connect, then select the pages AskElephant may access.

AskElephant can only reach the pages you select here. Anything you leave out stays invisible to it, including pages nested under a parent you did not share. If a page you need is missing later, reconnect Notion and grant access to that page.

What AskElephant Can and Cannot Do

AskElephant can:

Find pages and databases by title, content, or properties
Read and summarize a page
Query a database with filters and sorting
Create pages, database entries, databases, comments, and page content
Update page titles, properties, database settings, and content blocks
Append, remove, or archive content blocks, duplicate pages, and look up Notion workspace users

AskElephant cannot:

Delete pages, or groups of pages. It can only remove or archive content blocks.
Reach pages you did not share during authorization
Edit content that your own Notion role can only view. Your Notion permissions still apply.
Continuously sync content between Notion and AskElephant
Start a workflow from a Notion event. There are no Notion triggers. Notion actions run only when a workflow reaches the Notion step.

Using Notion in Chat

Open Chat, select the Tools control, and enable Notion. You can then ask AskElephant to find, read, query, create, or update Notion content in plain language.

Be specific about the page or database name and the change you want. For example:

Find the Customer Feedback database and add an entry using this meeting summary.

If more than one result matches, AskElephant may ask you to choose.

Using Notion in Workflows

Once an Owner has connected Notion for the workspace, open a workflow in the Automations tab and add a Notion action. You have two approaches.

Notion Agent

Give a plain-language instruction and let the agent work out the steps. This suits multi-step or flexible tasks. Include meeting, company, person, or earlier-step variables when the task depends on that context.

Specific Notion Actions

Choose a defined operation with structured fields when you need predictable inputs, such as a page ID, a database ID, a property value, or block content.

Available actions are loaded for your workspace and may change over time. The list can take a moment to appear the first time you open it. Use the action's Outputs tab to pass page IDs, URLs, and other results to later steps.

Best Practices

Name the target. Say which page or database you mean rather than describing it. Exact names avoid the wrong match.

Confirm before broad updates. Check page names and destination databases in your prompt before asking for a change that touches many records.

Share only what is needed. Grant access to the pages AskElephant actually has to work with rather than a whole workspace.

Disconnecting

Disconnecting the workspace connection is an Owner action and affects everyone: workflows using Notion will stop working. Disconnecting your personal connection only affects your own Chat.

In both cases, disconnecting removes future access. It does not delete content AskElephant already created in Notion.

Troubleshooting

Nearly everything that goes wrong with Notion traces back to one of two things: which of the two connections you made, or which pages you shared during authorization. Open the symptom that matches what you are seeing.

The authorization window never opened.

This is nearly always your browser's pop-up blocker rather than anything wrong with your account. Allow pop-ups for AskElephant, then select Connect again. If you run an ad blocker or a privacy extension, try pausing it for this one step.

Notion actions are missing from a workflow.

The usual cause is that a personal connection was made where a workspace one was needed. The two are not interchangeable, and only an Owner can make the workspace connection. Confirm that connection is active, then refresh the workflow editor. One thing worth knowing before you conclude anything is broken: the action list is loaded for your workspace and can take a moment to appear the first time you open it.

Chat shows Notion as disconnected.

This is the same mix-up in the opposite direction. A workspace connection does not cover Chat. Connect the personal integration in Personal Settings → Integrations. Holding both connections at once is normal, and one does not replace the other.

A page cannot be found, or access is denied.

AskElephant can only reach the pages you selected during authorization, so a page it cannot find was almost certainly never shared with it. The case that catches people out is nesting: a child page is not visible just because you shared something above it. Reconnect Notion and grant access to that specific page. Reconnecting does not disturb anything already created.

An edit is refused.

This is a Notion permission rather than an AskElephant one, so your AskElephant Owner cannot resolve it. AskElephant acts as the Notion user who made the connection, and it cannot edit a page that user can only view. Check your own access to the page in Notion.

A write timed out.

Look in Notion before you retry. A timeout often means the response was slow rather than that the write failed, so the change may already be sitting there. Retrying without checking is how duplicates happen.

AskElephant shows Reconnect.

Connections do not last forever, and they also drop when your Notion access changes. Select Reconnect and approve again. This is routine rather than a sign that something has broken.

You see Notion (New) in the integrations list.

Follow its on-screen description. That option may connect successfully while AI tools are still unavailable for the connection, which looks like a failed connection but is not. Use the standard Notion connection for Chat and workflows until the new option says otherwise.

Still stuck? Reach out using the options below. It helps to say which connection you made, workspace or personal, and which page or database you were trying to reach.

Need More Help?

Reach the AskElephant support team by:

clicking the Support tab on the right side of your screen,
emailing [email protected],
or using @askelephant support in your dedicated Slack channel.