Review website redirects when notes change
Update the website context in Notion and get a redirect timeline to help spot domain changes or migration issues.
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
Redirects API Lookup
Tool to retrieve live and historical redirects for a website. use after confirming the exact root domain to gather inbound and outbound redirect timelines.
Why this helps
Redirect checks are easy to forget when someone updates a website or domain detail during a busy day.
- Retrieve live and historical redirects for the confirmed root domain.
- Connect a website note change to a practical domain check.
- Make migration follow-up easier to notice.
Setup
Build it in a few focused steps.
- 1Connect Notion and BuiltWith to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it in plain language.
- 3In one instruction, ask Notis to run a BuiltWith redirect lookup for the root domain when relevant website notes change.
- 4Choose the Notion Page Content Updated trigger and a run-report channel.
- 5Test by editing a real page's website or migration notes.
Questions about this workflow
What does the redirect lookup show?
BuiltWith retrieves live and historical redirects for the exact root domain supplied to the lookup.
Can this run on any Notion content edit?
Describe in the prompt which website-note edits matter so Notis can use the page context to decide whether to run the lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Builtwith. A trigger fires from one place; an action lands in another.
Notion triggers
Builtwith actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Domain List File
Tool to create a txt or zip file from a list of domains. use when preparing a domain list for bulk or firehose lookups.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Datasets Lookup
Tool to access mass internet technology usage information from 2000 to today. use when you need historical technology usage trends for a domain.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Domain API Lookup
Tool to retrieve current and historical technology information of a website. use after confirming the domain to lookup.
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.
Financial API Lookup
Tool to fetch financial data for a domain. use when you need company financials for us or uk registered websites.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Free API Lookup
Tool to access last updated dates and counts for technology groups and categories for websites. use when you need a snapshot of technology usage timing for a domain.
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.
Lists API Get List With Meta
Tool to retrieve a list of websites using a specified technology, including metadata. use when you need detailed company and site information for sites using a particular technology.
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.
Lists API Get List
Tool to retrieve a list of websites using a specific technology. use when you want to find sites leveraging a particular tech.
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.
MCP API Lookup
Tool to query live web technologies for a root domain. use after confirming a valid domain name.
Connect any two apps with Notis in the middle.
Notion and Builtwith, 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 Builtwith.