Notion
Run connic agents when pages are created or changed or comments are added in Notion. Agents reply in the comment's discussion or create new pages.
- Modes
- Inbound, Outbound
- Set up in
- Dashboard or connectors/*.yaml
- Documentation
- Notion docs
- Publisher
- By connic
Answer pages and comments
When a page or comment matches an inbound connector's events and data source, every agent linked to it starts. An outbound connector on the same Connection posts the result as a comment.
- Pick events and a data source
- React to new pages, property changes, or new comments, everywhere the integration sees or only in one database.
- One subscription, many connectors
- The subscription belongs to the integration, so connic routes each event to every matching connector on the Connection.
- No loops, no double runs
- The integration's own changes are ignored, and an event that Notion sends again doesn't start a second run.
Something happens in Notion
Someone creates a page, changes its properties, or writes a comment.
page.createdconnic checks the event
It verifies the signature with the subscription's verification token and reads the page or comment from Notion.
X-Notion-SignatureLinked agents start
The run gets the page's title, link, properties and content in Markdown, or the comment's text.
comment.createdThe answer lands in the discussion
An outbound connector on the same Connection comments on the page, in the discussion of the comment that started the run.
One secret, one subscription
You paste the integration's secret once and create a webhook subscription in Notion with the URL connic shows. Notion then sends a verification token, which connic shows you to paste back.
- Your integration, your workspace
- The integration belongs to your Notion workspace and only sees what you share with it. You can revoke it in Notion at any time.
- Signed events
- connic checks every event with the verification token and keeps it once the first signed event has arrived.
- Fresh content
- Events only name a page or comment, so connic reads the current version from Notion before the agent starts.
POST https://connect.connic.co/notion/<connection-id>
{
"verification_token": "secret_…"
}Comment on pages or create new ones
An outbound Notion connector posts the agent's output, whether the run answers a page or comes from another connector or a schedule.
- Routing
- A page_id in the output wins. Without one, a run started from a page on the same Connection comments there, and any other run creates a page in the connector's data source.
- Three ways to send
- Send after every completed run, give the model a tool to call, or call send_connector from middleware when your code decides.
- Markdown pages
- New pages take the output as Markdown, with headings and lists. When Notion rate-limits, connic waits and sends again.
{
"title": "Weekly churn report",
"body": "## Summary\n\n4 accounts cancelled."
}{
"body": "Approved. The refund goes out today.",
"page_id": "1f2e3d4c5b6a47988a7b6c5d4e3f2a1b"
}Where Notion fits
Pick a setup to see what reaches the agent and what it posts back to Notion.
Someone adds a request to a database, and the agent comments with a first assessment.
{
"event": "page.created",
"page_id": "1f2e3d4c-5b6a-4798-8a7b-6c5d4e3f2a1b",
"title": "Refund request: order 1042",
"text": "Order 1042 arrived two weeks late. The customer asks for a refund.",
"url": "https://www.notion.so/acme/1f2e3d4c5b6a47988a7b6c5d4e3f2a1b"
}{
"body": "Eligible: delivery was 14 days late. Suggest a full refund of 49 EUR."
}Someone asks a question in a comment, and the agent answers in the same discussion.
{
"event": "comment.created",
"page_id": "1f2e3d4c-5b6a-4798-8a7b-6c5d4e3f2a1b",
"title": "Onboarding guide",
"text": "Does this still apply to the EU region?",
"url": "https://www.notion.so/acme/1f2e3d4c5b6a47988a7b6c5d4e3f2a1b"
}{
"body": "Yes, except step 4: EU projects pick the region at signup."
}A draft moves to Ready for review, and the agent reads it and leaves its notes.
{
"event": "page.properties_updated",
"page_id": "1f2e3d4c-5b6a-4798-8a7b-6c5d4e3f2a1b",
"title": "Launch post draft",
"text": "# Launch post\n\nToday we ship…",
"url": "https://www.notion.so/acme/1f2e3d4c5b6a47988a7b6c5d4e3f2a1b"
}{
"body": "Two claims need a source, and the pricing paragraph is outdated."
}A schedule starts the agent every Monday, and it writes the report as a page in a database.
{
"schedule": "0 8 * * MON",
"timezone": "Europe/Berlin"
}{
"title": "Weekly churn report",
"body": "## Summary\n\n4 accounts cancelled."
}Notion FAQ
More connectors
Azure Service Bus
Receive messages from Service Bus queues and topic subscriptions to trigger agents, and send results to a queue or topic.
Inbound · Outbound
Cron Scheduler
Run an agent on any cron expression. connic hosts the scheduler for daily digests, hourly health checks, and weekly audits.
Inbound
Email (SMTP/IMAP)
Read an inbox to trigger an agent. Reply with a drafted message over SMTP. Attachments included.
Inbound · Outbound
GitHub
Run an agent on issues, comments, pull requests and reviews in a GitHub repository. It comments back or opens a new issue.
Inbound · Outbound
Jira
Run an agent on new issues, issue updates and comments in Jira Cloud. It comments back or creates a new issue.
Inbound · Outbound
Shopify
Run an agent when an order in your Shopify store is created, paid, fulfilled or cancelled. It tags the order or adds a note.
Inbound · Outbound