Keep a regular pulse on keyword visibility
A short recurring check can keep visibility signals easy to review without repeatedly rebuilding the same research session.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve share of voice data
Fetches share of voice data for specified keywords.
Why this helps
Share-of-voice monitoring can disappear from the week when it requires a fresh manual setup every time.
- See visibility data on a consistent schedule.
- Keep targets organized in a familiar Notion tracker.
- Make keyword monitoring easier to return to after a busy week.
Setup
Build it in a few focused steps.
- 1Connect Notion and Junglescout to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for a weekly keyword visibility pulse.
- 3Write one plain-language instruction asking Notis to read the chosen Notion targets and retrieve Junglescout share-of-voice data.
- 4Choose a weekly trigger, set a channel for reports, and test with one tracked term.
Questions about this workflow
Can the pulse cover several terms?
Yes. Describe the relevant keyword set in the prompt and verify the result with a small initial test.
Does this update the Notion tracker?
The action retrieves share-of-voice data. Ask for a report in your chosen channel unless you have separately specified an available Notion write action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Junglescout. A trigger fires from one place; an action lands in another.
Notion triggers
Junglescout actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Retrieve historical search volume data for a keyword
Fetches the historical search volume data for a specified keyword over a given time period.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Query the product database
Queries the jungle scout product database to retrieve product data based on various filters. compatible parameters include marketplace, sort, page size, product tiers, seller types, categories, exclude top brands, exclude unavailable products, min price, max price, min net, max net, min rank, max rank, min sales, max sales, min revenue, max revenue, min reviews, max reviews, min rating, max rating, min weight, max weight, min sellers, max sellers, min lqs, max lqs, min updated at, and max updated at.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Retrieve data for a specific keyword query
Returns data based on a specific keyword query, including search volume and competition.
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.
Retrieve keyword data for specified asins
Returns keywords for which the queried asin(s) appear in amazon search results. for a given keyword, jungle scout collects up to 3 pages of amazon keyword search results. query up to 10 asins at a time. apply filters to narrow search results.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Retrieve sales estimates data
Fetches sales estimates data for specified parameters.
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.
Retrieve share of voice data
Fetches share of voice data for specified keywords.
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 Junglescout, 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 Junglescout.