Start company research from a new view
Create a review view and start a sample company lookup for the work it is meant to support.
Trigger
View Created
Triggers when a new Notion view is created. Fires workspace-wide. The payload includes `data.view_type` (`table`, `board`, `gallery`, `calendar`, `list`, `timeline`, `gantt`) and `data.parent` pointing at the view's tree parent (typically the teamspace), so customers can filter downstream.
Action
Name to Domain Search
Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.
Why this helps
A new view can organize work without making the first research step obvious or easy to remember.
- Give a new research view a concrete first action.
- Use a sample lookup to help make the workflow tangible.
- Reduce setup-to-action delay when organizing a company review.
Setup
Build it in a few focused steps.
- 1Connect Notion and Bigpicture io to Notis once through the portal.
- 2Create an automation and instruct Notis to find likely domains for a named sample company when a company review view is created.
- 3Select View Created and describe how Notis should identify the sample company.
- 4Choose a channel for run reports and test by creating a suitable view.
Questions about this workflow
Can this trigger tell which companies are in the view?
The event provides the view type and parent context. Describe a dependable way to identify a sample company in the prompt.
Why use a sample company?
View creation is a workspace structure event, so a designated sample keeps the action focused and useful rather than attempting broad research.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Bigpicture io. A trigger fires from one place; an action lands in another.
Notion triggers
Bigpicture io actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Company Find
Tool to lookup company data by domain name. use when you need detailed company profile by providing a website domain. use after confirming domain correctness.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
IP to Company Lookup
Tool to lookup company by ip address. use after obtaining an ip to get detailed company info.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Name to Domain Search
Tool to find company domain(s) by company name. use when you have a company name and need up to 3 likely domains.
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 Bigpicture io, 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 Bigpicture io.