Skip to content
Notis

Keep research agent inputs aligned with Notion

When a research record changes, ask Notis to refresh the relevant agent input so the next run uses the current scope.

Trigger

Page Properties Updated

Triggers when properties of a Notion page are updated. Customer optionally scopes with at most one of: - data_source_id: any row in this data source - page_id: this specific page - parent_page_id: any page whose immediate parent is this page With none set, fires for any property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.

Action

Update Input by Agent ID

Tool to update agent input by agent id. use when you need to modify an agent's input source (url, manual data, list, or agent) after verifying the agent id.

Why this helps

Research scope shifts, but the agent can keep working from outdated instructions unless someone remembers to revise its input.

  • Reduce stale-input runs after a scope change.
  • Avoid manually copying revised research instructions.
  • Keep agent preparation close to the source record.

Setup

Build it in a few focused steps.

  • 1Connect Notion and Agenty to Notis once through the portal.
  • 2Create a named automation in Automations in the Notis portal.
  • 3Write one plain-language instruction asking Notis to identify the associated Agenty agent and refresh its input from the changed research record.
  • 4Choose the Notion Page Properties Updated trigger for the research database, select a run-report channel, and test with a real scope update.

Questions about this workflow

Will every property edit change the agent input?

The trigger can fire on property updates. State in the prompt which kinds of changes should lead Notis to refresh the input.

Can I use this for any kind of agent input?

The Agenty action updates an agent's input. Describe the intended source and input clearly in the prompt.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Notion to Agenty. A trigger fires from one place; an action lands in another.

Notion triggers

Agenty actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Clone Agent by ID

Tool to clone an existing agent by its id. use when you need to duplicate an agent's configuration and optionally start the clone immediately.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Agent

Tool to create a new agent. use when you need to add an agent with configuration and optional auto-start.

ActionInstant

All Page Events

Triggers when any Notion page is created or updated across the workspace.

TriggerPolling

Get Agent Templates

Tool to fetch all public agent templates and sample agents. use when listing available templates for users to select.

ActionInstant

Comment Created

Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.

TriggerInstant

Delete Agent by ID

Tool to delete a single agent by its id. use when you need to permanently remove an agent after confirming it exists.

ActionInstant

New Comment

Triggers when a new comment is added to a specified Notion block or page.

TriggerPolling

Fetch all agents

Tool to fetch all active agents under an account. use after authenticating when you need to list agents with pagination and sorting.

ActionInstant

Database Created

Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.

TriggerInstant

Get Agent by ID

Tool to fetch details of a specific agent by its id. use when you need full agent configuration before taking further actions.

ActionInstant

Data Source Created

Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.

TriggerInstant

Update Agent by ID

Tool to update an agent's configuration and settings by agent id. use when you need to modify an existing agent after retrieving its current settings. example: "update agent 123 with new name and tags."

ActionInstant

Data Source Schema Updated

Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.

TriggerInstant

Create API Key

Tool to create a new api key. use when you need to provision access credentials for the api.

ActionInstant

Connect any two apps with Notis in the middle.

Notion and Agenty, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Agenty.