Make editorial review results easier to gather
Update the editorial review in Notion and have Notis fetch the relevant Ayrshare history and metrics.
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
Get Post History
Tool to retrieve ayrshare post history with metrics. use when you need to fetch and filter past posts by date, status, or record count.
Why this helps
Looking up results in a separate place can break focus while reviewing the editorial plan.
- Start a lookup from the review page already in use.
- Reduce switching between editorial planning and social reporting.
- Keep the review request and returned summary connected.
Setup
Build it in a few focused steps.
- 1Connect Notion and Ayrshare to Notis once in the portal.
- 2Create an automation in the portal or describe the intended workflow to Notis conversationally.
- 3Ask Notis in one plain-language instruction to fetch relevant post history and metrics when the editorial review is updated.
- 4Select Page Content Updated and scope it to the review page; choose a channel for run reports.
- 5Test with one real review edit and check the results.
Questions about this workflow
Can the trigger be limited to one review?
Yes. Page Content Updated can be scoped to a specific page.
Will every edit fetch results?
The event may follow content edits; describe the intended review cue in the instruction and test it with a real example.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Ayrshare. A trigger fires from one place; an action lands in another.
Notion triggers
Ayrshare actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Auto Schedule
Tool to create a new auto-post schedule with specified times and optional weekday filters. use when setting up recurring posting plans.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete a previously published Ayrshare post
Tool to delete an ayrshare post. use when you need to remove a published or scheduled post by its ayrshare post id, after confirming the correct id. note: instagram and tiktok published posts cannot be deleted via api; set `mark manual deleted=true` or remove manually.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Get Post History
Tool to retrieve ayrshare post history with metrics. use when you need to fetch and filter past posts by date, status, or record count.
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.
Set Auto Schedule
Tool to set up an auto-post schedule with specified times and optional weekday filters. use when scheduling posts around a recurring pattern.
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 Ayrshare, 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 Ayrshare.