Bring Instagram post context into creator feedback
A comment can be the cue to check the creator posts behind the discussion.
Trigger
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.
Action
Get Instagram Account Media
Tool to retrieve media content of an Instagram account. Use when you need detailed post-level data and performance metrics for analysis.
Why this helps
Feedback threads often point to content that still needs to be found and reviewed manually.
- Reduce the steps between feedback and evidence review.
- Keep discussion focused on actual creator media.
- Avoid losing a useful comment while switching into research.
Setup
Build it in a few focused steps.
- 1Connect Notion and HypeAuditor to Notis once in the portal.
- 2Create an automation in the portal or ask Notis conversationally to act on relevant comments.
- 3In one prompt, tell Notis to retrieve Instagram media when a comment discusses creator content, and explain how to identify the related account.
- 4Choose Comment Created, pick a run-report channel, and test with one real comment on a relevant page.
Questions about this workflow
Does this trigger require a special Notion capability?
Yes. The Notion connection needs the Read comments capability, and connections authorized before it was enabled may need reauthorization.
Can comments be limited to a page?
The event supports an optional page filter. When omitted, it applies to comments the integration can access.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Hypeauditor. A trigger fires from one place; an action lands in another.
Notion triggers
Hypeauditor actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Instagram Account Media
Tool to retrieve media content of an Instagram account. Use when you need detailed post-level data and performance metrics for analysis.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Instagram report
Tool to retrieve a detailed Instagram report. Use after providing username or user_id. Example: GET_REPORT_INSTAGRAM(username="nasa").
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get TikTok Analytics Report
Tool to get TikTok analytics report. Use when fetching detailed performance metrics for a TikTok account.
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 Hypeauditor, 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 Hypeauditor.