Evaluate Vendors Without Endless Site Reading
Add a vendor to your Notion evaluation and get their certifications, integrations, pricing tiers, and case studies scraped automatically. Know their capabilities instantly.
Trigger
New Page
Triggers when a new page is added to a Notion database.
Action
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
Why this helps
Vendor selection requires reading through compliance docs and case studies manually. Founders get lost in PDFs and lose the comparison context.
- Extracts compliance and capability data without manual PDF hunting
- Keeps vendor comparisons consistent and data-driven
- Reduces time from shortlist to decision
Setup
Build it in a few focused steps.
- 1Connect Notion and Agentql to Notis.
- 2Create this automation: 'When I add a new vendor to my Vendor Evaluation database, scrape their website for security certifications (SOC2, ISO, GDPR), supported integrations, SLA details, and number of case studies available. Summarize in the notes.'
- 3Set trigger to 'New Page' in your Vendor Evaluation database and choose your channel.
- 4Test by adding one vendor and verify certifications and integrations appear.
- 5Customize to prioritize the compliance standards or integrations your team cares about most.
Questions about this workflow
What if they don't publish certifications on their main site?
Agentql will check common locations (security/compliance pages, docs, etc). If not found, you'll see 'not publicly listed' and can reach out to sales.
Can it extract full case study text or just links?
It can scrape case study pages and pull key metrics (results, company size, industry). For PDFs, it pulls the link and you can review manually.
Does this work for services with no public pricing?
Yes - it captures whatever is public (team size, case studies, support model). For hidden pricing, you'll know to request a quote.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Agentql. A trigger fires from one place; an action lands in another.
Notion triggers
Agentql actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Usage Details
Tool to retrieve subscription usage details for the current api key, including usage limits and billing period. use after confirming api connection is valid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query Data
Tool to query structured data as json from a web page using an agentql query or natural language prompt. use after defining your query or prompt and a url or html.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Create Remote Browser Session
Tool to create a remote browser session. use when you need to run browser automation on remote infrastructure.
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.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
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.
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.
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.
Connect any two apps with Notis in the middle.
Notion and Agentql, 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 Agentql.