Documentation Index
Fetch the complete documentation index at: https://help.notis.ai/llms.txt
Use this file to discover all available pages before exploring further.
The most powerful customization in Notis happens inside Notion itself. Every Notion database has a description field, and so does every property. Notis reads both on every interaction, so anything you write there becomes the rules of the road for that database.
This is the foundation of turning any database into an AI agent.
Where to write instructions
Database-level description
Open any database in Notion. Click the three-dots menu → Edit description. Whatever you write here becomes context Notis loads every time it touches that database.
Use the database description for:
- The overall purpose of the database
- Multi-step workflows that touch this database (e.g. “always research before saving”)
- Rules that span multiple properties (e.g. “the title and the slug must always match”)
Property-level description
Click the dropdown arrow on any property → Edit property → Description. Use property descriptions for per-field rules.
Use property descriptions for:
- Formatting expectations (“dates always in ISO format”)
- Content rules (“title is max 60 characters”)
- Default behaviors (“if I don’t specify a value, default to Medium”)
- Cross-property rules (“if Severity is Critical, set Priority to P0”)
A common pattern. The database has columns for the post title, platform, copy, and image. The instructions live where they belong:
Database description:
Social Media Calendar. When a new entry is created without copy, draft the
copy based on the title and the platform. Match the brand voice: direct,
no buzzwords, no emojis. Always generate the hero image last so the copy
informs the visual.
One of: X, LinkedIn, Instagram, TikTok. Default to LinkedIn if not
specified. Used to drive the copy length and tone (X: 280 chars max,
LinkedIn: 1200 chars max with line breaks every 2 sentences).
1536x1024 landscape. Brand color #24D366 only. No text on the image —
the copy lives in the Copy field. Generate transparent PNG when the
post will be reused as an asset.
Example: Bug Reports
Database description:
Bug Reports. Every entry must include the standard format below in the
body of the page:
Steps to reproduce:
Expected behavior:
Actual behavior:
Environment:
Screenshot or screen recording:
If a screenshot is attached, copy it to the Files property. Default
Severity to Medium unless explicitly stated.
One of: Low, Medium, High, Critical. Critical is reserved for outages
and data loss. If Severity is Critical, also create a task in Todoist
in the "On call" project.
Example: CRM follow-ups
Database description:
CRM. Every contact has a "Next follow-up" date. When I log a meeting
in Meeting Minutes that links to a contact here, suggest a follow-up
date based on the meeting type:
Discovery call: +3 days
Demo: +5 days
Negotiation: +2 days
Closed won/lost: +30 days
Update the contact's "Last touched" date to today.
Best practices
Keep instructions short and actionable. Notis re-reads them on every interaction, so verbose instructions slow things down and get less attention than crisp ones. Bullet points and short rules beat long paragraphs.
Write instructions for an intern. If a smart intern wouldn’t know what you mean, neither will Notis. Spell out the why alongside the rule when it isn’t obvious.
Iterate from real misses. When Notis does something wrong, that’s a signal an instruction is missing or unclear. Fix the description, don’t just correct the one entry.
Instructions live in Notion and apply to that workspace. If you have multiple Notion accounts connected (work + personal), make sure to add instructions to the right database — they don’t carry over.
What’s next
