Create Agenty lists from new prospect collections
Start a prospect research collection in Notion and prepare a matching Agenty list without building the handoff from scratch.
Trigger
Page Created
Triggers when a new Notion page is created. Customer optionally scopes with at most one of: - data_source_id: new row in this data source - parent_page_id: new sub-page under this page (immediate parent only) With neither set, fires for any new page in the workspace the integration has access to. Notion sends ~60s aggregation latency on most events.
Action
Create List
Tool to create a new list. use after preparing the list name and optional description. example: "create a list named 'contacts' with description 'potential leads'."
Why this helps
Prospect research gets delayed when each new collection requires a separate list setup step.
- Prepare a dedicated place for new research results.
- Use the Notion page to preserve the collection's intent.
- Reduce setup steps when testing a new prospect segment.
Setup
Build it in a few focused steps.
- 1Connect Notion and Agenty to Notis once through the portal.
- 2Create a named automation in the Notis portal.
- 3Write one plain-language instruction asking Notis to create an Agenty list for each new prospect collection page, using its title and purpose.
- 4Choose the Notion Page Created trigger scoped to the collection's parent page, pick a run-report channel, and test with one real collection.
Questions about this workflow
Does this create a list for every new page?
Scope the trigger to the relevant parent page and describe the intended collection pages in the prompt.
Can the list have a description?
Yes. Ask Notis to derive a concise description from the page's stated research purpose.
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.