Connect each new campaign asset to creator media
Add an asset to your campaign database and make the account's Instagram content easier to review.
Trigger
New Page
Triggers when a new page is added to a Notion database.
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
Campaign assets and creator media often live apart, creating extra searching before a useful review.
- Bring creator posts alongside campaign asset planning.
- Make content review easier to start and finish.
- Reduce cross-tool searching during campaign work.
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 describe the asset-review outcome to Notis.
- 3In one prompt, ask Notis to retrieve Instagram media when a campaign asset page is added and explain where the creator account is recorded.
- 4Choose New Page for the asset database, select a run-report channel, and test with one real asset entry.
Questions about this workflow
What kind of account should this use?
This workflow is designed for Instagram assets and creator accounts that Notis can identify from the new page context.
Does the action create or edit campaign assets?
No. The selected action retrieves Instagram media for review.
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.