Connect launch-plan changes to creative options
When a launch-planning detail changes, bring current Imagior template options into the next planning conversation.
Trigger
Page Properties Updated
Triggers when properties of a Notion page are 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 property change in the workspace the integration has access to. Adding a column to a data source fires this trigger once per existing row. Customers can branch on `data.updated_properties` (array of property IDs) to filter downstream.
Action
List design templates
Tool to list all design templates. Use when you need to retrieve every template associated with your account.
Why this helps
A status change can require a new creative task, but founders may lose time switching tools to find a useful starting point.
- Make template discovery part of the launch-planning rhythm.
- Reduce tool switching after a launch detail changes.
- Give the next creative conversation a concrete reference point.
Setup
Build it in a few focused steps.
- 1Connect Notion and Imagior to Notis once in the portal.
- 2Create the automation or tell Notis to list Imagior templates when the relevant Notion launch-plan properties change.
- 3Pick Page Properties Updated and scope it to the launch data source or page if useful; choose a run-report channel.
- 4Test by changing one real launch-plan property and reviewing the run.
Questions about this workflow
Can I limit it to a particular launch plan?
The trigger supports a page or data-source scope. Use the plain-language prompt to explain the launch-planning context.
Does it run only when a specific property changes?
The trigger provides updated-property details, but this automation is set up through a plain-language instruction rather than a field-mapping screen.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Imagior. A trigger fires from one place; an action lands in another.
Notion triggers
Imagior actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
List design templates
Tool to list all design templates. Use when you need to retrieve every template associated with your account.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
All Page Events
Triggers when any Notion page is created or updated across the workspace.
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 Imagior, 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 Imagior.