Connecting
1
Connect Notion
Connect Notion from the workspace’s integrations and grant access to the page that holds your blog database.
2
Pick the blog database
Choose the database your posts live in.
3
Map the columns
Tell Attensira which property holds what:
The mapping is checked against the database’s columns when you save it, so a property that does not exist or has the wrong type is refused then, not at the first delivery.
How an article is delivered
When the agent writes an article that targets Notion, it waits in Work for your approval like every article does. Approving it (Send to Notion) creates a new row in the database, in its draft state.- Ask or draft mode: the row stays a draft for your team to publish in Notion.
- Act mode: the row is set to published, and its published date to today, only if the mapping has a published value. Without one it stays a draft.
How updates work
The agent can list and read the posts in your mapped blog, and propose an update to one as a before/after in Work.- Updates always wait for your approval, in every mode, act included.
- Approving replaces that post’s content in Notion. The old blocks are archived, not deleted, so Notion’s own history still has them.
- An update never changes the post’s status.
- We never delete a Notion post.
list_blog_posts, read_blog_post and propose_blog_update, are offered only when a Notion blog database is mapped. See The agent’s tools.
After it ships
Publishing through Notion starts the before-and-after re-reads for the tracked prompts attached to the article, the same as a merged pull request.Settings
The mapping is stored in project settings asnotion_blog, with database_id, database_title, title_property, slug_property, status_property, status_kind, draft_value, published_value, body_property and published_date_property. Changes show in the settings log as notion blog: X → Y.