An AI agent that answers from your Notion
Notion works with Ara in two ways. Add it as a place to read, and Ara keeps your pages searchable, re-reads them on an hourly cycle and answers company questions from them, told to name the source and the date. Connect it as an app, and Ara can also create pages and work with database rows when asked. People ask from Slack, a linked messenger or the dashboard, so they don't have to be in Notion.
How it connects: Through Composio. Reading into knowledge runs in the background on the connected account. Live page and row work uses tools that you can switch on and off one by one.
What Ara does with Notion
Answer a company question from your pages
You say: What's our refund window for annual plans?
Ara searches what it has read and is told to cite where it found it and the date. If the pages don't say, it is told to answer that it could not verify it and where it looked, not to fill the gap with what companies usually do.
Tools it can use
- NOTION_FETCH_DATA
- NOTION_GET_PAGE_MARKDOWN
Turn a meeting into a page
You say: Here's the transcript. Write the decisions and action items, and put them in our meetings page.
Ara pulls out decisions and dated action items and creates the page. It is told not to invent an attendee or a commitment.
Tools it can use
- NOTION_SEARCH_NOTION_PAGE
- NOTION_CREATE_NOTION_PAGE
- NOTION_ADD_MULTIPLE_PAGE_CONTENT
Work with a database
You say: Add these leads to the Leads database, and tell me which already exist.
Ara queries the database at the time of the request, so it sees the current rows, then adds the new ones and reports the ones already there.
Tools it can use
- NOTION_QUERY_DATABASE
- NOTION_INSERT_ROW_DATABASE
- NOTION_UPSERT_ROW_DATABASE
Keep a status page current
You say: Every Friday, add this week's status to our project page.
A workspace admin says it once from a direct chat and it becomes a schedule. Each run adds a dated block to the page and reports back where it was made.
Tools it can use
- NOTION_APPEND_TEXT_BLOCKS
What a reply looks like
Request: What's our refund window for annual plans?
Reply: I couldn't verify that. Nothing in the company documents covers annual-plan refunds. The Notion source was last read on [date], and the closest page is [page]. [Person] would know, or you can add it and I'll answer from it.
Setup
- In the dashboard, open Your apps, search for Notion and press Connect. Sign-in happens on the app's own page.
- To have it answer from your pages, a workspace admin opens the list of places Ara reads and adds Notion. It starts reading right away and shows how many documents it holds.
- Give it a question whose answer you already know, and check the source it names.
Runs without asking
- Reading pages into knowledge and re-reading them. This runs in the background, and an app rule doesn't hold it.
- With no rule, NOTION_REPLACE_PAGE_CONTENT and NOTION_UPDATE_ROW_DATABASE overwrite as soon as Ara calls them. Both are in the delete class on the permissions screen, so they are the first to switch off.
What waits for a person
- Under "Never runs", it can still answer from the pages it has read, and changes nothing. Live database queries such as NOTION_QUERY_DATABASE are refused too, because a rule goes by the tool's name.
- Under "Asks a person first", those database queries wait for a person as well as the changes do.
Limits
- The background reader takes pages, at most 200 per read and up to 2,000 documents or 100 MB across everything your workspace has given it. Past that it stops adding more, and the dashboard shows what it holds.
- It re-reads on an hourly cycle, so a page you just changed may be out of date for a while. A request that opens the page live is not affected.
- Disconnecting forgets everything it read there, and reading again later starts from nothing.
When Ara is not the right fit for Notion
- All your work lives in Notion and you want the agent right there. Notion's own Agents work inside Notion and are the first thing to look at.
- You only need page search. Notion's search is already there, and credits per run are not worth it.
How control works on every connected app
- Every tool has a switch on the account that connected it. All are on until you switch them off, and "Reads only" leaves only the reads. A switched-off tool never runs.
- An admin can set one rule per app: "Runs without asking", "Asks a person first" or "Never runs". With no rule, which is the default, nothing waits, and that includes sending, changing and deleting.
- A waiting action shows what would change. Any member can decide it, and if nobody does, it expires and nothing runs. The decision can be made in the dashboard.
- A rule tells reads from changes by the tool's name. That is why this page names the exceptions on this app.
- Ara looks when asked or on a schedule. Starting a run the moment something changes in an app is not switched on for arator.rinda.ai today.
- Ara acts as the connected account, with one live account per app. To switch accounts, disconnect first. You work with Ara in Slack, a linked messenger or the dashboard, not inside the app.
- Only a workspace admin can create a schedule, and not from a group chat.
- What Ara reads passes through Composio and a model provider. If your data may not pass through a third party, Ara is not for you. We don't train models on your data, and what a provider keeps follows its own terms.
Tool names
A sample from the catalogue on arator.rinda.ai, read on 2026-11-04, with the class Ara shows on the permissions screen. Composio owns this list and can change it, so your permissions screen is the current one. Every tool has its own switch.
Read
- NOTION_SEARCH_NOTION_PAGE
- NOTION_GET_PAGE_MARKDOWN
- NOTION_FETCH_DATA
- NOTION_QUERY_DATABASE
- NOTION_FETCH_COMMENTS
Write
- NOTION_CREATE_NOTION_PAGE
- NOTION_ADD_MULTIPLE_PAGE_CONTENT
- NOTION_APPEND_TEXT_BLOCKS
- NOTION_INSERT_ROW_DATABASE
- NOTION_UPSERT_ROW_DATABASE
- NOTION_CREATE_COMMENT
Deletes or overwrites
- NOTION_ARCHIVE_NOTION_PAGE
- NOTION_DELETE_BLOCK
- NOTION_REPLACE_PAGE_CONTENT
- NOTION_UPDATE_ROW_DATABASE
Questions
- What's the difference between a knowledge source and connected tools?
- A knowledge source is read in the background and searched on every question. Connected tools run during a request, and can read or change a page or a row at that moment.
- Will Ara make up an answer if Notion doesn't have it?
- It is told to say it could not verify it, name where it looked, and say what would settle it. That is an instruction to a model, so check anything that matters against the source it names.
What it costs
Free to start with 20 credits and no card. 1 credit per completed run plus external data lookups; failed runs cost nothing. Business is quoted. A scheduled run and a first look use credits like any other completed run, even on a quiet day when you hear nothing.
How we checked this
Read from Ara's own code and the live site on 2026-11-04. Example jobs show what the tools and instructions allow, and an AI model can still get things wrong. If something here is out of date, tell us
Products mentioned
Other integrations
Hand Ara the job you keep putting off.
Bring your team's first AI employee into the chat you already use and give it one job. It comes back finished. Free to start, no card.