Keep website monitoring inputs current from Notion
Change the monitoring brief once and prompt the corresponding Agenty input refresh, so the next run follows the current target.
Trigger
Page Content Updated
Triggers when the body content of a Notion page is 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 page content edit in the workspace the integration has access to. Notion aggregates content edits within a short window (~60s typical).
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
A website or monitoring scope can change in a brief while an agent input still points to the old target.
- Reduce outdated website targets in monitoring runs.
- Avoid repeating URL or scope edits in separate places.
- Keep the monitoring brief as the source of truth.
Setup
Build it in a few focused steps.
- 1Connect Notion and Agenty to Notis once through the portal.
- 2Create a named automation in Notis Automations.
- 3Write one plain-language instruction asking Notis to update the associated existing Agenty agent input from a changed monitoring brief when the new target or scope is clear.
- 4Select the Notion Page Content Updated trigger for the brief page, choose a run-report channel, and test with one real target change.
Questions about this workflow
Can this change the agent's input URL?
The Agenty action updates an agent input, which can include a URL. State clearly which brief supplies the target.
Will unrelated edits trigger an update?
Use the prompt to ask Notis to update the input only when the monitoring target or scope has changed.
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Agent
Tool to create a new agent. use when you need to add an agent with configuration and optional auto-start.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Agent Templates
Tool to fetch all public agent templates and sample agents. use when listing available templates for users to select.
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.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
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.
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."
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.
Create API Key
Tool to create a new api key. use when you need to provision access credentials for the api.
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.