Docs & knowledge
Give your agents full access to Notion.
Agents search your workspace, read pages and databases, write new entries, and keep knowledge current. Name a database in the prompt once and memory carries what the agent learns about it across runs.
5,000 free credits to start.
Agent reach
Notion API
The full surface, searched at run time.
Connect with
- Helios OAuth app
- Your own OAuth app
- API key
Event triggers
Not yet
Manual, schedule, and signed webhook are available.
What the agent can do
What agents do with Notion
Helios searches the Notion API at run time. The agent finds the endpoint the task needs and calls it.
- Search Notion's entire API surface at run time and call any endpoint your integration can reach.
- Search and read pages, blocks, and database rows across the workspace.
- Create pages, append blocks, and write structured content.
- Query databases with filters and sorts; create and update rows with typed properties.
- Keep a database current on a schedule - audit stale entries, fill gaps, fix formatting.
- Use your workspace as the knowledge base an agent answers questions from.
Examples
Tasks you can hand to a Notion agent
Answer questions from your workspace
An agent searches Notion the way a colleague would, reads the pages that matter, and answers with links to the source.
What is our current on-call escalation policy?
- notion·search workspace for on-call policy
- notion·read `Engineering Handbook → On-call`
Answer with sources
- Primary pages within 5 minutes, secondary at 15
- Sev-1 pages the eng manager immediately
- Source: Engineering Handbook, updated Feb 12
Find documentation that went stale
A scheduled agent checks pages against the code and flags the ones that describe something that changed.
Monthly, find docs pages that contradict the current codebase.
- notion·list pages in `Engineering Docs`
- github·read referenced files at `main`
- code·diff documented behavior vs code
- notion·comment on 6 stale pages
6 stale pages flagged
- `Auth Setup` references a removed env var
- `Deploy Runbook` names an old cluster
- Each page commented with the specific line
File decisions where you keep them
The agent turns a channel discussion into a structured Notion entry with decisions, owners, and next steps.
After the weekly product discussion, file decisions into the Decisions database.
- slack·read this week's #product threads
- notion·create rows in `Decisions`
4 decisions recorded
- Each row has an owner, date, and Slack link
- 2 tagged `needs-follow-up`
Publish release notes to your docs
When a release ships, the agent writes the notes as a Notion page and links it from the changelog database.
On each published release, write a Notion changelog entry.
- github·read release body and merged PRs
- notion·create page in `Changelog`
Changelog entry published
- v2.8.0 with features, fixes, and breaking changes
- Linked to the GitHub release
Triggers
How a Notion workflow starts
Notion does not emit event triggers yet. Workflows that use it start by hand, on a schedule, or from a signed webhook.
Manual
Run it from the app with an optional JSON payload. Every workflow supports this.
Schedule
A cron expression or a plain sentence such as every weekday at 9am. Times are UTC.
Signed webhook
A public URL per workflow. Requests are signed with HMAC-SHA256 and expire after five minutes.
Works with
Notion works with the rest of your stack
One agent, one run, several services. It reads from one tool and writes to the next in the same sandbox.
Templates
Ready-to-run Notion workflows
Copy the prompt, connect your tools, and start a run.
Support
Slack support triage
Watches your support channel, answers what your docs already cover, and escalates the rest with the account context attached.
Support
Plain thread triage
Triages every new Plain thread on arrival. Labels, priority, a draft reply, and an internal note with what it checked.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.
Engineering
Incident postmortem drafter
Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.
Support
Documentation freshness audit
Checks your written docs against the codebase every month and comments on the pages that have gone stale.
Use cases
Where Notion agents fit
Support
Support triage
A workflow reads each new thread as it arrives. It finds the customer, checks the plan and billing state, sets labels and priority, and drafts a reply from your docs.
Engineering
Pull request review
A workflow reads each diff against your conventions and leaves a real review. A second workflow on a schedule posts the week's merged work, review backlog, and CI health.
Engineering
Incident summaries
A workflow rebuilds the timeline from your incident channel and the deploys around it. It names the likely change and drafts the write-up with the facts in place.
Marketing
Research briefs
A workflow searches the web, reads what it finds, and writes a draft with every claim linked to its source. Give it your prior work and the draft matches your voice.
FAQ
Questions, answered
Put an agent on Notion.
Connect it once and describe the task in chat. Then reuse the prompt as a workflow on a schedule or a webhook.